asn.dev

Observed topology

AS20902 DEGNET DegNet GmbH

Unclassified RIPE NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS20902: 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
AS12611R-KOM Regensburger Telekommunikationsgesellschaft mbHUnclassifiedIPv4 IPv6468
AS57395synaforce GmbHUnclassifiedIPv4 IPv6410
AS57684Wasserversorgung Bayerischer WaldUnclassifiedIPv435

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS15933ith Kommunikationstechnik GmbHUnclassifiedIPv4174
AS57684Wasserversorgung Bayerischer WaldUnclassifiedIPv4 IPv6126
AS64396Breitband in Bayern GmbHUnclassifiedIPv4 IPv697

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS12611R-KOM Regensburger Telekommunikationsgesellschaft mbHUnclassifiedIPv4 IPv6690
AS57395synaforce GmbHUnclassifiedIPv4 IPv6650
AS57684Wasserversorgung Bayerischer WaldUnclassifiedIPv4 IPv6226
AS15933ith Kommunikationstechnik GmbHUnclassifiedIPv4174
AS64396Breitband in Bayern GmbHUnclassifiedIPv4 IPv697

Provenance

Where this comes from

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