Data as of Nov 10, 2026

178.34.128.0/20

514 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
514
13% of its addresses · 30 days
Always-on exits
111
22% of its exits
Spread
3 of 16
/24s with at least one exit
Providers
49
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

379K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
178.34.136.0/2457256
178.34.137.0/2453256
178.34.139.0/2412

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 9Proxy
  • Ake.net
  • AnyIP
  • BirdProxies
  • BottingTools
  • Bright Data
  • ByteProxies
  • Byteful
  • CoreProxy
  • DataImpulse
  • Decodo
  • Evomi
  • FlashProxy
  • FloppyData
  • Geonode
  • GloryCloud
  • GoProxies
  • GonzoProxy
  • IPFly
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • Kookey
  • LightningProxies
  • MarsProxies
  • Maskify
  • NSocks
  • Novada
  • Oxylabs
  • PacketStream
  • PrivateProxy
  • Proxiware
  • Proxy-Cheap
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Proxying
  • Proxyma
  • Shifter
  • Smartproxy
  • StrikeProxy
  • Thordata
  • ThunderProxy
  • VitalExclusive
  • Webshare

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.128.0/204,096BROADBAND_INTERNET_ACCESSBroadband Internet Access for Customers RostelecomSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via RU-RTK-20100121
└ 178.34.139.0/24256Rostelecom_netunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via BROADBAND_INTERNET_ACCESS
└ 178.34.140.0/24256Rostelecom_netunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via BROADBAND_INTERNET_ACCESS

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

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Aug 2014
Current origin since
Aug 2014 · 12 yr
Origin networks
1