Data as of Nov 16, 2026

85.26.167.0/24

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.39% of its addresses · 30 days
Providers
2
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

41 observations

Proxy providers listing exits

  • IPFly
  • PuraRoute

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
85.26.164.0/22
since Jan 2009
AS31133Mobile474PJSC MegaFon
via OJSC MSS-Povolzhe network - GPRS Access Pool No. 3
85.26.128.0/17
since Feb 2020
AS31133Mobile3,058
11 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.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

RPKI

Route origin authorizations

ROA prefixASNMax lenAnchorVerdict
85.26.167.0/24AS31133/24RIPERPKI valid
85.26.164.0/22AS31133/22RIPEToo specific
85.26.128.0/17AS31133/17RIPEToo specific
IRR

Route objects on the exact prefix

OriginRegistryDescriptionMaintainerModified
AS31133 RIPEOJSC MSS-Povolzhe Network.GDC-TR-COREIPMar 30, 2022