Data as of Nov 10, 2026

77.50.136.0/23

11 residential-proxy exits · 30 days

Megasvyaz LLC

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

Residential-proxy exits

Proxy exits
11
2.1% of its addresses · 30 days
Spread
2 of 2
/24s with at least one exit
Providers
37
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

2.0K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
77.50.136.0/2406
77.50.137.0/2405

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BartProxies
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FlashProxy
  • GSocks
  • Geonix
  • GonzoProxy
  • IPFly
  • IPOasis
  • IPPeak
  • Infatica
  • Kookey
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • VantageProxies
  • VitalData
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
77.50.0.0/16
since Jan 2007
AS34602Residential2,253
207 always on
Megasvyaz LLC

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
77.50.0.0/1665,536RU-MEGASVYAZ-20070104Megasvyaz LLC (ORG-ML423-RIPE) · RUALLOCATED PAJun 27, 2017noc@starlink.ru
└ 77.50.128.0/1816,384STARLINK-NETstarlink block 3ASSIGNED PAJun 18, 2010noc@starlink.ru
via RU-MEGASVYAZ-20070104

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

77.50.128.0/17

Routing history

Pattern
Stable
First seen
Oct 2007
Current origin since
Oct 2007 · 19 yr
Origin networks
1