asn.dev

Observed topology

AS5605 NETUSE

Hosting APNIC

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

Transit

Upstream networks

All 23

Networks observed carrying traffic for AS5605: 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
AS1299Arelion Sweden ABTransitIPv4 IPv6171
AS2914NTT America, Inc.TransitIPv4 IPv689
AS6939Hurricane Electric LLCTransitIPv4 IPv678
AS3223Voxility LLPHostingIPv458
AS31027GlobalConnect A/SUnclassifiedIPv4 IPv646
AS3320Deutsche Telekom AGMobileIPv4 IPv639
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv622
AS24482SG.GSHostingIPv4 IPv68
AS42708Glesys ABUnclassifiedIPv4 IPv67
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv67

All 23 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS34086T-Systems International GmbHUnclassifiedIPv4 IPv6325
AS214792Hamburger Hochbahn AGUnclassifiedIPv425

Adjacency

Adjacent networks

All 26

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

ASNetworkTypeFamiliesPaths seen
AS34086T-Systems International GmbHUnclassifiedIPv4 IPv6325
AS2914NTT America, Inc.TransitIPv4 IPv6299
AS1299Arelion Sweden ABTransitIPv4 IPv6210
AS6939Hurricane Electric LLCTransitIPv4 IPv6129
AS3223Voxility LLPHostingIPv458
AS31027GlobalConnect A/SUnclassifiedIPv4 IPv648
AS3320Deutsche Telekom AGMobileIPv4 IPv639
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv625
AS214792Hamburger Hochbahn AGUnclassifiedIPv425
AS42708Glesys ABUnclassifiedIPv4 IPv622

All 26 adjacent →

Provenance

Where this comes from

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