Data as of Nov 12, 2026

178.22.171.0/24

8 residential-proxy exits · 30 days

JSC Transtelecom

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
8
3.1% of its addresses · 30 days
Always-on exits
1
13% of its exits
Providers
41
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

9.7K observations

Proxy providers listing exits

  • 711Proxy
  • 911Proxy
  • ASHBURNPROXIES
  • Ake.net
  • AnyIP
  • BestProxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • Evomi
  • FlashProxy
  • GSocks
  • Geonode
  • GonzoProxy
  • IPOasis
  • Infatica
  • LUMIPROXY
  • LemonBright
  • LightningProxies
  • MangoProxy
  • NSocks
  • NiuProxy
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyWing
  • Proxyma
  • RainProxy
  • Shifter
  • Smartproxy
  • Thordata
  • ThunderProxy
  • VibeProxies
  • VitalExclusive
  • VitalProxy
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
178.22.168.0/21
since Nov 2021
AS41798Residential110
9 always on
JSC Transtelecom

Registrations in this block

The registry's network records over the announcement: those covering it, widest first, then every record inside it, under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
178.22.168.0/212,048KZ-TRANSTELECOM-20100409JSC Transtelecom (ORG-TA238-RIPE) · KZALLOCATED PAApr 9, 2010azelkhanov@rambler.ru
└ 178.22.171.0/24256PPPoE_AstanaTranstelecom KazakhstanASSIGNED PANov 17, 2011azelkhanov@rambler.ru
via KZ-TRANSTELECOM-20100409

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

Summary

Routing history

Pattern
Stable
First seen
May 2010
Current origin since
May 2017 · 9.5 yr
Origin networks
1