Data as of Nov 16, 2026

217.112.1.0/24

28 residential-proxy exits · 30 days

PJSC MegaFon

Announcement
RPKI valid
Announced by
Type
Hosting
Risk
50 / 100 · Medium

Residential-proxy exits

Proxy exits
28
11% of its addresses · 30 days
Always-on exits
1
3.6% of its exits
Providers
46
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

1.4K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • Ake.net
  • BartProxies
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • Geonix
  • GloryCloud
  • GonzoProxy
  • HELODATA
  • IPFly
  • IPPeak
  • Infatica
  • KindProxy
  • LemonPrime
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYLANE
  • PROXYSCRAPE
  • Proxio
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • VantageProxies
  • VitalExclusive
  • VitalProxy

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
217.112.0.0/204,096RU-MEGAFON-20090504PJSC MegaFon (ORG-OM1-RIPE) · RUALLOCATED PAMay 4, 2009abuse-mailbox@megafon.ru
└ 217.112.1.0/24256ITCN-VVG-DATACENTERNet By Net Holding LLCASSIGNED PANov 19, 2009abuse-mailbox@megafon.ru
via RU-MEGAFON-20090504

A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.

Network & registry

Routing timeline

Who has announced 217.112.0.0/20

217.112.0.0/20

Routing history

Pattern
Stable
First seen
May 2009
Current origin since
Oct 2014 · 12 yr
Origin networks
3
Last change of origin
Oct 2014
Recorded history

History

Handoffs
3