Observed topology

AS48854 TEAM-BLUE-DENMARK

Hosting RIPE Content

Upstreams 3 carry this network

Downstreams 4 this network carries

Adjacent (IPv4) 7

Adjacent (IPv6) 5

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS48854: 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
AS3292	TDC Holding A/S	Residential	IPv4 IPv6	1,625
AS3342	Cibicom A/S	Unclassified	IPv4 IPv6	1,310
AS31027	GlobalConnect A/S	Unclassified	IPv4	2

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS59701	NetNordic Denmark A/S	Unclassified	IPv4 IPv6	894
AS204652	team.blue Denmark A/S	Unclassified	IPv4 IPv6	186
AS196976	team.blue Denmark A/S	Unclassified	IPv4	59
AS208310	team.blue Denmark A/S	Unclassified	IPv4	59

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS3292	TDC Holding A/S	Residential	IPv4 IPv6	2,302
AS3342	Cibicom A/S	Unclassified	IPv4 IPv6	1,803
AS59701	NetNordic Denmark A/S	Unclassified	IPv4 IPv6	894
AS204652	team.blue Denmark A/S	Unclassified	IPv4 IPv6	186
AS196976	team.blue Denmark A/S	Unclassified	IPv4	59
AS208310	team.blue Denmark A/S	Unclassified	IPv4	59
AS31027	GlobalConnect A/S	Unclassified	IPv4 IPv6	30

Provenance

Where this comes from

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