Data as of Nov 13, 2026

62.64.0.0/20

5 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
5
0.12% of its addresses · 30 days
Spread
5 of 16
/24s with at least one exit
Providers
17
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

381 observations

/24s with the most always-on exits

Proxy providers listing exits

  • 711Proxy
  • Ake.net
  • B2Proxy
  • BottingTools
  • Decodo
  • EZProxies
  • FastProxy
  • IPFly
  • IPPeak
  • LudaxProxy
  • Oxylabs
  • PuraRoute
  • RainProxy
  • RoamProxy
  • Shifter
  • Thordata
  • ThunderProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
62.64.0.0/19
since Feb 2020
AS31133Mobile19
2 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
62.64.0.0/198,192RU-MEGAFON-970429PJSC MegaFon (ORG-OM1-RIPE) · RUALLOCATED PADec 10, 2001abuse-mailbox@megafon.ru
└ 62.64.0.0/212,048MF-MOSCOW-BBA-20220424-T4104128Megafon-Moscow Broadband clients poolASSIGNED PANov 21, 2011abuse-mailbox@megafon.ru
via RU-MEGAFON-970429
└ 62.64.8.0/212,048MF-MOSCOW-BBA-20220424-T4104128Megafon-Moscow Broadband clients pool # 1ASSIGNED PANov 21, 2011abuse-mailbox@megafon.ru
via RU-MEGAFON-970429

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
Sep 2020
Current origin since
Sep 2020 · 6.1 yr
Origin networks
1