asn.dev

Observed topology

AS24864 R-IT-AS Raiffeisen Informatik GmbH & Co KG

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS24864: 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
AS13335Cloudflare, Inc.HostingIPv42,201
AS8218Zayo Infrastructure France SAUnclassifiedIPv4 IPv6127
AS3356Level 3 Parent, LLCTransitIPv4 IPv677
AS1299Arelion Sweden ABTransitIPv4 IPv668
AS6939Hurricane Electric LLCTransitIPv4 IPv645
AS3303Swisscom (Schweiz) AGResidentialIPv410
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv62
AS9002RETN LimitedUnclassifiedIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS205752Kontron AGUnclassifiedIPv459
AS211099Raiffeisen Informatik GmbH & Co KGUnclassifiedIPv4 IPv620

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS13335Cloudflare, Inc.HostingIPv42,201
AS8218Zayo Infrastructure France SAUnclassifiedIPv4 IPv6168
AS3356Level 3 Parent, LLCTransitIPv4 IPv692
AS1299Arelion Sweden ABTransitIPv4 IPv681
AS205752Kontron AGUnclassifiedIPv459
AS6939Hurricane Electric LLCTransitIPv4 IPv652
AS211099Raiffeisen Informatik GmbH & Co KGUnclassifiedIPv4 IPv620
AS3303Swisscom (Schweiz) AGResidentialIPv412
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv63
AS9002RETN LimitedUnclassifiedIPv61

Provenance

Where this comes from

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