Data as of Nov 12, 2026

77.82.56.0/22

186 residential-proxy exits · 30 days

PJSC Rostelecom

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential
88% of it

Residential-proxy exits

Proxy exits
186
18% of its addresses · 30 days
Always-on exits
1
0.54% of its exits
Spread
4 of 4
/24s with at least one exit
Providers
79
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

12K observations
  • Residential
  • Business

/24s with the most always-on exits

/24Always-on exitsProxy exits
77.82.59.0/24135
77.82.58.0/24053
77.82.57.0/24051
77.82.56.0/24048

Proxy providers listing exits

  • 711Proxy
  • 911Proxy
  • 9Proxy
  • ASHBURNPROXIES
  • Ake.net
  • AnyIP
  • B2Proxy
  • BartProxies
  • BirdProxies
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • DataImpulse
  • Datarama
  • Decodo
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • Geonix
  • Geonode
  • GhostConnect
  • GloryCloud
  • GonzoProxy
  • HideProxy
  • HydraProxy
  • IPFly
  • IPOasis
  • IPPeak
  • Infatica
  • InfiniteProxies
  • KindProxy
  • Kookey
  • LemonLabs
  • LemonPrime
  • LudaxProxy
  • MangoProxy
  • Maskify
  • MoMoProxy
  • NSocks
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYON
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • PrivateProxy
  • ProxiesVision
  • Proxio
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • Proxying
  • Proxyma
  • PuraRoute
  • RainProxy
  • RapidProxy
  • SPYDERPROXY_BASIC
  • SPYDERPROXY_PREMIUM
  • Shifter
  • ThunderProxy
  • VantageProxies
  • VitalData
  • VitalExclusive
  • YumiProxy
  • ZENPROXY_LITE
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
77.82.48.0/20
since Jul 2008
AS34974Residential715
2 always on
PJSC Rostelecom

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.82.0.0/1665,536RU-RTK-20070221PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PAFeb 21, 2007abuse@rt.ru
└ 77.82.56.0/24256RU-KAMCHATKAFar East Telecommunications Company (Dalsvyaz)ASSIGNED PAJan 14, 2025abuse@rt.ru
via RU-RTK-20070221
└ 77.82.57.0/24256RU-KAMCHATKAFar East Telecommunications Company (Dalsvyaz)ASSIGNED PAJan 14, 2025abuse@rt.ru
via RU-RTK-20070221
└ 77.82.58.0/24256RU-KAMCHATKAFar East Telecommunications Company (Dalsvyaz)ASSIGNED PAJan 14, 2025abuse@rt.ru
via RU-RTK-20070221
└ 77.82.59.0/25128RU-KAMCHATKAFar East Telecommunications Company (Dalsvyaz)ASSIGNED PAJan 14, 2025abuse@rt.ru
via RU-RTK-20070221
└ 77.82.59.128/25128RU-KAMCHATKARostelecom (ORG-FETC4-RIPE)ASSIGNED PAMay 25, 2009abuse@noc.kamchatka.ru

A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.

Composition

The types across the prefix's announced space, by addresses.

Announced space

Address share

Announced space

Types across the prefix

1,024 addresses
TypeAddressesShareRanges
Residential89688%2
Business12813%1

Network & registry

Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Dec 2016
Current origin since
Dec 2016 · 9.9 yr
Origin networks
1