Data as of Nov 11, 2026

178.34.64.0/22

7 residential-proxy exits · 30 days

PJSC Rostelecom

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
7
0.68% of its addresses · 30 days
Spread
3 of 4
/24s with at least one exit
Providers
21
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

235 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
178.34.67.0/2405
178.34.64.0/2401
178.34.66.0/2401

Proxy providers listing exits

  • 711Proxy
  • Ake.net
  • B2Proxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • CliProxy
  • DataImpulse
  • Decodo
  • FlashProxy
  • FloppyData
  • GloryCloud
  • IPFly
  • IPPeak
  • Novada
  • ProxyRack
  • ProxyWing
  • PuraRoute
  • StrikeProxy
  • Thordata
  • ThunderProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
178.34.64.0/19
since Aug 2023
AS12389Residential22
3 always on
PJSC Rostelecom
via Krasnodar, Russia

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
178.34.0.0 - 178.34.151.25538,912RU-RTK-20100121PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PAMar 6, 2015abuse@rt.ru
└ 178.34.0.0/1732,768Rostelecom_South_RegionKrasnodar, RussiaSUB-ALLOCATED PAJul 16, 2024abuse@rt.ru
via RU-RTK-20100121

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 2023
Current origin since
Mar 2023 · 3.6 yr
Origin networks
1