Data as of Nov 10, 2026

5.34.2.0/23

11 residential-proxy exits · 30 days

Kar-Tel LLC

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

Residential-proxy exits

Proxy exits
11
2.1% of its addresses · 30 days
Spread
2 of 2
/24s with at least one exit
Providers
23
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

186 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
5.34.2.0/2407
5.34.3.0/2404

Proxy providers listing exits

  • 711Proxy
  • 911Proxy
  • ASHBURNPROXIES
  • BestProxy
  • Byteful
  • FastProxy
  • Geonix
  • Infatica
  • LUMIPROXY
  • LemonBright
  • MangoProxy
  • NSocks
  • NiuProxy
  • NodeProxy
  • NovaProxy
  • Proxy-Seller
  • ProxyRack
  • RainProxy
  • Shifter
  • Smartproxy
  • ThunderProxy
  • VitalExclusive
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
5.34.0.0/17
since Nov 2022
AS21299Residential5,957
1,410 always on
Kar-Tel LLC

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
5.34.0.0/1732,768KZ-IPNET-KAR-TEL-20120510Kar-Tel LLC (ORG-KL166-RIPE) · KZALLOCATED PAMay 10, 2012ripe-kartel-mobile@beeline.kz
└ 5.34.0.0/221,024KZ-TNSPLUS-FTTBFTTB KaragandaASSIGNED PAJul 2, 2012ripe-kartel-mobile@beeline.kz
via KZ-IPNET-KAR-TEL-20120510

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
May 2023
Current origin since
May 2023 · 3.5 yr
Origin networks
1