asn.dev

Observed topology

AS50472 CHAOS-AS

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS50472: 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
AS50629LWLcom GmbHUnclassifiedIPv4 IPv683
AS9002RETN LimitedUnclassifiedIPv4 IPv672
AS5405Inter.link GmbHUnclassifiedIPv4 IPv666
AS2914NTT America, Inc.TransitIPv4 IPv645
AS24961WIIT AGHostingIPv4 IPv641
AS9136Wobcom GmbHResidentialIPv4 IPv636
AS3320Deutsche Telekom AGMobileIPv4 IPv624
AS6797GlobalConnect ABUnclassifiedIPv43
AS8218Zayo Infrastructure France SAUnclassifiedIPv63
AS24482SG.GSHostingIPv43

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS39788Chaos Computer Club e.V.UnclassifiedIPv4 IPv695

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS9002RETN LimitedUnclassifiedIPv4 IPv696
AS39788Chaos Computer Club e.V.UnclassifiedIPv4 IPv695
AS50629LWLcom GmbHUnclassifiedIPv4 IPv694
AS5405Inter.link GmbHUnclassifiedIPv4 IPv688
AS2914NTT America, Inc.TransitIPv4 IPv660
AS9136Wobcom GmbHResidentialIPv4 IPv648
AS24961WIIT AGHostingIPv4 IPv641
AS3320Deutsche Telekom AGMobileIPv4 IPv632
AS6797GlobalConnect ABUnclassifiedIPv44
AS8218Zayo Infrastructure France SAUnclassifiedIPv64

All 11 adjacent →

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.