Data as of Nov 14, 2026

62.64.28.0/24

3 residential-proxy exits · 30 days

PJSC MegaFon

Announcement
RPKI valid
Announced by
Type
Mobile
Risk
10 / 100 · Low
Shared address

Residential-proxy exits

Proxy exits
3
1.2% of its addresses · 30 days
Always-on exits
1
33% of its exits
Providers
30
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

682 observations

Proxy providers listing exits

  • 711Proxy
  • Ake.net
  • B2Proxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • Decodo
  • Evomi
  • FlashProxy
  • FloppyData
  • Geonode
  • GloryCloud
  • IPFly
  • IPPeak
  • Infatica
  • InfiniteProxies
  • Maskify
  • NovaProxy
  • Oxylabs
  • PrivateByte
  • Proxies.fo
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • RapidProxy
  • StrikeProxy
  • SwiftProxy
  • Thordata
  • ThunderProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
62.64.0.0/19
since Feb 2020
AS31133Mobile19
4 always on
PJSC MegaFon

Registrations in this block

The registry's network records over this block, widest first, each 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.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

Routing timeline

Covering aggregate above, the prefix's own history below

62.64.16.0/20

Routing history

Pattern
Rotating
First seen
Jul 2012
Current origin since
Oct 2023 · 3.1 yr
Origin networks
2
Last change of origin
Oct 2023
Recorded history

History

Handoffs
1