Data as of Nov 11, 2026

77.50.4.0/22

5 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
5
0.49% of its addresses · 30 days
Spread
1 of 4
/24s with at least one exit
Providers
28
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

459 observations

Proxy providers listing exits

  • Ake.net
  • BartProxies
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • DataImpulse
  • EnigmaProxy
  • GSocks
  • Geonix
  • GonzoProxy
  • IPFly
  • Infatica
  • LemonLabs
  • LemonPrime
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • VantageProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
77.50.0.0/16
since Jan 2007
AS34602Residential2,260
168 always on
Megasvyaz LLC

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
77.50.0.0/1665,536RU-MEGASVYAZ-20070104Megasvyaz LLC (ORG-ML423-RIPE) · RUALLOCATED PAJun 27, 2017noc@starlink.ru
└ 77.50.0.0 - 77.50.27.2557,168STARLINK-NETstarlink block 1ASSIGNED PAOct 6, 2026noc@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

Summary

Routing history

Pattern
Stable
First seen
Mar 2018
Current origin since
Mar 2018 · 8.7 yr
Origin networks
1