asn.dev

Observed topology

AS20783 POP

Unclassified RIPE

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

Transit

Upstream networks

All 19

Networks observed carrying traffic for AS20783: 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
AS174Cogent Communications, LLCTransitIPv4 IPv6132
AS6939Hurricane Electric LLCTransitIPv4 IPv660
AS13237euNetworks GmbHUnclassifiedIPv4 IPv658
AS199524G-Core Labs S.A.HostingIPv458
AS3320Deutsche Telekom AGMobileIPv4 IPv632
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv619
AS24482SG.GSHostingIPv4 IPv67
AS34019Hivane AssociationUnclassifiedIPv4 IPv67
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv67
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv67

All 19 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS50179d.vinci HR-Systems GmbHUnclassifiedIPv4167

Adjacency

Adjacent networks

All 21

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

ASNetworkTypeFamiliesPaths seen
AS174Cogent Communications, LLCTransitIPv4 IPv6196
AS50179d.vinci HR-Systems GmbHUnclassifiedIPv4167
AS13237euNetworks GmbHUnclassifiedIPv4 IPv686
AS6939Hurricane Electric LLCTransitIPv4 IPv681
AS199524G-Core Labs S.A.HostingIPv458
AS3320Deutsche Telekom AGMobileIPv4 IPv650
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv628
AS24482SG.GSHostingIPv4 IPv610
AS34019Hivane AssociationUnclassifiedIPv4 IPv610
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv610

All 21 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.