Data as of Nov 12, 2026

77.34.66.0/23

57 residential-proxy exits · 30 days

PJSC Rostelecom

Announcement
RPKI valid
Announced by
Type
Residential

Residential-proxy exits

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

Exits seen per day

5.1K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
77.34.67.0/24056
77.34.66.0/2401

Proxy providers listing exits

  • Ake.net
  • BartProxies
  • BirdProxies
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • DataImpulse
  • Datarama
  • Decodo
  • EVOPROXY
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • Geonix
  • Geonode
  • GonzoProxy
  • HideProxy
  • IPFly
  • IPPeak
  • Infatica
  • InfiniteProxies
  • LemonLabs
  • LemonPrime
  • LudaxProxy
  • MangoProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • PrivateByte
  • ProxiesVision
  • Proxio
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • Proxyma
  • PuraRoute
  • RainProxy
  • RapidProxy
  • Shifter
  • SwiftProxy
  • TORCHPROXIES_BASIC
  • TORCHPROXIES_PREMIUM
  • TORCHPROXIES_X
  • TrueProxies
  • VantageProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
77.34.0.0/15
since Apr 2008
AS12332Residential24,318
35 always on
PJSC Rostelecom
More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
77.34.67.0/24
since Mar 2025
AS12389Residential56PJSC Rostelecom

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
77.34.0.0/15131,072RU-RTK-20050601PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PAJan 24, 2007abuse@rt.ru
└ 77.34.66.0/23512POL-PPPOE-NET-UNLDynamic Broadband Clients.ASSIGNED PAJul 17, 2012abuse@rt.ru
via RU-RTK-20050601

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.34.64.0/20

Routing history

Pattern
Stable
First seen
Mar 2010
Current origin since
Mar 2010 · 17 yr
Origin networks
1