asn.dev

Observed topology

AS20546 SOPRADO-ANY SOPRADO GmbH

Hosting RIPE Content

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

Transit

Upstream networks

All 31

Networks observed carrying traffic for AS20546: 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 IPv64,899
AS6939Hurricane Electric LLCTransitIPv4 IPv6446
AS174Cogent Communications, LLCTransitIPv4 IPv6256
AS2914NTT America, Inc.TransitIPv4 IPv6160
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv670
AS24482SG.GSHostingIPv4 IPv641
AS34019Hivane AssociationUnclassifiedIPv4 IPv641
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv640
AS17639Converge ICT Solutions Inc.UnclassifiedIPv631
AS213241TECHIT.BE SRLResidentialIPv631

All 31 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS12337noris network AGUnclassifiedIPv4116

Adjacency

Adjacent networks

All 32

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

ASNetworkTypeFamiliesPaths seen
AS33891Core-Backbone GmbHHostingIPv4 IPv65,013
AS6939Hurricane Electric LLCTransitIPv4 IPv6446
AS174Cogent Communications, LLCTransitIPv4 IPv6256
AS2914NTT America, Inc.TransitIPv4 IPv6162
AS12337noris network AGUnclassifiedIPv4116
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv670
AS24482SG.GSHostingIPv4 IPv641
AS34019Hivane AssociationUnclassifiedIPv4 IPv641
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv640
AS17639Converge ICT Solutions Inc.UnclassifiedIPv631

All 32 adjacent →

Provenance

Where this comes from

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