Data as of Nov 11, 2026

91.185.8.0/24

8 residential-proxy exits · 30 days

JSC Transtelecom

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

Residential-proxy exits

Proxy exits
8
3.1% of its addresses · 30 days
Providers
46
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

1.6K observations
  • Residential
  • Business

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • Ake.net
  • AnyIP
  • BartProxies
  • BestProxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • CoreProxy
  • DataImpulse
  • EnigmaProxy
  • FastProxy
  • FlashProxy
  • GSocks
  • Geonode
  • GonzoProxy
  • IPOasis
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • Kookey
  • LemonBright
  • MangoProxy
  • NSocks
  • NodeProxy
  • Novada
  • PacketStream
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Proxyma
  • RainProxy
  • Shifter
  • Smartproxy
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VibeProxies
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
91.185.0.0/19
since Jan 2012
AS41798Residential515
95 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.8.0/2664MID_RKMinister of Foreign Affairs of KazakhstanASSIGNED PAJan 13, 2021azelkhanov@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

256 addresses
TypeAddressesShareRanges
Residential19275%1
Business6425%1

Network & registry

Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Jan 2007
Current origin since
Jan 2007 · 20 yr
Origin networks
1