asn.dev

Observed topology

AS215605 INFORMATIQ

Hosting RIPE Network Services

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS215605: 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
AS64289Macarne.comUnclassifiedIPv488
AS6939Hurricane Electric LLCTransitIPv4 IPv621
AS1103SURF B.V.UnclassifiedIPv42
AS5405Inter.link GmbHUnclassifiedIPv42
AS20766Association "Gitoyen"UnclassifiedIPv42
AS24482SG.GSHostingIPv42
AS34927iFog GmbHHostingIPv42
AS37721Virtual Technologies & SolutionsResidentialIPv42

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS207740Youssef HamedUnclassifiedIPv633

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS64289Macarne.comUnclassifiedIPv4 IPv689
AS6939Hurricane Electric LLCTransitIPv4 IPv651
AS207740Youssef HamedUnclassifiedIPv633
AS1103SURF B.V.UnclassifiedIPv4 IPv63
AS24482SG.GSHostingIPv4 IPv63
AS5405Inter.link GmbHUnclassifiedIPv42
AS20766Association "Gitoyen"UnclassifiedIPv42
AS34927iFog GmbHHostingIPv42
AS37721Virtual Technologies & SolutionsResidentialIPv42

Provenance

Where this comes from

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