Data as of Nov 20, 2026

37.29.127.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 21, 2026 – Nov 19, 2026

Exits seen per day

355 observations

Proxy providers listing exits

  • Ake.net
  • BirdProxies
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • GonzoProxy
  • HydraProxy
  • Infatica
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • Shifter
  • VantageProxies
  • VitalData
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
37.29.0.0/17
since Feb 2020
AS31133Mobile1,082
100 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.112.0/204,096MF-KAVKAZCaucasus Branch of OJSC MegaFon, Mobile & Fixed BroabbandLIR-PARTITIONED PAJul 17, 2012abuse-mailbox@megafon.ru
via RU-MEGAFON-20111230
└ 37.29.127.0/24256MF-KAVKAZ-18082022-T4122797unknownASSIGNED PASep 27, 2012abuse-mailbox@megafon.ru
via MF-KAVKAZ

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
Mar 2013
Current origin since
Mar 2013 · 14 yr
Origin networks
1