asn.dev

Observed topology

AS21150 INACDE-ATOS

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS21150: 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
AS88811&1 Versatel GmbHResidentialIPv4 IPv6852
AS15830Equinix (EMEA) Acquisition Enterprises B.V.HostingIPv460
AS15598NorthC Deutschland GmbHHostingIPv622

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS15465Siemens AGUnclassifiedIPv4 IPv6754
AS47696Atos Information Technology GmbHUnclassifiedIPv4360
AS43978Atos Information Technology GmbHUnclassifiedIPv4300
AS8735Atos Information Technology GmbHUnclassifiedIPv4258
AS20594Atos Information Technology GmbHUnclassifiedIPv4 IPv6214
AS21026Atos Information Technology GmbHUnclassifiedIPv4180

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS88811&1 Versatel GmbHResidentialIPv4 IPv62,876
AS15465Siemens AGUnclassifiedIPv4 IPv6754
AS47696Atos Information Technology GmbHUnclassifiedIPv4360
AS43978Atos Information Technology GmbHUnclassifiedIPv4300
AS8735Atos Information Technology GmbHUnclassifiedIPv4258
AS20594Atos Information Technology GmbHUnclassifiedIPv4 IPv6214
AS21026Atos Information Technology GmbHUnclassifiedIPv4180
AS15598NorthC Deutschland GmbHHostingIPv664
AS15830Equinix (EMEA) Acquisition Enterprises B.V.HostingIPv460

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-26 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.