LAYER3 INTEL
Get started
Sign in
Data as of Nov 13, 2026

37.29.80.0/22

14 residential-proxy exits · 30 days

PJSC MegaFon

Announcement
this exact prefix
RPKI valid
Announced by
AS50928
Type
Mobile

Residential-proxy exits

Proxy exits
14
1.4% of its addresses · 30 days
Always-on exits
2
14% of its exits
Spread
4 of 4
/24s with at least one exit
Providers
58
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

7.4K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
37.29.81.0/2426
37.29.83.0/2405
37.29.82.0/2402
37.29.80.0/2401

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 9Proxy
  • Ake.net
  • AnyIP
  • BartProxies
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • Decodo
  • EnigmaProxy
  • Evomi
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • Geonix
  • Geonode
  • GonzoProxy
  • IPCola
  • IPFly
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • Kookey
  • LemonLabs
  • LemonPrime
  • MagneticProxy
  • MangoProxy
  • MarsProxies
  • NSocks
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • PROXYSCRAPE
  • PrivateByte
  • PrivateProxy
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • StrikeProxy
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalData
  • VitalExclusive
  • Webshare

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
37.29.0.0/17
since Feb 2020
AS31133Mobile1,089
97 always on
PJSC MegaFon
More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
37.29.80.0/24
since Aug 2016
AS50928Mobile1PJSC MegaFon
via Siberia Branch of OJSC MegaFon
37.29.81.0/24
since Dec 2012
AS50928Mobile6
2 always on
PJSC MegaFon
via Siberia Branch of OJSC MegaFon
37.29.82.0/24
since Jul 2013
AS50928Mobile2PJSC MegaFon
via Siberia Branch of OJSC MegaFon
37.29.83.0/24
since Apr 2015
AS50928Mobile5PJSC MegaFon
via Siberia Branch of OJSC 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.80.0/221,024MF-SIBSiberia Branch of OJSC MegaFonLIR-PARTITIONED PAOct 15, 2012abuse-mailbox@megafon.ru
via RU-MEGAFON-20111230
└ 37.29.80.0/24256MF-SIBSiberia Branch of OJSC MegaFonASSIGNED PAOct 17, 2012abuse-mailbox@megafon.ru
via MF-SIB
└ 37.29.81.0/24256MF-SIBSiberia Branch of OJSC MegaFonASSIGNED PAOct 17, 2012abuse-mailbox@megafon.ru
via MF-SIB
└ 37.29.82.0/24256MF-SIBSiberia Branch of OJSC MegaFonASSIGNED PAOct 17, 2012abuse-mailbox@megafon.ru
via MF-SIB
└ 37.29.83.0/24256MF-SIBSiberia Branch of PJSC MegaFon for clients of OmskASSIGNED PAOct 17, 2012abuse-mailbox@megafon.ru
via MF-SIB

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

AnnouncementRouting historyRPKI & IRRWhois & abuse
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