Data as of Nov 10, 2026

91.185.0.0/19

512 residential-proxy exits · 30 days

JSC Transtelecom

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential
>99% of it

Residential-proxy exits

Proxy exits
512
6.3% of its addresses · 30 days
Always-on exits
96
19% of its exits
Spread
30 of 32
/24s with at least one exit
Providers
106
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

264K observations
  • Residential
  • Business

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 911Proxy
  • 9Proxy
  • ASHBURNPROXIES
  • Ake.net
  • AnyIP
  • BartProxies
  • BestProxy
  • BirdProxies
  • BottingTools
  • Bright Data
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • CoreProxy
  • DataImpulse
  • Datarama
  • Decodo
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FLEETPROXY
  • FastProxy
  • FlashProxy
  • GSocks
  • GeekProxy
  • Geonix
  • Geonode
  • GhostConnect
  • GloryCloud
  • GoProxies
  • GonzoProxy
  • HideProxy
  • HydraProxy
  • IPFly
  • IPOasis
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • Kookey
  • LUMIPROXY
  • LemonBright
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • MagneticProxy
  • MangoProxy
  • MarsProxies
  • Maskify
  • MoMoProxy
  • NSocks
  • NextProxy
  • NiuProxy
  • NodeMaven
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYSCRAPE
  • PSBProxy
  • PacketStream
  • PrivateByte
  • PrivateProxy
  • Proxies.fo
  • ProxiesVision
  • Proxio
  • Proxiware
  • Proxmint
  • Proxy-Cheap
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • ProxyWing
  • Proxyma
  • PuraRoute
  • Q2IP
  • RH7Proxy
  • RainProxy
  • RapidProxy
  • ResiProxies
  • RoamProxy
  • Shifter
  • Smartproxy
  • SpyderProxy
  • StrikeProxy
  • SwiftProxy
  • TalorData
  • Thordata
  • ThunderProxy
  • VProxy
  • VantageProxies
  • VibeProxies
  • VitalData
  • VitalExclusive
  • VitalProxy
  • Webshare
  • 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

Arrived
PrefixOriginTypeProxy exitsHolderRPKI
91.185.1.0/24
since Jun 2009
AS41798Residential12
1 always on
JSC Transtelecom
91.185.2.0/24
since Jun 2009
AS41798Residential4JSC Transtelecom
91.185.3.0/24
since Jun 2009
AS41798Residential14JSC Transtelecom
91.185.4.0/24
since Dec 2019
AS41798Residential6
1 always on
JSC Transtelecom
91.185.5.0/24
since Feb 2019
AS41798Residential7
2 always on
JSC Transtelecom
91.185.6.0/24
since Sep 2018
AS41798Residential8
4 always on
JSC Transtelecom
91.185.7.0/24
since Nov 2021
AS41798Residential15
1 always on
JSC Transtelecom
91.185.8.0/24
since Jan 2007
AS41798Residential8JSC Transtelecom
91.185.9.0/24
since May 2017
AS41798Residential7
1 always on
JSC Transtelecom
91.185.10.0/24
since Jan 2023
AS41798Residential256
73 always on
JSC Transtelecom
91.185.12.0/24
since Apr 2007
AS41798Residential6JSC Transtelecom
91.185.13.0/24
since Jan 2020
AS41798Residential13JSC Transtelecom
91.185.14.0/24
since Jan 2020
AS41798ResidentialJSC Transtelecom
91.185.15.0/24
since Aug 2007
AS41798Residential17
1 always on
JSC Transtelecom
91.185.16.0/24
since Jan 2020
AS41798Residential14
2 always on
JSC Transtelecom
91.185.17.0/24
since Dec 2007
AS41798Residential10JSC Transtelecom
91.185.18.0/24
since Jan 2020
AS41798Residential5JSC Transtelecom
91.185.19.0/24
since Dec 2007
AS41798Residential15
2 always on
JSC Transtelecom
91.185.20.0/24
since Jan 2020
AS41798Residential19JSC Transtelecom
91.185.22.0/24
since Feb 2008
AS41798Residential1JSC Transtelecom
91.185.23.0/24
since Feb 2008
AS41798Residential7
1 always on
JSC Transtelecom
91.185.24.0/24
since Jan 2020
AS41798Residential11
1 always on
JSC Transtelecom
91.185.25.0/24
since Apr 2008
AS41798Residential1JSC Transtelecom
91.185.26.0/24
since Jan 2020
AS41798Residential11
2 always on
JSC Transtelecom
91.185.27.0/24
since Apr 2008
AS41798Residential10
2 always on
JSC Transtelecom
91.185.28.0/24
since Nov 2022
AS41798ResidentialJSC Transtelecom
91.185.29.0/24
since Jan 2020
AS41798Residential6JSC Transtelecom
91.185.30.0/24
since Jan 2020
AS41798Residential12JSC Transtelecom
91.185.31.0/24
since Jan 2020
AS41798Residential12
1 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.0.0/24256TTC_pool_for_New_NATTranstelecom Kazakhstan NetworkASSIGNED PADec 15, 2011azelkhanov@rambler.ru
via KZ-TRANSTELECOM-20061019
└ 91.185.1.0/24256TTC_pool_for_Corp_customersTranstelecom Kazakhstan NetworkASSIGNED PADec 17, 2011azelkhanov@rambler.ru
via KZ-TRANSTELECOM-20061019
└ 91.185.2.0/24256TTC_pool_for_Corp_customersTranstelecom Kazakhstan NetworkASSIGNED PADec 17, 2011azelkhanov@rambler.ru
via KZ-TRANSTELECOM-20061019
└ 91.185.3.0/24256TTC_pool_for_Corp_customersTranstelecom Kazakhstan NetworkASSIGNED PADec 15, 2011azelkhanov@rambler.ru
via KZ-TRANSTELECOM-20061019
└ 91.185.4.0/24256TTC_pool_for_Corp_customersTranstelecom Kazakhstan NetworkASSIGNED PADec 17, 2011azelkhanov@rambler.ru
via KZ-TRANSTELECOM-20061019
└ 91.185.5.0/24256TTC_pool_for_RoutersTranstelecom Kazakhstan NetworkASSIGNED PADec 17, 2011azelkhanov@rambler.ru
via KZ-TRANSTELECOM-20061019
└ 91.185.6.0/24256TTC_pool_for_Corp_customersTranstelecom Kazakhstan NetworkASSIGNED PADec 17, 2011azelkhanov@rambler.ru
via KZ-TRANSTELECOM-20061019
└ 91.185.7.0/24256TTC_pool_for_Corp_customersTranstelecom Kazakhstan NetworkASSIGNED PADec 17, 2011azelkhanov@rambler.ru
via KZ-TRANSTELECOM-20061019
└ 91.185.8.0/2664MID_RKMinister of Foreign Affairs of KazakhstanASSIGNED PAJan 13, 2021azelkhanov@rambler.ru
via KZ-TRANSTELECOM-20061019
└ 91.185.9.0/24256TTC_pool_for_Corp_customersTranstelecom Kazakhstan NetworkASSIGNED PAJan 16, 2007azelkhanov@rambler.ru
via KZ-TRANSTELECOM-20061019
└ 91.185.10.0/24256NAT_pool_AlmatyTranstelecom Kazakhstan NetworkASSIGNED PANov 18, 2011azelkhanov@rambler.ru
via KZ-TRANSTELECOM-20061019
└ 91.185.11.0/24256COD_Cloud_AlmatyTranstelecom Kazakhstan NetworkASSIGNED PANov 18, 2011azelkhanov@rambler.ru
via KZ-TRANSTELECOM-20061019
└ 91.185.12.0/24256TTC_pool_for_Corp_customersTranstelecom Kazakhstan NetworkASSIGNED PANov 18, 2011azelkhanov@rambler.ru
via KZ-TRANSTELECOM-20061019
└ 91.185.13.0/24256TTC_pool_for_Corp_customersunknownASSIGNED PAMar 18, 2019azelkhanov@rambler.ru
via KZ-TRANSTELECOM-20061019
└ 91.185.14.0/24256TTC_pool_for_Corp_customersTranstelecom Kazakhstan NetworkASSIGNED PADec 15, 2011azelkhanov@rambler.ru
via KZ-TRANSTELECOM-20061019
└ 91.185.15.0/24256TTC_pool_for_Corp_customersTranstelecom Kazakhstan NetworkASSIGNED PAJul 26, 2007azelkhanov@rambler.ru
via KZ-TRANSTELECOM-20061019
└ 91.185.16.0/24256TTC_pool_for_Corp_customersTranstelecom Kazakhstan NetworkASSIGNED PADec 15, 2011azelkhanov@rambler.ru
via KZ-TRANSTELECOM-20061019
└ 91.185.17.0/24256TTC_pool_for_Corp_customersunknownASSIGNED PAMar 18, 2019azelkhanov@rambler.ru
via KZ-TRANSTELECOM-20061019
└ 91.185.18.0/24256TTC_pool_for_Corp_customersunknownASSIGNED PAMar 18, 2019azelkhanov@rambler.ru
via KZ-TRANSTELECOM-20061019
└ 91.185.19.0/24256TTC_pool_for_Corp_customersunknownASSIGNED PAMar 18, 2019azelkhanov@rambler.ru
via KZ-TRANSTELECOM-20061019
└ 91.185.20.0/24256TTC_pool_for_Corp_customersunknownASSIGNED PAMar 18, 2019azelkhanov@rambler.ru
via KZ-TRANSTELECOM-20061019
└ 91.185.21.0/24256TTC_pool_for_Corp_customersunknownASSIGNED PAMar 18, 2019azelkhanov@rambler.ru
via KZ-TRANSTELECOM-20061019
└ 91.185.22.0/24256AO_NK_KTZHTTC- for KTZHASSIGNED PAJan 25, 2008azelkhanov@rambler.ru
via KZ-TRANSTELECOM-20061019
└ 91.185.23.0/24256TTC_pool_for_Corp_customers_AktobeKazakhstan Transtelecom NetworkASSIGNED PAJan 31, 2008azelkhanov@rambler.ru
via KZ-TRANSTELECOM-20061019
└ 91.185.24.0/24256TTC_pool_for_Corp_customersTranstelecom KazkhstanASSIGNED PAFeb 19, 2008azelkhanov@rambler.ru
via KZ-TRANSTELECOM-20061019
└ 91.185.25.0/24256TTC_pool_for_Corp_customersunknownASSIGNED PAMar 31, 2008azelkhanov@rambler.ru
via KZ-TRANSTELECOM-20061019
└ 91.185.26.0/24256TTC_pool_for_Corp_customersTranstelecom Kazakhstan NetworkASSIGNED PAMar 31, 2008azelkhanov@rambler.ru
via KZ-TRANSTELECOM-20061019
└ 91.185.27.0/24256TTC_pool_for_Corp_customersTranstelecom Kazakhstan NetworkASSIGNED PAApr 14, 2008azelkhanov@rambler.ru
via KZ-TRANSTELECOM-20061019
└ 91.185.28.0/24256PPPoE_AlmatyunknownASSIGNED PAApr 22, 2008azelkhanov@rambler.ru
via KZ-TRANSTELECOM-20061019
└ 91.185.29.0/24256TTC-NETunknownASSIGNED PAApr 28, 2008azelkhanov@rambler.ru
via KZ-TRANSTELECOM-20061019
└ 91.185.30.0/24256TTC_pool_for_Corp_customersTranstelecom Kazakhstan NetworkASSIGNED PAMay 16, 2008azelkhanov@rambler.ru
via KZ-TRANSTELECOM-20061019
└ 91.185.31.0/24256Transtelecom_IPFor Ethernet customers TTCASSIGNED PAJul 1, 2008azelkhanov@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.

Composition

The types across the prefix's announced space, by addresses.

Announced space

Address share

Announced space

Types across the prefix

8,192 addresses
TypeAddressesShareRanges
Residential8,128>99%32
Business640.78%1

Network & registry

Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Jan 2012
Current origin since
Jan 2012 · 15 yr
Origin networks
1