asn.dev

Observed topology

AS209216 TRUSTED-COLO

Hosting RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS209216: 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
AS6939Hurricane Electric LLCTransitIPv4 IPv6183
AS29404Elbracht-Computer Netzwerk & Grafik Service GmbHHostingIPv4114
AS3320Deutsche Telekom AGMobileIPv4102
AS44066firstcolo GmbHUnclassifiedIPv416
AS34154Configo Systems Gesellschaft fuer Systemloesungen mbHResidentialIPv46

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS204197JD Invest GmbHUnclassifiedIPv4114
AS59741Marco Sandro NaefHostingIPv4 IPv6102

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6395
AS29404Elbracht-Computer Netzwerk & Grafik Service GmbHHostingIPv4114
AS204197JD Invest GmbHUnclassifiedIPv4114
AS3320Deutsche Telekom AGMobileIPv4102
AS59741Marco Sandro NaefHostingIPv4 IPv6102
AS44066firstcolo GmbHUnclassifiedIPv420
AS34154Configo Systems Gesellschaft fuer Systemloesungen mbHResidentialIPv46

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.