asn.dev

Observed topology

AS43284 IWB-TELEKOM IWB Industrielle Werke Basel

Unclassified RIPE NSP

Upstreams 8 carry this network
Downstreams 2 this network carries
Adjacent (IPv4) 10
Adjacent (IPv6) 7
Upstream graph Who carries AS43284, and who carries them, drawn as a map up to the transit-free core. 1 exchange Where AS43284 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS43284: 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
AS33891Core-Backbone GmbHHostingIPv4 IPv6178
AS6939Hurricane Electric LLCTransitIPv4 IPv6106
AS13030Init7 (Switzerland) Ltd.HostingIPv4 IPv697
AS174Cogent Communications, LLCTransitIPv4 IPv690
AS24482SG.GSHostingIPv4 IPv69
AS3303Swisscom (Schweiz) AGResidentialIPv47
AS34019Hivane AssociationUnclassifiedIPv43
AS9002RETN LimitedUnclassifiedIPv62

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS199567Fr. Sauter AGUnclassifiedIPv4 IPv6378
AS30973Loomis International Corporate AGUnclassifiedIPv445

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS199567Fr. Sauter AGUnclassifiedIPv4 IPv6378
AS33891Core-Backbone GmbHHostingIPv4 IPv6358
AS6939Hurricane Electric LLCTransitIPv4 IPv6187
AS174Cogent Communications, LLCTransitIPv4 IPv6165
AS13030Init7 (Switzerland) Ltd.HostingIPv4 IPv6160
AS30973Loomis International Corporate AGUnclassifiedIPv445
AS24482SG.GSHostingIPv4 IPv617
AS3303Swisscom (Schweiz) AGResidentialIPv414
AS34019Hivane AssociationUnclassifiedIPv410
AS9002RETN LimitedUnclassifiedIPv63

All 11 adjacent →

Provenance

Where this comes from

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