asn.dev

Observed topology

AS31564 HEXAGLOBE-AS Hexaglobe SAS

Hosting RIPE

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

Transit

Upstream networks

All 15

Networks observed carrying traffic for AS31564: 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
AS3356Level 3 Parent, LLCTransitIPv4 IPv643
AS1299Arelion Sweden ABTransitIPv435
AS6939Hurricane Electric LLCTransitIPv4 IPv628
AS174Cogent Communications, LLCTransitIPv412
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv46
AS9002RETN LimitedUnclassifiedIPv63
AS24482SG.GSHostingIPv4 IPv63
AS34019Hivane AssociationUnclassifiedIPv4 IPv63
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv63
AS50628Leonix Telecom SASUnclassifiedIPv4 IPv63

All 15 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS200906MCT SASUnclassifiedIPv4156
AS212424Association des Reseaux de CentraleSupelecUnclassifiedIPv4 IPv688

Adjacency

Adjacent networks

All 17

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

ASNetworkTypeFamiliesPaths seen
AS200906MCT SASUnclassifiedIPv4156
AS3356Level 3 Parent, LLCTransitIPv4 IPv6119
AS1299Arelion Sweden ABTransitIPv4109
AS212424Association des Reseaux de CentraleSupelecUnclassifiedIPv4 IPv688
AS174Cogent Communications, LLCTransitIPv459
AS6939Hurricane Electric LLCTransitIPv4 IPv649
AS6696VERIXI SAUnclassifiedIPv47
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv46
AS24482SG.GSHostingIPv4 IPv66
AS34019Hivane AssociationUnclassifiedIPv4 IPv66

All 17 adjacent →

Provenance

Where this comes from

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