Data as of Nov 17, 2026

81.23.9.0/24

7 residential-proxy exits · 30 days

PJSC MegaFon

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

Residential-proxy exits

Proxy exits
7
2.7% of its addresses · 30 days
Providers
35
selling exits here
Oct 18, 2026 – Nov 16, 2026

Exits seen per day

2.4K observations

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FlashProxy
  • GEEKPROXY_FLEX
  • GSocks
  • Geonix
  • GloryCloud
  • GonzoProxy
  • IPFly
  • IPOasis
  • IPPeak
  • Infatica
  • LemonLabs
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • VantageProxies
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
81.23.8.0/23
since Dec 2010
AS31261Internet provider13PJSC MegaFon

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
81.23.0.0/204,096RU-MEGAFON-20100812PJSC MegaFon (ORG-OM1-RIPE) · RUALLOCATED PAAug 12, 2010abuse-mailbox@megafon.ru
└ 81.23.9.0/24256Dmitrovka_PlazaOOO Dmitrovka PlazaASSIGNED PAAug 9, 2011abuse-mailbox@megafon.ru
via RU-MEGAFON-20100812

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

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Feb 2019
Current origin since
Feb 2019 · 7.8 yr
Origin networks
1