Data as of Nov 11, 2026

82.200.207.4/30

No anonymizer space · no proxy exits in 30 days

JSC Kazakhtelecom

Announcement

82.200.204.0/22

RPKI valid

Announced by

AS9198

Type

Business

Risk

0 / 100 · Low

Residential-proxy exits

Proxy exits

75% of its addresses · listed by providers

Providers

selling exits here

Proxy providers listing exits

BestProxy
BirdProxies
ByteProxies
Byteful
CliProxy
EnigmaProxy
FlashProxy
GSocks
GonzoProxy
Infatica
MangoProxy
NSocks
NodeProxy
NovProxy
NovaProxy
Proxiware
Proxy-Seller
ProxyEmpire
Proxyma
RainProxy
Shifter
Smartproxy
VantageProxies

Announcements

Less specific

Covering announcements

Prefix	Origin	Type	Proxy exits	Holder	RPKI
82.200.128.0/17 since May 2005	AS9198	Residential	785 37 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
82.200.128.0/17	32,768	KZ-KAZAKTELECOM-20030918	JSC Kazakhtelecom (ORG-KDNA1-RIPE) · KZ	ALLOCATED PA	Sep 18, 2003	abuse@telecom.kz
└ 82.200.207.4/30	4	ENPF	AO <NPF GNPF>	ASSIGNED PA	Jul 27, 2012	abuse@telecom.kz via KZ-KAZAKTELECOM-20030918

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

82.200.204.0/22

Routing history

Pattern: Stable
First seen: Aug 2005
Current origin since: Aug 2005 · 21 yr
Origin networks: 1

RPKI

Route origin authorizations

ROA prefix	ASN	Max len	Anchor	Verdict
82.200.204.0/22	AS9198	/22	RIPE	RPKI valid
82.200.128.0/17	AS9198	/24	RIPE	RPKI valid

IRR

Route objects on 82.200.204.0/22

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