Data as of Nov 10, 2026

5.76.0.0/16

16,796 residential-proxy exits · 30 days

JSC Kazakhtelecom

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential

Residential-proxy exits

Proxy exits
16,796
26% of its addresses · 30 days
Always-on exits
260
1.5% of its exits
Spread
244 of 256
/24s with at least one exit
Providers
125
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

1.2M observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 911Proxy
  • 9Proxy
  • ASHBURNPROXIES
  • Ake.net
  • AnyIP
  • B2Proxy
  • BartProxies
  • BestProxy
  • BirdProxies
  • BlurPath
  • BottingTools
  • Bright Data
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • DataImpulse
  • Datarama
  • Decodo
  • EVOPROXY
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FLEETPROXY
  • FastProxy
  • FlashProxy
  • FuseProxy
  • GSocks
  • GeekProxy
  • Geonix
  • Geonode
  • GhostConnect
  • GloryCloud
  • GoProxies
  • GonzoProxy
  • HPROXY
  • HideProxy
  • HydraProxy
  • IPCola
  • IPFly
  • IPMUSK
  • IPOasis
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • JoyProxy
  • KindProxy
  • KocerRoxy
  • Kookey
  • LUMIPROXY
  • LemonBright
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • LudaxProxy
  • MagneticProxy
  • MangoProxy
  • Maskify
  • MoMoProxy
  • NSocks
  • NextProxy
  • NiuProxy
  • NodeMaven
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYON
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • PSBProxy
  • PacketStream
  • PrivateByte
  • PrivateProxy
  • Proxies.fo
  • ProxiesVision
  • Proxio
  • Proxiware
  • Proxmint
  • Proxy-Seller
  • Proxy302
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • ProxyStyler
  • ProxyWing
  • Proxying
  • Proxyma
  • PuraRoute
  • Q2IP
  • QUANTICDATA
  • RH7Proxy
  • RainProxy
  • RapidProxy
  • RealProxy
  • ResiProxies
  • RoamProxy
  • RolaProxy
  • SPYDERPROXY_BASIC
  • SPYDERPROXY_PREMIUM
  • Shifter
  • Smartproxy
  • StrikeProxy
  • SwiftProxy
  • TalorData
  • Thordata
  • ThunderProxy
  • TrueProxies
  • VProxy
  • VantageProxies
  • VibeProxies
  • VitalData
  • VitalExclusive
  • VitalProxy
  • Webshare
  • YumiProxy
  • ZENPROXY_LITE
  • ZENPROXY_PREMIUM

Announcements

Nesting

More-specifics by size

Sized by addresses, colored by each announcement's type. Click a tile with children to zoom in, a leaf to open it.
More specific

Announcements inside

Arrived
PrefixOriginTypeProxy exitsHolderRPKI
5.76.0.0/21
since Oct 2016
AS9198Residential495
7 always on
JSC Kazakhtelecom
5.76.8.0/21
since Oct 2016
AS9198Residential464
8 always on
JSC Kazakhtelecom
5.76.16.0/21
since Mar 2013
AS9198Residential429
7 always on
JSC Kazakhtelecom
5.76.32.0/21
since Jan 2017
AS9198Residential451
9 always on
JSC Kazakhtelecom
5.76.40.0/21
since Jan 2017
AS9198Residential423
12 always on
JSC Kazakhtelecom
5.76.48.0/21
since Jan 2017
AS9198Residential390
8 always on
JSC Kazakhtelecom
5.76.60.0/22
since Aug 2016
AS9198Residential212
12 always on
JSC Kazakhtelecom
5.76.64.0/22
since Apr 2013
AS9198Residential213
1 always on
JSC Kazakhtelecom
5.76.68.0/22
since Apr 2013
AS9198Residential372
5 always on
JSC Kazakhtelecom
5.76.72.0/22
since Sep 2017
AS9198Residential237
7 always on
JSC Kazakhtelecom
5.76.76.0/22
since Jun 2017
AS9198Residential276
8 always on
JSC Kazakhtelecom
5.76.80.0/22
since Oct 2016
AS9198Residential295
10 always on
JSC Kazakhtelecom
5.76.88.0/22
since Oct 2016
AS9198Residential365
3 always on
JSC Kazakhtelecom
5.76.92.0/22
since Oct 2016
AS9198Residential202
9 always on
JSC Kazakhtelecom
5.76.96.0/22
since Oct 2016
AS9198Residential314
7 always on
JSC Kazakhtelecom
5.76.104.0/22
since Oct 2016
AS9198Residential298
7 always on
JSC Kazakhtelecom
5.76.128.0/22
since Apr 2013
AS9198Residential373
3 always on
JSC Kazakhtelecom
5.76.132.0/22
since Nov 2016
AS9198Residential404JSC Kazakhtelecom
5.76.136.0/22
since Sep 27, 2026
AS9198Residential268
10 always on
JSC Kazakhtelecom
5.76.140.0/22
since Apr 2013
AS9198Residential244
4 always on
JSC Kazakhtelecom
5.76.144.0/21
since Dec 2018
AS9198Residential488
3 always on
JSC Kazakhtelecom
5.76.152.0/21
since Apr 2013
AS9198Residential1,230JSC Kazakhtelecom
5.76.160.0/21
since Sep 2016
AS9198Residential485
12 always on
JSC Kazakhtelecom
5.76.168.0/21
since Oct 2016
AS9198Residential492
20 always on
JSC Kazakhtelecom
5.76.176.0/21
since Sep 2016
AS9198Residential516
19 always on
JSC Kazakhtelecom
5.76.184.0/21
since Dec 2018
AS9198Residential324
9 always on
JSC Kazakhtelecom
5.76.192.0/21
since Dec 2018
AS9198Residential456
3 always on
JSC Kazakhtelecom
5.76.208.0/21
since Dec 2018
AS9198Residential498
3 always on
JSC Kazakhtelecom
5.76.216.0/21
since Dec 2018
AS9198Residential451
9 always on
JSC Kazakhtelecom
5.76.248.0/21
since Dec 2018
AS9198Residential431
4 always on
JSC Kazakhtelecom

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.76.0.0/1665,536KZ-KAZAKTELECOM-20120612JSC Kazakhtelecom (ORG-KDNA1-RIPE) · KZALLOCATED PAJun 12, 2012abuse@telecom.kz
└ 5.76.0.0/212,048GPON_FTTH_SERVICESJSC KazakhtelecomASSIGNED PAAug 7, 2018abuse@telecom.kz
via KZ-KAZAKTELECOM-20120612
└ 5.76.8.0/212,048GPON_FTTH_SERVICESJSC KazakhtelecomASSIGNED PAAug 7, 2018abuse@telecom.kz
via KZ-KAZAKTELECOM-20120612
└ 5.76.16.0/212,048GPON_FTTH_SERVICES_KTJSC KazakhtelecomASSIGNED PAApr 4, 2013abuse@telecom.kz
via KZ-KAZAKTELECOM-20120612
└ 5.76.24.0/212,048GPON_FTTH_SERVICES_KTJSC KazakhtelecomASSIGNED PAMar 18, 2013abuse@telecom.kz
via KZ-KAZAKTELECOM-20120612
└ 5.76.32.0/212,048GPON_FTTH_SERVICES_KTJSC KazakhtelecomASSIGNED PAMar 18, 2013abuse@telecom.kz
via KZ-KAZAKTELECOM-20120612
└ 5.76.40.0/212,048GPON_FTTH_SERVICES_KTJSC KazakhtelecomASSIGNED PAMar 18, 2013abuse@telecom.kz
via KZ-KAZAKTELECOM-20120612
└ 5.76.48.0/212,048GPON_FTTH_SERVICES_KTJSC KazakhtelecomASSIGNED PAMar 18, 2013abuse@telecom.kz
via KZ-KAZAKTELECOM-20120612
└ 5.76.56.0/221,024GPON_FTTH_SERVICESJSC KazakhtelecomASSIGNED PAFeb 7, 2018abuse@telecom.kz
via KZ-KAZAKTELECOM-20120612
└ 5.76.60.0/221,024GPON_FTTH_SERVICESJSC KazakhtelecomASSIGNED PAFeb 7, 2018abuse@telecom.kz
via KZ-KAZAKTELECOM-20120612
└ 5.76.64.0/221,024GPON_FTTH_SERVICESAktauASSIGNED PAJun 1, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20120612
└ 5.76.72.0/221,024GPON_FTTH_SERVICESJSC KazakhtelecomASSIGNED PAJan 8, 2019abuse@telecom.kz
via KZ-KAZAKTELECOM-20120612
└ 5.76.76.0/221,024GPON_FTTH_SERVICESJSC KazakhtelecomASSIGNED PAJan 4, 2019abuse@telecom.kz
via KZ-KAZAKTELECOM-20120612
└ 5.76.80.0/221,024GPON_FTTH_SERVICESJSC KazakhtelecomASSIGNED PAFeb 7, 2018abuse@telecom.kz
via KZ-KAZAKTELECOM-20120612
└ 5.76.88.0/221,024GPON_FTTH_SERVICESJSC KazakhtelecomASSIGNED PAAug 7, 2018abuse@telecom.kz
via KZ-KAZAKTELECOM-20120612
└ 5.76.92.0/221,024GPON_FTTH_SERVICESJSC KazakhtelecomASSIGNED PAAug 7, 2018abuse@telecom.kz
via KZ-KAZAKTELECOM-20120612
└ 5.76.112.0/204,096GPON_FTTH_SERVICESJSC KazakhtelecomASSIGNED PADec 28, 2018abuse@telecom.kz
via KZ-KAZAKTELECOM-20120612
└ 5.76.128.0/221,024GPON_FTTH_SERVICESJSC KazakhtelecomASSIGNED PAJan 4, 2019abuse@telecom.kz
via KZ-KAZAKTELECOM-20120612
└ 5.76.132.0/221,024GPON_FTTH_SERVICESJSC KazakhtelecomASSIGNED PAJan 8, 2019abuse@telecom.kz
via KZ-KAZAKTELECOM-20120612
└ 5.76.136.0/212,048GPON_FTTH_SERVICES_KTJSC KazakhtelecomASSIGNED PAApr 11, 2013abuse@telecom.kz
via KZ-KAZAKTELECOM-20120612
└ 5.76.144.0/212,048GPON_FTTH_SERVICES_KTJSC KazakhtelecomASSIGNED PASep 11, 2013abuse@telecom.kz
via KZ-KAZAKTELECOM-20120612
└ 5.76.152.0/212,048ATRMETROJSC Kazakhtelecom, Atyrau AffiliateASSIGNED PAAug 1, 2012abuse@telecom.kz
via KZ-KAZAKTELECOM-20120612
└ 5.76.160.0/212,048GPON_FTTH_SERVICES_KTJSC KazakhtelecomASSIGNED PAApr 11, 2013abuse@telecom.kz
via KZ-KAZAKTELECOM-20120612
└ 5.76.168.0/212,048GPON_FTTH_SERVICES_KTJSC KazakhtelecomASSIGNED PASep 11, 2013abuse@telecom.kz
via KZ-KAZAKTELECOM-20120612
└ 5.76.176.0/212,048GPON_FTTH_SERVICES_KTJSC KazakhtelecomASSIGNED PAApr 11, 2013abuse@telecom.kz
via KZ-KAZAKTELECOM-20120612
└ 5.76.184.0/212,048GPON_FTTH_SERVICES_KTJSC KazakhtelecomASSIGNED PASep 11, 2013abuse@telecom.kz
via KZ-KAZAKTELECOM-20120612
└ 5.76.192.0/212,048GPON_FTTH_SERVICES_KTJSC KazakhtelecomASSIGNED PAMar 18, 2013abuse@telecom.kz
via KZ-KAZAKTELECOM-20120612
└ 5.76.200.0/212,048GPON_FTTH_SERVICESJSC KazakhtelecomASSIGNED PADec 28, 2018abuse@telecom.kz
via KZ-KAZAKTELECOM-20120612
└ 5.76.208.0/212,048GPON_FTTH_SERVICES_KTJSC KazakhtelecomASSIGNED PAMar 18, 2013abuse@telecom.kz
via KZ-KAZAKTELECOM-20120612
└ 5.76.216.0/212,048GPON_FTTH_SERVICESJSC KazakhtelecomASSIGNED PAAug 7, 2018abuse@telecom.kz
via KZ-KAZAKTELECOM-20120612
└ 5.76.224.0/212,048GPON_FTTH_SERVICES_KTJSC KazakhtelecomASSIGNED PAAug 1, 2012abuse@telecom.kz
via KZ-KAZAKTELECOM-20120612
└ 5.76.232.0/212,048GPON_FTTH_SERVICES_KTJSC KazakhtelecomASSIGNED PAMar 18, 2013abuse@telecom.kz
via KZ-KAZAKTELECOM-20120612
└ 5.76.240.0/212,048GPON_FTTH_SERVICESJSC KazakhtelecomASSIGNED PAAug 7, 2018abuse@telecom.kz
via KZ-KAZAKTELECOM-20120612
└ 5.76.248.0/212,048GPON_FTTH_SERVICES_KTJSC KazakhtelecomASSIGNED PAMar 18, 2013abuse@telecom.kz
via KZ-KAZAKTELECOM-20120612

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
Jun 2012
Current origin since
Jun 2012 · 14 yr
Origin networks
1