Data as of Nov 21, 2026

178.234.11.0/24

25 residential-proxy exits · 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
25
9.8% of its addresses · 30 days
Always-on exits
7
28% of its exits
Providers
66
selling exits here
Oct 22, 2026 – Nov 20, 2026

Exits seen per day

6.9K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 9HTTP
  • AETHYN_ELITE
  • ASHBURNPROXIES
  • Ake.net
  • B2Proxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CYBERYOZH
  • CatProxies
  • CliProxy
  • EZProxies
  • EnigmaProxy
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • FastProxy
  • FlashProxy
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • Geonix
  • Geonode
  • GonzoProxy
  • HASDATA
  • HELODATA
  • HideProxy
  • HydraProxy
  • IPFly
  • IPPeak
  • Infatica
  • InfiniteProxies
  • LOKIPROXY
  • LemonPrime
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • NSocks
  • NodeProxy
  • NovaProxy
  • PROXIWARE_ECO
  • PROXYLANE
  • PROXYSCRAPE
  • PrivateByte
  • ProxiesVision
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • Proxyma
  • PuraRoute
  • Q2IP
  • RainProxy
  • ResiProxies
  • SOTAPROXY
  • Shifter
  • Smartproxy
  • VantageProxies
  • VitalData
  • VitalExclusive
  • VitalProxy
  • YumiProxy
  • ZENPROXY_LITE
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
178.234.0.0/17
since Jun 2010
AS8570Residential7,145
27 always on
PJSC Rostelecom
178.234.0.0/16
since Jun 2010
AS8570Residential13,953
27 always on
PJSC Rostelecom

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
178.234.0.0/1665,536RU-RTK-20100510PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PAMay 10, 2010abuse@rt.ru
└ 178.234.0.0 - 178.234.175.25545,056MACROREGIONAL_CENTEROJSC Rostelecom, Lipetsk branchASSIGNED PAMay 28, 2010abuse@rt.ru
via RU-RTK-20100510

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

178.234.0.0/18

Routing history

Pattern
Stable
First seen
Jun 2010
Current origin since
Jun 2010 · 16 yr
Origin networks
1