Data as of Nov 10, 2026

178.68.90.0/24

37 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
37
14% of its addresses · 30 days
Always-on exits
3
8.1% of its exits
Providers
40
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

2.5K observations

Proxy providers listing exits

  • 711Proxy
  • Ake.net
  • BartProxies
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • Decodo
  • EnigmaProxy
  • FLEETPROXY
  • GSocks
  • Geonix
  • GonzoProxy
  • IPFly
  • IPPeak
  • Infatica
  • LemonLabs
  • LemonPrime
  • MangoProxy
  • MoMoProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • Proxio
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyRack
  • Proxyma
  • PuraRoute
  • RainProxy
  • RoamProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_PREMIUM

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.68.64.0/1816,384RU-AVANGARD-DSLOJSC "North-West Telecom"ASSIGNED PANov 15, 2013abuse@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.68.64.0/18

Routing history

Pattern
Stable
First seen
Dec 2013
Current origin since
Jul 2017 · 9.3 yr
Origin networks
2
Last change of origin
Jul 2017
Recorded history

History

Handoffs
1