LAYER3 INTEL
Get started
Sign in
Data as of Nov 12, 2026

178.34.55.0/24

65 residential-proxy exits · 30 days

PJSC Rostelecom

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

Residential-proxy exits

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

Exits seen per day

1.9K observations

Proxy providers listing exits

  • 711Proxy
  • 9Proxy
  • Ake.net
  • AnyIP
  • B2Proxy
  • BartProxies
  • BirdProxies
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • DataImpulse
  • Datarama
  • Decodo
  • EVOPROXY
  • EZProxies
  • Evomi
  • FastProxy
  • Geonode
  • GhostConnect
  • GloryCloud
  • HideProxy
  • IPFly
  • IPMUSK
  • IPPeak
  • InfiniteProxies
  • KindProxy
  • LudaxProxy
  • Maskify
  • MoMoProxy
  • NextProxy
  • NovProxy
  • NovaProxy
  • Novada
  • ProxiesVision
  • Proxio
  • Proxiware
  • Proxmint
  • Proxy4U
  • ProxyGeo
  • PuraRoute
  • RainProxy
  • RapidProxy
  • RoamProxy
  • SwiftProxy
  • TORCHPROXIES_X
  • TrueProxies
  • VantageProxies
  • YumiProxy

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

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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Who has announced 178.34.0.0/18

178.34.0.0/18

Routing history

Pattern
Stable
First seen
Mar 2013
Current origin since
Jan 2022 · 4.8 yr
Origin networks
2
Last change of origin
Dec 2015
Recorded history

History

Handoffs
1