Observed topology

AS12488 KRYSTAL

Hosting RIPE

Upstreams 6 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 7

Adjacent (IPv6) 5

Upstream graph Who carries AS12488, and who carries them, drawn as a map up to the transit-free core. 1 exchange Where AS12488 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS12488: 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.

AS	Network	Type	Families	Paths seen
AS174	Cogent Communications, LLC	Transit	IPv4 IPv6	624
AS2914	NTT America, Inc.	Transit	IPv4 IPv6	363
AS12025	Iron Mountain Data Center	Unclassified	IPv4 IPv6	254
AS20473	The Constant Company, LLC	Hosting	IPv4	72
AS35266	EX Networks Limited	Unclassified	IPv4 IPv6	15
AS1299	Arelion Sweden AB	Transit	IPv4 IPv6	5

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS57770	Echo Internet Limited	Unclassified	IPv4	59

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS174	Cogent Communications, LLC	Transit	IPv4 IPv6	655
AS2914	NTT America, Inc.	Transit	IPv4 IPv6	391
AS12025	Iron Mountain Data Center	Unclassified	IPv4 IPv6	254
AS20473	The Constant Company, LLC	Hosting	IPv4	72
AS57770	Echo Internet Limited	Unclassified	IPv4	59
AS35266	EX Networks Limited	Unclassified	IPv4 IPv6	15
AS1299	Arelion Sweden AB	Transit	IPv4 IPv6	5

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-20 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.16M 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.