asn.dev

Observed topology

AS21282 KAZNIC-AS KazNIC Organization

Unclassified RIPE Non-Profit

Upstreams 1 carry this network
Downstreams 4 this network carries
Adjacent (IPv4) 4
Adjacent (IPv6) 4
Upstream graph Who carries AS21282, and who carries them, drawn as a map up to the transit-free core. 1 exchange Where AS21282 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS21282: the AS immediately before it in a routing path. Ranked by how many paths showed the relationship, which reflects how widely it is used, not how much traffic crosses it.

ASNetworkTypeFamiliesPaths seen
AS9198JSC KazakhtelecomUnclassifiedIPv4 IPv6134

Transit

Downstream networks

inferred

Networks for which AS21282 was observed as the last hop before the origin, meaning it appears to provide them transit.

ASNetworkTypeFamiliesPaths seen
AS206768Association of IT Companies of KazakhstanHostingIPv4 IPv654
AS51833Association of IT Companies of KazakhstanHostingIPv4 IPv643
AS42909Community DNS LimitedHostingIPv42
AS25152Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv61

Adjacency

Adjacent networks

observed

Every AS seen directly next to AS21282 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS9198JSC KazakhtelecomUnclassifiedIPv4 IPv6234
AS206768Association of IT Companies of KazakhstanHostingIPv4 IPv654
AS51833Association of IT Companies of KazakhstanHostingIPv4 IPv643
AS42909Community DNS LimitedHostingIPv42
AS25152Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv61

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-31 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.50M route entries. These are observations from those vantage points, not a complete or authoritative view of the internet.

Inferred from path position, not from any declaration by either party. A network appearing here is carrying these routes; whether that is a paid transit arrangement, a backup, or something else is not something routing data can tell you. Adjacency is not the same as peering. Being next to each other in a path covers paid transit, settlement-free peering and customer connections alike, and routing data cannot distinguish them. Treat this as "these networks exchange routes", nothing more specific.

Cross-check against RIPEstat or BGP.tools, which observe from a different and larger set of vantage points.