Data as of Nov 10, 2026

85.26.152.0/21

2 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
2
0.10% of its addresses · 30 days
Spread
2 of 8
/24s with at least one exit
Providers
21
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

202 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
85.26.155.0/2401
85.26.156.0/2401

Proxy providers listing exits

  • 2Captcha
  • BartProxies
  • BirdProxies
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • GonzoProxy
  • Infatica
  • MangoProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • RainProxy
  • Shifter
  • VantageProxies
  • VitalData
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
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.144.0/204,096MF-STF-20220624-T4104128unknownLIR-PARTITIONED PAJun 24, 2022abuse-mailbox@megafon.ru
via RU-MEGAFON-20050310
└ 85.26.152.0/212,048MF-STF-21062023unknownSUB-ALLOCATED PAJun 21, 2023abuse-mailbox@megafon.ru
via MF-STF-20220624-T4104128

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.144.0/20

Routing history

Pattern
Stable
First seen
Sep 2020
Current origin since
Sep 2020 · 6.1 yr
Origin networks
1