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

178.68.188.0/23

30 residential-proxy exits · 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
30
5.9% of its addresses · 30 days
Spread
2 of 2
/24s with at least one exit
Providers
30
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

1.1K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
178.68.189.0/24016
178.68.188.0/24014

Proxy providers listing exits

  • 711Proxy
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • Decodo
  • EZProxies
  • FlexyProxies
  • GSocks
  • Geonix
  • Geonode
  • GonzoProxy
  • IPFly
  • IPPeak
  • Infatica
  • LemonLabs
  • LemonPrime
  • MangoProxy
  • Maskify
  • NodeProxy
  • NovaProxy
  • Proxio
  • Proxy-Seller
  • Proxy4U
  • ProxyGeo
  • PuraRoute
  • RainProxy
  • Shifter
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
178.64.0.0/13
since Oct 2018
AS12389Residential67,800
2,403 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.68.188.0/23512RU-AVANGARD-DSLPJSC RostelecomASSIGNED PAApr 19, 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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Covering aggregate above, the prefix's own history below

178.68.128.0/17

Routing history

Pattern
Stable
First seen
Dec 2010
Current origin since
May 2017 · 9.5 yr
Origin networks
2
Last change of origin
May 2017
Recorded history

History

Handoffs
1