Data as of Nov 12, 2026

37.29.86.0/24

1 residential-proxy exit · 30 days

PJSC MegaFon

Announcement
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
20
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

1.0K observations

Proxy providers listing exits

  • 711Proxy
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • Decodo
  • Evomi
  • FlashProxy
  • GoProxies
  • GonzoProxy
  • Infatica
  • InfiniteProxies
  • Maskify
  • Oxylabs
  • Proxy-Seller
  • ProxyWing
  • Proxyma
  • ThunderProxy
  • Webshare

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
37.29.0.0/17
since Feb 2020
AS31133Mobile1,090
98 always on
PJSC MegaFon

Registrations in this block

The registry's network records over this block, widest first, each 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.84.0/221,024MF-GDC-T4120634-20220711Siberia Branch of OJSC MegaFonLIR-PARTITIONED PAJun 3, 2013abuse-mailbox@megafon.ru
via RU-MEGAFON-20111230
└ 37.29.86.0/23512MF-GDC-20220711-T4120634-CUS3G-2Megafon Siberia customer 2G/3GASSIGNED PAJun 4, 2013abuse-mailbox@megafon.ru
via MF-GDC-T4120634-20220711

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

37.29.86.0/23

Routing history

Pattern
Stable
First seen
Jun 2013
Current origin since
Jun 2013 · 13 yr
Origin networks
1