asn.dev

Observed topology

AS41678 TIBUS The Internet Business Ltd

Hosting RIPE Content

Upstreams 14 carry this network
Downstreams 2 this network carries
Adjacent (IPv4) 16
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 14

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.

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4684
AS174Cogent Communications, LLCTransitIPv4131
AS1299Arelion Sweden ABTransitIPv4120
AS3356Level 3 Parent, LLCTransitIPv456
AS34549meerfarbig GmbH & Co. KGHostingIPv434
AS3303Swisscom (Schweiz) AGResidentialIPv425
AS3741Dimension DataUnclassifiedIPv418
AS24482SG.GSHostingIPv418
AS37100SEACOM LimitedUnclassifiedIPv418
AS37721Virtual Technologies & SolutionsResidentialIPv418

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS16032The Internet Business LtdUnclassifiedIPv4330
AS209980Marlink ASUnclassifiedIPv4154

Adjacency

Adjacent networks

All 16

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv41,010
AS16032The Internet Business LtdUnclassifiedIPv4330
AS174Cogent Communications, LLCTransitIPv4175
AS1299Arelion Sweden ABTransitIPv4157
AS209980Marlink ASUnclassifiedIPv4154
AS3356Level 3 Parent, LLCTransitIPv470
AS34549meerfarbig GmbH & Co. KGHostingIPv448
AS3303Swisscom (Schweiz) AGResidentialIPv430
AS3741Dimension DataUnclassifiedIPv426
AS24482SG.GSHostingIPv426

Provenance

Where this comes from

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