asn.dev

Observed topology

AS215628 AS-XENOX-AT Xenox IT & Kommunikations GmbH

Hosting RIPE Network Services

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS215628: 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
AS12577MMC GmbHUnclassifiedIPv4 IPv6505
AS6939Hurricane Electric LLCTransitIPv4 IPv6146
AS8218Zayo Infrastructure France SAUnclassifiedIPv4 IPv613
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv613
AS9002RETN LimitedUnclassifiedIPv64

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS199156Peter RoubicekUnclassifiedIPv4 IPv694
AS219198open mind consulting gmbhUnclassifiedIPv4 IPv694
AS199596Electronic u. Kommunikationstechnik GmbHUnclassifiedIPv460

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS12577MMC GmbHUnclassifiedIPv4 IPv6683
AS6939Hurricane Electric LLCTransitIPv4 IPv6205
AS199156Peter RoubicekUnclassifiedIPv4 IPv694
AS219198open mind consulting gmbhUnclassifiedIPv4 IPv694
AS199596Electronic u. Kommunikationstechnik GmbHUnclassifiedIPv460
AS8218Zayo Infrastructure France SAUnclassifiedIPv4 IPv618
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv617
AS9002RETN LimitedUnclassifiedIPv66

Provenance

Where this comes from

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