asn.dev

Observed topology

AS205185 DCSPINE

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS205185: 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
AS39686Eurofiber Nederland BVResidentialIPv4 IPv6795

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS25459Eurofiber Cloud Infra B.V.HostingIPv4 IPv61,074
AS62353Eurofiber Cloud Infra B.V.UnclassifiedIPv4 IPv696
AS212098Jeroen van Brink trading as InfrapodUnclassifiedIPv4 IPv691
AS198352Espresso Gridpoint BVUnclassifiedIPv4 IPv650
AS57626E-Zorg B.V.UnclassifiedIPv4 IPv646
AS44299SPL B.V.UnclassifiedIPv420
AS196755Sewan Belgium SAResidentialIPv4 IPv617
AS214864BPC AGUnclassifiedIPv413
AS58075X2com BVResidentialIPv48
AS398300OCIENT INCUnclassifiedIPv45

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS39686Eurofiber Nederland BVResidentialIPv4 IPv62,307
AS25459Eurofiber Cloud Infra B.V.HostingIPv4 IPv61,074
AS212098Jeroen van Brink trading as InfrapodUnclassifiedIPv4 IPv6183
AS62353Eurofiber Cloud Infra B.V.UnclassifiedIPv4 IPv696
AS198352Espresso Gridpoint BVUnclassifiedIPv4 IPv650
AS57626E-Zorg B.V.UnclassifiedIPv4 IPv646
AS44299SPL B.V.UnclassifiedIPv420
AS196755Sewan Belgium SAResidentialIPv4 IPv617
AS214864BPC AGUnclassifiedIPv413
AS58075X2com BVResidentialIPv48

All 11 adjacent →

Provenance

Where this comes from

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