Data as of Nov 10, 2026

212.76.2.0/24

5 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
5
2.0% of its addresses · 30 days
Always-on exits
1
20% of its exits
Providers
33
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

379 observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • BestProxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • FastProxy
  • FlashProxy
  • GonzoProxy
  • HydraProxy
  • IPOasis
  • Infatica
  • LemonBright
  • MangoProxy
  • NSocks
  • NodeMaven
  • NovaProxy
  • Novada
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyWing
  • Proxyma
  • RainProxy
  • Shifter
  • Smartproxy
  • Thordata
  • ThunderProxy
  • VitalData
  • VitalExclusive
  • VitalProxy
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
212.76.0.0/19
since Sep 2022
AS21299Mobile46
7 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
212.76.0.0/198,192KZ-IPNET-KAR-TEL-980928Kar-Tel LLC (ORG-KL166-RIPE) · KZALLOCATED PA—ripe-kartel-mobile@beeline.kz
└ 212.76.2.0/24256FTTB_KaragandaFTTB KaragandaASSIGNED PAOct 28, 2011ripe-kartel-mobile@beeline.kz
via KZ-IPNET-KAR-TEL-980928

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
Oct 2011
Current origin since
Apr 2014 · 13 yr
Origin networks
2
Last change of origin
Apr 2014
Recorded history

History

Handoffs
1