Data as of Nov 12, 2026

85.26.212.0/22

1 residential-proxy exit · 30 days

PJSC MegaFon

Announcement
this exact prefix
RPKI valid
Announced by
Type
Mobile
Risk
10 / 100 · Low
Shared address

Residential-proxy exits

Proxy exits
1
0.10% of its addresses · 30 days
Spread
1 of 4
/24s with at least one exit
Providers
20
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

43 observations

Proxy providers listing exits

  • BartProxies
  • BirdProxies
  • ByteProxies
  • Byteful
  • GSocks
  • Geonix
  • GonzoProxy
  • Infatica
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • RainProxy
  • Shifter
  • VantageProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
85.26.128.0/17
since Feb 2020
AS31133Mobile3,070
9 always on
PJSC 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
85.26.128.0/1732,768RU-MEGAFON-20050310PJSC MegaFon (ORG-OM1-RIPE) · RUALLOCATED PAMar 10, 2005abuse-mailbox@megafon.ru
└ 85.26.208.0/204,096MF-GDC-NWunknownLIR-PARTITIONED PANov 23, 2022abuse-mailbox@megafon.ru
via RU-MEGAFON-20050310
└ 85.26.212.0 - 85.26.219.2552,048MF-NWGSMunknownASSIGNED PAApr 18, 2025abuse-mailbox@megafon.ru
via MF-GDC-NW

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
Apr 2009
Current origin since
Aug 2016 · 10 yr
Origin networks
1