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

178.22.168.0/21

110 residential-proxy exits · 30 days

JSC Transtelecom

Announcement
this exact prefix
RPKI valid
Announced by
AS41798
Type
Residential

Residential-proxy exits

Proxy exits
110
5.4% of its addresses · 30 days
Always-on exits
9
8.2% of its exits
Spread
8 of 8
/24s with at least one exit
Providers
87
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

33K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
178.22.170.0/24218
178.22.172.0/2429
178.22.173.0/24124
178.22.169.0/24116
178.22.168.0/24115
178.22.174.0/24112
178.22.171.0/2418
178.22.175.0/2408

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 911Proxy
  • ASHBURNPROXIES
  • Ake.net
  • AnyIP
  • BartProxies
  • BestProxy
  • BirdProxies
  • BottingTools
  • Bright Data
  • ByteProxies
  • Byteful
  • CROXY
  • CatProxies
  • CliProxy
  • DataImpulse
  • Decodo
  • EVOPROXY
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • GSocks
  • Geonix
  • Geonode
  • GloryCloud
  • GonzoProxy
  • HideProxy
  • HydraProxy
  • IPFly
  • IPOasis
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • Kookey
  • LUMIPROXY
  • LemonBright
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • MangoProxy
  • MoMoProxy
  • NSocks
  • NextProxy
  • NiuProxy
  • NodeMaven
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYSCRAPE
  • ProxiesVision
  • Proxiware
  • Proxmint
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • ProxyWing
  • Proxyma
  • PuraRoute
  • RH7Proxy
  • RainProxy
  • RapidProxy
  • ResiProxies
  • RoamProxy
  • RolaProxy
  • Shifter
  • Smartproxy
  • StrikeProxy
  • SwiftProxy
  • TalorData
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VibeProxies
  • VitalData
  • VitalExclusive
  • VitalProxy
  • ZENPROXY_PREMIUM

Announcements

Nesting

More-specifics by size

Sized by addresses, colored by each announcement's type. Click a tile with children to zoom in, a leaf to open it.
More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
178.22.168.0/24
since May 2010
AS41798Residential15
1 always on
JSC Transtelecom
178.22.169.0/24
since May 2010
AS41798Residential16
1 always on
JSC Transtelecom
178.22.170.0/24
since Oct 2022
AS41798Residential18
2 always on
JSC Transtelecom
178.22.171.0/24
since May 2017
AS41798Residential8
1 always on
JSC Transtelecom
178.22.172.0/24
since Jan 2019
AS41798Residential9
2 always on
JSC Transtelecom
178.22.173.0/24
since Jan 2019
AS41798Residential24
1 always on
JSC Transtelecom
178.22.174.0/24
since Jul 2017
AS41798Residential12
1 always on
JSC Transtelecom
178.22.175.0/24
since Feb 2022
AS41798Residential8JSC 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.168.0/24256TTC_pool_for_Corp_customersunknownASSIGNED PAMar 18, 2019azelkhanov@rambler.ru
via KZ-TRANSTELECOM-20100409
└ 178.22.169.0/24256TTC_pool_for_Corp_customersunknownASSIGNED PAMar 18, 2019azelkhanov@rambler.ru
via KZ-TRANSTELECOM-20100409
└ 178.22.170.0/24256NAT_pool_AstanaTranstelecom KazakhstanASSIGNED PANov 17, 2011azelkhanov@rambler.ru
via KZ-TRANSTELECOM-20100409
└ 178.22.171.0/24256PPPoE_AstanaTranstelecom KazakhstanASSIGNED PANov 17, 2011azelkhanov@rambler.ru
via KZ-TRANSTELECOM-20100409
└ 178.22.172.0/24256TTC_pool_for_Corp_customersTranstelecom KazakhstanASSIGNED PANov 17, 2011azelkhanov@rambler.ru
via KZ-TRANSTELECOM-20100409
└ 178.22.173.0/24256TTC_networkTranstelecom KazakhstanASSIGNED PANov 17, 2011azelkhanov@rambler.ru
via KZ-TRANSTELECOM-20100409
└ 178.22.174.0/24256NAT_pool_AktobeunknownASSIGNED PANov 17, 2011azelkhanov@rambler.ru
via KZ-TRANSTELECOM-20100409
└ 178.22.175.0/24256PPPoE_AktobeTranstelecom 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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Feb 2012
Current origin since
Nov 2021 · 5.0 yr
Origin networks
1