Data as of Nov 10, 2026

178.66.158.0/24

256 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
256
100% of its addresses · 30 days
Always-on exits
133
52% of its exits
Providers
42
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

223K observations

Proxy providers listing exits

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

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
178.64.0.0/13
since Oct 2018
AS12389Residential68,006
3,842 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.64.0.0/13524,288RU-RTK-20100105PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PAJan 5, 2010abuse@rt.ru
└ 178.66.158.0/23512RU-RTK-NAT-SZLPJSC "Rostelecom" North-West RegionASSIGNED PANov 11, 2021abuse@rt.ru
via RU-RTK-20100105

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.66.0.0/16

Routing history

Pattern
Stable
First seen
Nov 2010
Current origin since
Oct 2018 · 8.1 yr
Origin networks
2
Last change of origin
Oct 2018
Recorded history

History

Handoffs
1