Home Prefix Lookup2a06:4080::/29

2a06:4080::/29 - KZ NAT Kazakhstan NAT Kazakhstan JSC (AS202461)

IPv6RIPE NCCallocatedAS202461KZ-NAT_Kazakhstan NAT Kazakhstan JSC RPKI Valid

CIDR

2a06:4080::/29

IP Version

IPv6

Addresses

633825.3Y

Mask

/29

Country

🇰🇿 Kazakhstan

City

Almaty

RIR

RIPE NCC

Status

allocated

Allocated

2026-01-08

Announced BGP Routes

1 of 1 route

RPKI:

IRR:

Swipe sideways to see all columns →

Prefix	Origin AS	RPKI	IRR	Last Seen
2a06:4080::/29	AS202461 KZ-NAT_Kazakhstan NAT Kazakhstan JSC	Valid	RIPE	2026-10-11

RPKI ROAs

Prefix	Origin	Max Length	Trust Anchor
2a06:4080::/29	AS202461	/48	ripe

IRR Route Objects

Origin	Registry	Maintainer	Modified
AS202461	RIPE	nat-kz-mnt	2026-01-12

Transfer History

Registry transfers of 2a06:4080::/29, blocks inside it, or blocks containing it.

2a06:4080::/29M&A · 2025-07-03
CLDIN B.V.
RIPE NCC
→
Your hosting B.V.
RIPE NCC
2a06:4080::/29M&A · 2022-01-20
PCextreme B.V.
RIPE NCC
→
CLDIN B.V.
RIPE NCC

Date	Resource	From	To	Type
2025-07-03	2a06:4080::/29	CLDIN B.V. RIPE NCC	Your hosting B.V. RIPE NCC	M&A
2022-01-20	2a06:4080::/29	PCextreme B.V. RIPE NCC	CLDIN B.V. RIPE NCC	M&A

Origin ASN

AS202461

KZ-NAT_Kazakhstan NAT Kazakhstan JSC

Related Prefixes

More prefixes of AS202461

All prefixes of AS202461 →

Geolocation

Country🇰🇿KazakhstanKZ

RegionAlmaty

CityAlmaty

Coordinates43.2380, 76.8829 ↗

Abuse Contact

Learn more

RPKI and ROAs explainedWhat RPKI valid, invalid and no ROA mean
RPKI validatorCheck ROA coverage for any prefix or ASN
What is BGP?How prefixes are announced and routed
More-specific prefixesGlossary: covering and more-specific routes
IPv4 transfers in the RIPE NCC regionWho bought and sold address space recently

API

Open

GEThttps://api.ipctl.io/v1/prefix/2a06:4080::/29

Returns prefix allocation, BGP routes, and more-specific subnets.

curl -s "https://api.ipctl.io/v1/prefix/2a06:4080::/29" | jq

External Links

RIPEstat