Data as of Nov 12, 2026

77.35.108.64/28

4 residential-proxy exits · 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
4
25% of its addresses · 30 days
Providers
46
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

271 observations

Proxy providers listing exits

  • 9Proxy
  • Ake.net
  • BartProxies
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • EZProxies
  • EnigmaProxy
  • Evomi
  • GSocks
  • Geonix
  • Geonode
  • GhostConnect
  • GonzoProxy
  • HideProxy
  • IPFly
  • Infatica
  • InfiniteProxies
  • LemonLabs
  • LemonPrime
  • LudaxProxy
  • MangoProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • PROXYON
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • PrivateProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • Proxyma
  • PuraRoute
  • RainProxy
  • ResiProxies
  • SPYDERPROXY_BASIC
  • SPYDERPROXY_PREMIUM
  • Shifter
  • VantageProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
77.34.0.0/15
since Apr 2008
AS12332Residential24,318
35 always on
PJSC 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.35.108.64/2816POL-MUZDETPOL1-NETGor. Detskaya Policlinica 1ASSIGNED PAOct 9, 2007abuse@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.35.108.0/24

Routing history

Pattern
Rotating
First seen
Jul 2020
Current origin since
Sep 2022 · 4.1 yr
Origin networks
2
Last change of origin
Sep 2022
Recorded history

History

Handoffs
2