Data as of Nov 16, 2026

5.8.177.0/24

5 residential-proxy exits · 30 days

PJSC MegaFon

Announcement
this exact prefix
RPKI valid
Announced by
Type
Internet provider
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
5
2.0% of its addresses · 30 days
Always-on exits
1
20% of its exits
Providers
39
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

4.3K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • DataImpulse
  • EnigmaProxy
  • FlashProxy
  • GSocks
  • GeekProxy
  • Geonix
  • GonzoProxy
  • HydraProxy
  • IPFly
  • Infatica
  • LemonLabs
  • LightningProxies
  • MangoProxy
  • NSocks
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • PSBProxy
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • PuraRoute
  • Shifter
  • Smartproxy
  • VProxy
  • VibeProxies
  • VitalData
  • VitalExclusive
  • VitalProxy

Registrations in this block

The registry's network records over the announcement: those covering it, widest first, then every record inside it, under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
5.8.176.0/212,048RU-MEGAFON-20120426PJSC MegaFon (ORG-OM1-RIPE) · RUALLOCATED PAApr 26, 2012abuse-mailbox@megafon.ru
└ 5.8.177.0/24256GARSGARS TelecomASSIGNED PAMay 3, 2012abuse-mailbox@megafon.ru
via RU-MEGAFON-20120426

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 this prefix

Summary

Routing history

Pattern
Stable
First seen
Jun 2012
Current origin since
Apr 2015 · 12 yr
Origin networks
2
Last change of origin
Apr 2015
Recorded history

History

Handoffs
1