Data as of Nov 12, 2026

82.115.47.0/24

256 residential-proxy exits · 30 days

JSC Transtelecom

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential
Risk
10 / 100 · Low
Shared address · Proxy exits nearby

Residential-proxy exits

Proxy exits
256
100% of its addresses · 30 days
Always-on exits
129
50% of its exits
Providers
29
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

208K observations

Proxy providers listing exits

  • 711Proxy
  • AnyIP
  • BirdProxies
  • BottingTools
  • Bright Data
  • ByteProxies
  • Byteful
  • DataImpulse
  • Decodo
  • Evomi
  • FlashProxy
  • Geonode
  • GoProxies
  • GonzoProxy
  • IPRoyal
  • Infatica
  • Kookey
  • LemonBright
  • Maskify
  • Oxylabs
  • PacketStream
  • Proxy-Seller
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • StrikeProxy
  • Thordata
  • ThunderProxy
  • Webshare

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
82.115.44.0/22
since Dec 2024
AS41798Residential513
269 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
82.115.44.0/221,024KZ-TRANSTELECOM-20040107JSC Transtelecom (ORG-TA238-RIPE) · KZALLOCATED PADec 30, 2024azelkhanov@rambler.ru
└ 82.115.47.0/24256TTC_CGNAT_RES_POOLunknownASSIGNED PAOct 29, 2026azelkhanov@rambler.ru
via KZ-TRANSTELECOM-20040107

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
Aug 2025
Current origin since
Aug 2025 · 1.3 yr
Origin networks
1