asn.dev

Observed topology

AS31617 REEVO

Hosting RIPE Content

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS31617: 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
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv6481
AS174Cogent Communications, LLCTransitIPv4 IPv6400
AS6939Hurricane Electric LLCTransitIPv4 IPv6126
AS1299Arelion Sweden ABTransitIPv460
AS24482SG.GSHostingIPv4 IPv615
AS3303Swisscom (Schweiz) AGResidentialIPv413
AS59919Brainbox S.r.l.ResidentialIPv413
AS31543myNet GmbHResidentialIPv4 IPv612
AS8612Smeraldo S.p.A.ResidentialIPv410
AS29632Netassist International EOODUnclassifiedIPv64

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS209191Mediatech s.r.l.UnclassifiedIPv459

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv6503
AS174Cogent Communications, LLCTransitIPv4 IPv6437
AS6939Hurricane Electric LLCTransitIPv4 IPv6126
AS1299Arelion Sweden ABTransitIPv460
AS209191Mediatech s.r.l.UnclassifiedIPv459
AS24482SG.GSHostingIPv4 IPv615
AS3303Swisscom (Schweiz) AGResidentialIPv413
AS59919Brainbox S.r.l.ResidentialIPv413
AS31543myNet GmbHResidentialIPv4 IPv612
AS8612Smeraldo S.p.A.ResidentialIPv410

All 11 adjacent →

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-30 10:00 UTC by route-views2,rrc00, as seen from 76 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.