asn.dev

Observed topology

AS210967 ASN-INDASYS indasys IT Systemhaus AG

Unclassified RIPE Enterprise

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

Transit

Upstream networks

All 17

Networks observed carrying traffic for AS210967: 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
AS59745AE Technology Services Germany GmbHUnclassifiedIPv4 IPv672
AS88811&1 Versatel GmbHResidentialIPv4 IPv643
AS6939Hurricane Electric LLCTransitIPv4 IPv629
AS3320Deutsche Telekom AGMobileIPv4 IPv625
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv610
AS24482SG.GSHostingIPv4 IPv64
AS34019Hivane AssociationUnclassifiedIPv4 IPv64
AS212024Marc SchmittUnclassifiedIPv4 IPv64
AS213241TECHIT.BE SRLResidentialIPv4 IPv64
AS6797GlobalConnect ABUnclassifiedIPv43

All 17 upstreams →

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

All 17

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

ASNetworkTypeFamiliesPaths seen
AS59745AE Technology Services Germany GmbHUnclassifiedIPv4 IPv672
AS88811&1 Versatel GmbHResidentialIPv4 IPv643
AS6939Hurricane Electric LLCTransitIPv4 IPv629
AS3320Deutsche Telekom AGMobileIPv4 IPv625
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv610
AS24482SG.GSHostingIPv4 IPv64
AS34019Hivane AssociationUnclassifiedIPv4 IPv64
AS212024Marc SchmittUnclassifiedIPv4 IPv64
AS213241TECHIT.BE SRLResidentialIPv4 IPv64
AS6797GlobalConnect ABUnclassifiedIPv43

All 17 adjacent →

Provenance

Where this comes from

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