Data as of Nov 16, 2026

178.34.111.0/24

50 residential-proxy exits · 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
50
20% of its addresses · 30 days
Providers
49
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

1.2K observations

Proxy providers listing exits

  • 711Proxy
  • Ake.net
  • B2Proxy
  • BirdProxies
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CatProxies
  • DataImpulse
  • Datarama
  • Decodo
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FloppyData
  • Geonode
  • GhostConnect
  • HPROXY
  • HideProxy
  • IPFly
  • IPPeak
  • InfiniteProxies
  • KindProxy
  • LudaxProxy
  • MoMoProxy
  • NextProxy
  • NovaProxy
  • Novada
  • PROXYON
  • PROXYSCRAPE
  • PrivateProxy
  • ProxiesVision
  • Proxio
  • Proxiware
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • PuraRoute
  • Q2IP
  • RainProxy
  • RapidProxy
  • ResiProxies
  • Shifter
  • Smartproxy
  • VantageProxies
  • ZENPROXY_LITE
  • ZENPROXY_PREMIUM

Registrations in this block

The registry's network records over this block, widest first, each 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
└ 178.34.96.0/198,192Rostelecom_South_RegionKrasnodar, RussiaASSIGNED PAJul 16, 2024abuse@rt.ru
via Rostelecom_South_Region

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 178.34.96.0/19

178.34.96.0/19

Routing history

Pattern
Stable
First seen
Nov 2015
Current origin since
Oct 2021 · 5.1 yr
Origin networks
1