Data as of Nov 12, 2026

85.26.228.0/24

2 residential-proxy exits · 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
2
0.78% of its addresses · 30 days
Providers
4
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

2 observations

Proxy providers listing exits

  • BottingTools
  • IPFly
  • LudaxProxy
  • PuraRoute

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
85.26.128.0/17
since Feb 2020
AS31133Mobile3,066
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.228.0/221,024MF-GDC-20220711-T4120634Siberia Branch of OJSC MegaFonLIR-PARTITIONED PANov 19, 2010abuse-mailbox@megafon.ru
via RU-MEGAFON-20050310
└ 85.26.228.0 - 85.26.230.255768MF-GDC-20220711-T4120634-CUS3G-1Megafon Siberia customer 2G/3GASSIGNED PAJul 1, 2011abuse-mailbox@megafon.ru
via MF-GDC-20220711-T4120634

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
Jun 2011
Current origin since
Jun 2011 · 15 yr
Origin networks
1