Data as of Nov 12, 2026

77.34.74.0/24

6 residential-proxy exits · 30 days

PJSC Rostelecom

Announcement
this exact prefix
RPKI valid
Announced by
Type
Business
50% of it

Residential-proxy exits

Proxy exits
6
2.3% of its addresses · 30 days
Providers
30
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

1.1K observations
  • Residential
  • Business

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • EnigmaProxy
  • GSocks
  • GonzoProxy
  • IPFly
  • IPPeak
  • Infatica
  • LemonPrime
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • PuraRoute
  • Shifter
  • VantageProxies
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
77.34.64.0/20
since Mar 2010
AS12332Residential135
13 always on
PJSC Rostelecom
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 the announcement: those covering it, widest first, then every record inside it, 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.74.0/25128POL-PPPOE-NET-UNLDynamic Broadband Clients.ASSIGNED PAJul 17, 2012abuse@rt.ru
via RU-RTK-20050601
└ 77.34.74.128/25128POL-FOKINOTELECOM-NETFokino-Telecom, LTDASSIGNED PASep 25, 2011abuse@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.

Composition

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

Announced space

Address share

Announced space

Types across the prefix

256 addresses
TypeAddressesShareRanges
Business12850%1
Residential12850%1

Network & registry

Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Jun 2022
Current origin since
Jun 2022 · 4.4 yr
Origin networks
1