Data as of Nov 10, 2026

2.57.97.0/24

256 residential-proxy exits · 30 days

JSC Transtelecom

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

Residential-proxy exits

Proxy exits
256
100% of its addresses · 30 days
Always-on exits
244
95% of its exits
Providers
27
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

293K observations

Proxy providers listing exits

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

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
2.57.96.0/221,024KZ-TRANSTELECOM-20190319JSC Transtelecom (ORG-TA238-RIPE) · KZALLOCATED PAMar 19, 2019azelkhanov@rambler.ru
└ 2.57.97.0/24256NAT_AlmatyunknownASSIGNED PAApr 2, 2019azelkhanov@rambler.ru
via KZ-TRANSTELECOM-20190319

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

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Apr 2019
Current origin since
Apr 2019 · 7.6 yr
Origin networks
1