Data as of Nov 10, 2026

85.26.166.0/23

1 residential-proxy exit · 30 days

PJSC MegaFon

Announcement
RPKI valid
Announced by
Type
Mobile

Residential-proxy exits

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

Exits seen per day

11 observations

Proxy providers listing exits

  • IPFly
  • PuraRoute

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
85.26.128.0/17
since Feb 2020
AS31133Mobile3,052
10 always on
PJSC MegaFon
More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
85.26.167.0/24
since Feb 2009
AS31133Mobile1PJSC MegaFon
via OJSC MSS-Povolzhe network - GPRS Access Pool No. 3

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.164.0/221,024MF-GDCOJSC MSS-Povolzhe network - GPRS Access Pool No. 3LIR-PARTITIONED PAAug 20, 2021abuse-mailbox@megafon.ru
via RU-MEGAFON-20050310
└ 85.26.166.0/23512MF-GDCOJSC MSS-Povolzhe network - GPRS Access Pool No. 3ASSIGNED PAMay 5, 2022abuse-mailbox@megafon.ru
via MF-GDC

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.164.0/22

Routing history

Pattern
Stable
First seen
Jan 2009
Current origin since
Jan 2009 · 18 yr
Origin networks
1