Data as of Nov 11, 2026

178.209.241.0/24

39 residential-proxy exits · 30 days

PJSC MegaFon

Announcement
RPKI valid
Announced by
Type
Mobile
Risk
10 / 100 · Low
Shared address

Residential-proxy exits

Proxy exits
39
15% of its addresses · 30 days
Always-on exits
1
2.6% of its exits
Providers
55
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

8.3K observations

Proxy providers listing exits

  • 2Captcha
  • 9Proxy
  • Ake.net
  • BartProxies
  • BirdProxies
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • DataImpulse
  • Datarama
  • Decodo
  • EnigmaProxy
  • Evomi
  • FLEETPROXY
  • FastProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • Geonix
  • Geonode
  • GoProxies
  • GonzoProxy
  • HideProxy
  • IPFly
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • LemonLabs
  • LemonPrime
  • LudaxProxy
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • PROXYSCRAPE
  • ProxiesVision
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • Proxyma
  • PuraRoute
  • RainProxy
  • ResiProxies
  • SPYDERPROXY_PREMIUM
  • Shifter
  • Thordata
  • VantageProxies
  • VitalExclusive

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
178.209.224.0/198,192RU-MEGAFON-20100610PJSC MegaFon (ORG-OM1-RIPE) · RUALLOCATED PAJun 10, 2010abuse-mailbox@megafon.ru
└ 178.209.240.0/221,024SURGUT-ME-NETNet By Net Holding LLCASSIGNED PANov 29, 2011abuse-mailbox@megafon.ru
via RU-MEGAFON-20100610

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 178.209.224.0/19

178.209.224.0/19

Routing history

Pattern
Stable
First seen
Jun 2010
Current origin since
Mar 2014 · 13 yr
Origin networks
2
Last change of origin
Mar 2014
Recorded history

History

Handoffs
1