Data as of Nov 12, 2026

91.185.25.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 13, 2026 – Nov 11, 2026

Exits seen per day

84 observations

Proxy providers listing exits

  • 2Captcha
  • BestProxy
  • BirdProxies
  • ByteProxies
  • FastProxy
  • GonzoProxy
  • Infatica
  • LemonBright
  • MangoProxy
  • NSocks
  • Proxy-Seller
  • ProxyWing
  • Proxyma
  • RainProxy
  • Shifter
  • Smartproxy
  • Thordata
  • ThunderProxy
  • VitalExclusive
  • ZENPROXY_PREMIUM

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.25.0/24256TTC_pool_for_Corp_customersunknownASSIGNED PAMar 31, 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
Apr 2008
Current origin since
Apr 2008 · 19 yr
Origin networks
1