Data as of Nov 15, 2026

37.29.70.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
31
selling exits here
Oct 16, 2026 – Nov 14, 2026

Exits seen per day

486 observations

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BirdProxies
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • EnigmaProxy
  • Evomi
  • GSocks
  • Geonode
  • GonzoProxy
  • HideProxy
  • HydraProxy
  • Infatica
  • InfiniteProxies
  • LightningProxies
  • MangoProxy
  • NextProxy
  • NodeMaven
  • NovaProxy
  • ProxiesVision
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • Proxyma
  • Shifter
  • VantageProxies
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
37.29.0.0/17
since Feb 2020
AS31133Mobile1,089
95 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
37.29.0.0/1732,768RU-MEGAFON-20111230PJSC MegaFon (ORG-OM1-RIPE) · RUALLOCATED PADec 30, 2011abuse-mailbox@megafon.ru
└ 37.29.68.0/221,024MF-NWGSMNorth-West Branch of OJSC MegaFon Network, Pool 9 (PublicIP).LIR-PARTITIONED PAAug 17, 2021abuse-mailbox@megafon.ru
via RU-MEGAFON-20111230
└ 37.29.70.0/23512MF-NWGSMunknownASSIGNED PAApr 17, 2025abuse-mailbox@megafon.ru
via MF-NWGSM

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