Data as of Nov 11, 2026

37.29.78.64/26

3 residential-proxy exits · 30 days

PJSC MegaFon

Announcement
RPKI valid
Announced by
Type
Business
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
3
4.7% of its addresses · 30 days
Always-on exits
1
33% of its exits
Providers
24
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

541 observations

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • GonzoProxy
  • IPFly
  • Infatica
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • NodeProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • PuraRoute
  • Shifter
  • VibeProxies
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
37.29.76.0/22
since Jun 2013
AS35298Mobile8
1 always on
PJSC MegaFon
via Volga Branch of OJSC MegaFon, TD
37.29.0.0/17
since Feb 2020
AS31133Mobile1,096
102 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.76.0/221,024MF-PF-TDVolga Branch of OJSC MegaFon, TDLIR-PARTITIONED PAMay 29, 2013abuse-mailbox@megafon.ru
via RU-MEGAFON-20111230
└ 37.29.78.64/2664CUSTOMER-BNGTLTBNGTLTASSIGNED PANov 18, 2016abuse-mailbox@megafon.ru
via MF-PF-TD

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.78.0/24

Routing history

Pattern
Reactivated
First seen
Jun 2019
Current origin since
Aug 2022 · 4.2 yr
Origin networks
2
Last change of origin
Aug 2022
Recorded history

History

Handoffs
1