Data as of Nov 10, 2026

2.134.148.136/30

No anonymizer space · no proxy exits in 30 days

JSC Kazakhtelecom

Announcement

2.134.128.0/18

RPKI valid

Announced by

AS9198

Type

Business

Risk

0 / 100 · Low

Residential-proxy exits

Proxy exits

100% of its addresses · listed by providers

Providers

selling exits here

Proxy providers listing exits

2Captcha
711Proxy
BirdProxies
BottingTools
ByteProxies
Byteful
CliProxy
FastProxy
FlashProxy
GonzoProxy
Infatica
LemonBright
NSocks
Novada
Proxy-Seller
ProxyEmpire
ProxyWing
Proxyma
RainProxy
Shifter
Smartproxy
Thordata
ThunderProxy
VitalExclusive

Announcements

Less specific

Covering announcements

Prefix	Origin	Type	Proxy exits	Holder	RPKI
2.132.0.0/14 since Jan 2011	AS9198	Residential	61,303 2,294 always on	JSC Kazakhtelecom

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

Range	Addresses	Netname	Holder	Type	Created	Abuse contact
2.132.0.0/14	262,144	KZ-KAZAKTELECOM-20101223	JSC Kazakhtelecom (ORG-KDNA1-RIPE) · KZ	ALLOCATED PA	Dec 23, 2010	abuse@telecom.kz
└ 2.134.148.136/30	4	OTDELOBRAZOVANIA	SHYMKENT	ASSIGNED PA	Jun 15, 2023	abuse@telecom.kz via KZ-KAZAKTELECOM-20101223

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

Announcement Routing history RPKI & IRR Whois & abuse

Routing timeline

Covering aggregate above, the prefix's own history below

2.134.128.0/18

Routing history

Pattern: Stable
First seen: Jan 2011
Current origin since: Oct 2016 · 10 yr
Origin networks: 1

RPKI

Route origin authorizations

ROA prefix	ASN	Max len	Anchor	Verdict
2.134.128.0/18	AS9198	/24	RIPE	RPKI valid
2.132.0.0/14	AS9198	/24	RIPE	RPKI valid

IRR

Route objects on 2.134.128.0/18

Origin	Registry	Description	Maintainer	Modified
AS9198	RIPE	Kazakhtelecom Data Network Administration	KNIC-MNT	Feb 8, 2012