asn.dev

Observed topology

AS54148 DYNAMIC-QUANTUM-NETWORKS

Unclassified ARIN

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

Transit

Upstream networks

All 30

Networks observed carrying traffic for AS54148: 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 LLCTransitIPv4 IPv6321
AS34927iFog GmbHHostingIPv4 IPv6203
AS53667FranTech SolutionsHostingIPv4 IPv6168
AS63473HostHatch, LLCUnclassifiedIPv4 IPv6151
AS52025ParadoxNetworks LimitedUnclassifiedIPv4 IPv6126
AS400587Ryamer, LLCHostingIPv4 IPv698
AS835GoCodeIT IncUnclassifiedIPv4 IPv695
AS20473The Constant Company, LLCHostingIPv4 IPv670
AS137409GSL Networks Pty LTDUnclassifiedIPv670
AS21738RozintResidentialIPv446

All 30 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS47689Pudu, LLCUnclassifiedIPv4 IPv69

Adjacency

Adjacent networks

All 31

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6321
AS34927iFog GmbHHostingIPv4 IPv6203
AS53667FranTech SolutionsHostingIPv4 IPv6168
AS63473HostHatch, LLCUnclassifiedIPv4 IPv6151
AS52025ParadoxNetworks LimitedUnclassifiedIPv4 IPv6128
AS400587Ryamer, LLCHostingIPv4 IPv698
AS835GoCodeIT IncUnclassifiedIPv4 IPv695
AS20473The Constant Company, LLCHostingIPv4 IPv670
AS137409GSL Networks Pty LTDUnclassifiedIPv670
AS21738RozintResidentialIPv453

All 31 adjacent →

Provenance

Where this comes from

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