Data as of Nov 10, 2026

91.185.2.0/24

4 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
4
1.6% of its addresses · 30 days
Providers
34
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

864 observations

Proxy providers listing exits

  • 711Proxy
  • 911Proxy
  • ASHBURNPROXIES
  • BestProxy
  • BirdProxies
  • BottingTools
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FastProxy
  • GSocks
  • Geonix
  • IPPeak
  • Infatica
  • LemonBright
  • MangoProxy
  • NSocks
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Proxyma
  • RainProxy
  • Shifter
  • Smartproxy
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
91.185.0.0/19
since Jan 2012
AS41798Residential512
96 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
91.185.0.0/198,192KZ-TRANSTELECOM-20061019JSC Transtelecom (ORG-TA238-RIPE) · KZALLOCATED PAOct 19, 2006azelkhanov@rambler.ru
└ 91.185.2.0/24256TTC_pool_for_Corp_customersTranstelecom Kazakhstan NetworkASSIGNED PADec 17, 2011azelkhanov@rambler.ru
via KZ-TRANSTELECOM-20061019

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
Jun 2009
Current origin since
Jun 2009 · 17 yr
Origin networks
1