Data as of Nov 15, 2026

85.26.236.224/28

No anonymizer space · no proxy exits in 30 days

PJSC MegaFon

Announcement
RPKI valid
Announced by
Type
Business
Risk
0 / 100 · Low
Proxy exits nearby

Residential-proxy exits

Proxy exits
6
38% of its addresses · listed by providers
Always-on exits
5
83% of its exits
Providers
27
selling exits here

Proxy providers listing exits

  • 711Proxy
  • AnyIP
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • DataImpulse
  • Decodo
  • Evomi
  • FlashProxy
  • FloppyData
  • Geonode
  • GoProxies
  • IPFly
  • IPRoyal
  • Kookey
  • Maskify
  • NSocks
  • Oxylabs
  • Proxy4U
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • PuraRoute
  • StrikeProxy
  • Thordata
  • ThunderProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
85.26.232.0/21
since Dec 2009
AS31133Mobile1,022
6 always on
PJSC MegaFon
85.26.128.0/17
since Feb 2020
AS31133Mobile3,062
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.236.224/2816PSK-PSKOVLINE-LANPSKOVLINEASSIGNED PAJan 27, 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