asn.dev

Observed topology

AS31293 ITNSGLOBAL-AS

Unclassified RIPE

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

Transit

Upstream networks

All 13

Networks observed carrying traffic for AS31293: 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
AS57344Telehouse EADResidentialIPv4 IPv6434
AS3356Level 3 Parent, LLCTransitIPv4 IPv6177
AS6939Hurricane Electric LLCTransitIPv4 IPv6158
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv641
AS400687Solytro LTDUnclassifiedIPv49
AS8280SYNAPSECOM S.A. Provider of Telecommunications and Internet ServicesHostingIPv47
AS24482SG.GSHostingIPv47
AS37721Virtual Technologies & SolutionsResidentialIPv47
AS49673Truenetwork LLCUnclassifiedIPv47
AS56655Gigahost ASUnclassifiedIPv47

All 13 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS394470Ecloud360UnclassifiedIPv4183
AS203954ITNS GLOBAL EOODUnclassifiedIPv450

Adjacency

Adjacent networks

All 15

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

ASNetworkTypeFamiliesPaths seen
AS57344Telehouse EADResidentialIPv4 IPv6576
AS3356Level 3 Parent, LLCTransitIPv4 IPv6240
AS394470Ecloud360UnclassifiedIPv4183
AS6939Hurricane Electric LLCTransitIPv4 IPv6176
AS203954ITNS GLOBAL EOODUnclassifiedIPv450
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv643
AS8280SYNAPSECOM S.A. Provider of Telecommunications and Internet ServicesHostingIPv410
AS400687Solytro LTDUnclassifiedIPv49
AS24482SG.GSHostingIPv48
AS37721Virtual Technologies & SolutionsResidentialIPv48

All 15 adjacent →

Provenance

Where this comes from

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