Data as of Nov 21, 2026

81.24.128.0/24

4 residential-proxy exits · 30 days

PJSC MegaFon

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

Residential-proxy exits

Proxy exits
4
1.6% of its addresses · 30 days
Always-on exits
1
25% of its exits
Providers
40
selling exits here
Oct 22, 2026 – Nov 20, 2026

Exits seen per day

1.2K observations

Proxy providers listing exits

  • 2Captcha
  • AETHYN_BASIC
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CYBERYOZH
  • CatProxies
  • EnigmaProxy
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • FlashProxy
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • GonzoProxy
  • IPFly
  • IPRoyal
  • Infatica
  • LightningProxies
  • MangoProxy
  • NextProxy
  • NodeProxy
  • NovaProxy
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • ProxyRack
  • ProxyWing
  • Proxyma
  • PuraRoute
  • SOTAPROXY
  • Shifter
  • TORCHPROXIES_BASIC
  • TORCHPROXIES_PREMIUM
  • TORCHPROXIES_X
  • VitalExclusive
  • VitalProxy

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
81.24.128.0/204,096RU-MEGAFON-20020315PJSC MegaFon (ORG-OM1-RIPE) · RUALLOCATED PASep 24, 2002abuse-mailbox@megafon.ru
└ 81.24.128.0/221,024ASPOLASPOL-Diamant-Murmansk Ltd. RussiaASSIGNED PAMar 15, 2002abuse-mailbox@megafon.ru
via RU-MEGAFON-20020315

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 81.24.128.0/20

81.24.128.0/20

Routing history

Pattern
Rotating
First seen
May 2005
Current origin since
Aug 2022 · 4.3 yr
Origin networks
3
Last change of origin
Aug 2022
Recorded history

History

Handoffs
2