Data as of Nov 21, 2026

37.29.116.0/24

4 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
4
1.6% of its addresses · 30 days
Providers
22
selling exits here
Oct 22, 2026 – Nov 20, 2026

Exits seen per day

386 observations

Proxy providers listing exits

  • Ake.net
  • BirdProxies
  • Byteful
  • CatProxies
  • Datarama
  • Evomi
  • GEEKPROXY_FLEX
  • GSocks
  • Infatica
  • InfiniteProxies
  • LudaxProxy
  • MangoProxy
  • NodeProxy
  • PrivateProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • Proxyma
  • RainProxy
  • Shifter
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
37.29.0.0/17
since Feb 2020
AS31133Mobile1,078
101 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.116.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
Jul 2012
Current origin since
Jul 2012 · 14 yr
Origin networks
1