Observed topology

AS41678 TIBUS

Hosting RIPE

Upstreams 15 carry this network

Downstreams 2 this network carries

Adjacent (IPv4) 17

Adjacent (IPv6) 0

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

Transit

Upstream networks

All 15

Networks observed carrying traffic for AS41678: 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
AS6939	Hurricane Electric LLC	Transit	IPv4	669
AS174	Cogent Communications, LLC	Transit	IPv4	115
AS1299	Arelion Sweden AB	Transit	IPv4	109
AS3356	Level 3 Parent, LLC	Transit	IPv4	51
AS34549	meerfarbig GmbH & Co. KG	Hosting	IPv4	42
AS3303	Swisscom (Schweiz) AG	Residential	IPv4	25
AS3741	Dimension Data	Unclassified	IPv4	18
AS24482	SG.GS	Hosting	IPv4	18
AS37100	SEACOM Limited	Unclassified	IPv4	18
AS37721	Virtual Technologies & Solutions	Residential	IPv4	18

All 15 upstreams →

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS16032	The Internet Business Ltd	Unclassified	IPv4	448
AS209980	Marlink AS	Unclassified	IPv4	150

Adjacency

Adjacent networks

All 17

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

AS	Network	Type	Families	Paths seen
AS6939	Hurricane Electric LLC	Transit	IPv4	1,067
AS16032	The Internet Business Ltd	Unclassified	IPv4	448
AS174	Cogent Communications, LLC	Transit	IPv4	168
AS1299	Arelion Sweden AB	Transit	IPv4	153
AS209980	Marlink AS	Unclassified	IPv4	150
AS3356	Level 3 Parent, LLC	Transit	IPv4	65
AS34549	meerfarbig GmbH & Co. KG	Hosting	IPv4	62
AS3303	Swisscom (Schweiz) AG	Residential	IPv4	32
AS3741	Dimension Data	Unclassified	IPv4	28
AS24482	SG.GS	Hosting	IPv4	28

All 17 adjacent →

Provenance

Where this comes from

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