LAYER3 INTEL
Get started
Sign in
Data as of Nov 11, 2026

62.64.0.0/19

19 residential-proxy exits · 30 days

PJSC MegaFon

Announcement
this exact prefix
RPKI valid
Announced by
AS31133
Type
Mobile

Residential-proxy exits

Proxy exits
19
0.23% of its addresses · 30 days
Always-on exits
2
11% of its exits
Spread
12 of 32
/24s with at least one exit
Providers
60
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

1.9K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
62.64.28.0/2413
62.64.30.0/2411
62.64.16.0/2403
62.64.23.0/2402
62.64.25.0/2402
62.64.29.0/2402
62.64.3.0/2401
62.64.9.0/2401
62.64.10.0/2401
62.64.12.0/2401
62.64.14.0/2401
62.64.19.0/2401

Proxy providers listing exits

  • 711Proxy
  • Ake.net
  • B2Proxy
  • BirdProxies
  • BlurPath
  • BottingTools
  • ByteProxies
  • Byteful
  • CatProxies
  • DataImpulse
  • Decodo
  • EZProxies
  • Evomi
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • Geonix
  • Geonode
  • GloryCloud
  • GonzoProxy
  • IPFly
  • IPPeak
  • Infatica
  • InfiniteProxies
  • KindProxy
  • Kookey
  • LudaxProxy
  • MangoProxy
  • Maskify
  • MoMoProxy
  • NextProxy
  • NiuProxy
  • NodeProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PrivateByte
  • Proxies.fo
  • Proxio
  • Proxiware
  • Proxmint
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • PuraRoute
  • Q2IP
  • RainProxy
  • RapidProxy
  • RoamProxy
  • Shifter
  • StrikeProxy
  • SwiftProxy
  • Thordata
  • ThunderProxy
  • VitalData
  • VitalProxy

Announcements

More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
62.64.0.0/20
since Sep 2020
AS25159Mobile5PJSC MegaFon
62.64.16.0/20
since Oct 2023
AS25159Mobile14
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
└ 62.64.16.0/204,096MF-STF-27092023unknownSUB-ALLOCATED PASep 27, 2023abuse-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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
Feb 2020 · 6.8 yr
Origin networks
2
Last change of origin
Feb 2020
Recorded history

History

Handoffs
1