Observed topology

AS60497 ict-media Uwe Zeidler

Hosting RIPE

Upstreams 3 carry this network

Downstreams 4 this network carries

Adjacent (IPv4) 7

Adjacent (IPv6) 5

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS60497: 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
AS1299	Arelion Sweden AB	Transit	IPv4	154
AS174	Cogent Communications, LLC	Transit	IPv4 IPv6	89
AS3257	GTT Communications Inc.	Transit	IPv4	20

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS206677	EMG Belgium NV	Unclassified	IPv4 IPv6	180
AS215667	Cyclop S.a r.l.	Unclassified	IPv4 IPv6	136
AS199839	MikeNetworks S.a r.l.-S.	Hosting	IPv4 IPv6	77
AS210834	LU-CIX Management G.I.E.	Hosting	IPv4	4

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS1299	Arelion Sweden AB	Transit	IPv4 IPv6	320
AS174	Cogent Communications, LLC	Transit	IPv4 IPv6	258
AS206677	EMG Belgium NV	Unclassified	IPv4 IPv6	180
AS215667	Cyclop S.a r.l.	Unclassified	IPv4 IPv6	136
AS3257	GTT Communications Inc.	Transit	IPv4	85
AS199839	MikeNetworks S.a r.l.-S.	Hosting	IPv4 IPv6	80
AS210834	LU-CIX Management G.I.E.	Hosting	IPv4	4

Provenance

Where this comes from

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