asn.dev

Observed topology

AS48173 UNBELIEVABLE-AS

Hosting RIPE Content

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

Transit

Upstream networks

All 26

Networks observed carrying traffic for AS48173: 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 IPv6541
AS13335Cloudflare, Inc.HostingIPv4520
AS2914NTT America, Inc.TransitIPv4 IPv6424
AS6939Hurricane Electric LLCTransitIPv4 IPv6229
AS42649Baffin Bay Networks ABUnclassifiedIPv4118
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv681
AS33891Core-Backbone GmbHHostingIPv452
AS1836green.ch AGResidentialIPv4 IPv628
AS24482SG.GSHostingIPv4 IPv628
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv628

All 26 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS43503synaforce GmbHUnclassifiedIPv473
AS62193BCIX Management GmbHUnclassifiedIPv4 IPv614

Adjacency

Adjacent networks

All 28

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv6541
AS13335Cloudflare, Inc.HostingIPv4520
AS2914NTT America, Inc.TransitIPv4 IPv6474
AS6939Hurricane Electric LLCTransitIPv4 IPv6229
AS42649Baffin Bay Networks ABUnclassifiedIPv4118
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv6115
AS43503synaforce GmbHUnclassifiedIPv473
AS33891Core-Backbone GmbHHostingIPv458
AS62193BCIX Management GmbHUnclassifiedIPv4 IPv644
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv642

All 28 adjacent →

Provenance

Where this comes from

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