asn.dev

Observed topology

AS50873 AS50873 - David Doepelheuer

Hosting ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS50873: 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
AS24961WIIT AGHostingIPv4 IPv6362

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS60316RS Gesellschaft fuer Informationstechnik mbH & Co.KGUnclassifiedIPv4 IPv6587
AS204136Kevin HollyUnclassifiedIPv4 IPv6182
AS200603FIXME GmbHUnclassifiedIPv4 IPv6149
AS204333Witalij KoweschnikowUnclassifiedIPv4 IPv6100
AS60571David DoepelheuerUnclassifiedIPv4 IPv691
AS49436Stadtwerke Soest GmbHUnclassifiedIPv452
AS35675Wissenschaftsladen Dortmund e.V.UnclassifiedIPv42

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS24961WIIT AGHostingIPv4 IPv61,773
AS60316RS Gesellschaft fuer Informationstechnik mbH & Co.KGUnclassifiedIPv4 IPv6587
AS204333Witalij KoweschnikowUnclassifiedIPv4 IPv6280
AS204136Kevin HollyUnclassifiedIPv4 IPv6182
AS200603FIXME GmbHUnclassifiedIPv4 IPv6149
AS60571David DoepelheuerUnclassifiedIPv4 IPv691
AS49436Stadtwerke Soest GmbHUnclassifiedIPv465
AS41451Dominik SchlueterUnclassifiedIPv4 IPv655
AS35675Wissenschaftsladen Dortmund e.V.UnclassifiedIPv42

Provenance

Where this comes from

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