Data as of Nov 10, 2026

85.26.239.0/24

3 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
3
1.2% of its addresses · 30 days
Always-on exits
1
33% of its exits
Providers
32
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

755 observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 9Proxy
  • Ake.net
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • Decodo
  • EnigmaProxy
  • Evomi
  • FlashProxy
  • Geonode
  • GloryCloud
  • IPFly
  • IPRoyal
  • InfiniteProxies
  • KindProxy
  • Kookey
  • NextProxy
  • Oxylabs
  • PrivateProxy
  • Proxy4U
  • ProxyGeo
  • ProxyRack
  • ProxyWing
  • PuraRoute
  • RainProxy
  • RapidProxy
  • StrikeProxy
  • SwiftProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
85.26.232.0/21
since Dec 2009
AS31133Mobile1,028
6 always on
PJSC MegaFon
85.26.128.0/17
since Feb 2020
AS31133Mobile3,052
10 always on
PJSC MegaFon

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
85.26.128.0/1732,768RU-MEGAFON-20050310PJSC MegaFon (ORG-OM1-RIPE) · RUALLOCATED PAMar 10, 2005abuse-mailbox@megafon.ru
└ 85.26.236.0/221,024MF-FCURPunknownLIR-PARTITIONED PAAug 31, 2021abuse-mailbox@megafon.ru
via RU-MEGAFON-20050310
└ 85.26.239.0/24256CUSTOMERS-GPRS-LANCORPASSIGNED PAFeb 4, 2011abuse-mailbox@megafon.ru
via MF-FCURP

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

85.26.236.0/22

Routing history

Pattern
Stable
First seen
Dec 2010
Current origin since
Dec 2010 · 16 yr
Origin networks
1