Data as of Nov 16, 2026

94.141.176.0/20

57 residential-proxy exits · 30 days

Megasvyaz LLC

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
57
1.4% of its addresses · 30 days
Always-on exits
4
7.0% of its exits
Spread
15 of 16
/24s with at least one exit
Providers
86
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

12K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • AETHYN_ELITE
  • Ake.net
  • B2Proxy
  • BartProxies
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • CoreProxy
  • DataImpulse
  • Decodo
  • EVOPROXY
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GEEKPROXY_FLEX
  • GSocks
  • Geonix
  • Geonode
  • GonzoProxy
  • HELODATA
  • HydraProxy
  • IPFly
  • IPMUSK
  • IPOasis
  • IPPeak
  • IPROCKET_PREMIUM
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • Kookey
  • LOKIPROXY
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • MoMoProxy
  • NSocks
  • NextProxy
  • NiuProxy
  • NodeMaven
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYLANE
  • PROXYSCRAPE
  • PrivateProxy
  • Proxiware
  • Proxmint
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • ProxyStyler
  • ProxyWing
  • Proxyma
  • PuraRoute
  • Q2IP
  • RainProxy
  • RapidProxy
  • RoamProxy
  • Shifter
  • StrikeProxy
  • SwiftProxy
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalData
  • VitalExclusive
  • VitalProxy
  • ZENPROXY_LITE

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
94.141.160.0/198,192RU-MEGASVYAZ-20070707Megasvyaz LLC (ORG-ML423-RIPE) · RUALLOCATED PAJun 27, 2017noc@starlink.ru
└ 94.141.176.0/212,048NLN-STARLINK-POOLNLN-STARLINK IP block 2ASSIGNED PAJul 8, 2010noc@starlink.ru
via RU-MEGASVYAZ-20070707
└ 94.141.184.0/221,024NLN-STARLINK-POOLNLN-Starlink Block 3ASSIGNED PAJul 8, 2010noc@starlink.ru
via RU-MEGASVYAZ-20070707
└ 94.141.188.0/23512NLN-STARLINK-POOLNLN-Starlink Block 4ASSIGNED PAJul 8, 2010noc@starlink.ru
via RU-MEGASVYAZ-20070707
└ 94.141.190.0/24256NLN-STARLINK-POOLNLN-Starlink Block 5ASSIGNED PAJul 8, 2010noc@starlink.ru
via RU-MEGASVYAZ-20070707

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

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Aug 2011
Current origin since
Mar 2024 · 2.7 yr
Origin networks
1