Data as of Nov 11, 2026

91.185.22.0/24

1 residential-proxy exit · 30 days

JSC Transtelecom

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

Residential-proxy exits

Proxy exits
1
0.39% of its addresses · 30 days
Providers
20
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

49 observations

Proxy providers listing exits

  • 9Proxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • Evomi
  • FlashProxy
  • Geonode
  • GonzoProxy
  • Infatica
  • InfiniteProxies
  • MangoProxy
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • Shifter
  • Thordata
  • VitalExclusive

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.22.0/24256AO_NK_KTZHTTC- for KTZHASSIGNED PAJan 25, 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.

Network & registry

Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Feb 2008
Current origin since
Feb 2008 · 19 yr
Origin networks
2
Last change of origin
Aug 2016
Recorded history

History

Handoffs
1