Data as of Nov 14, 2026

37.29.23.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
19
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

255 observations

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BirdProxies
  • ByteProxies
  • Byteful
  • EnigmaProxy
  • GonzoProxy
  • HydraProxy
  • Infatica
  • LightningProxies
  • MangoProxy
  • NovaProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • Shifter
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
37.29.0.0/17
since Feb 2020
AS31133Mobile1,091
96 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.16.0 - 37.29.27.2553,072MF-FCURPunknownLIR-PARTITIONED PASep 14, 2021abuse-mailbox@megafon.ru
via RU-MEGAFON-20111230
└ 37.29.18.0 - 37.29.23.2551,536CUSTOMER-30-LAN-37-29-16PtPASSIGNED PAJul 7, 2014abuse-mailbox@megafon.ru
via MF-FCURP

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
Oct 2014
Current origin since
Oct 2014 · 12 yr
Origin networks
1