asn.dev

Observed topology

AS31293 ITNSGLOBAL-AS ITNS GLOBAL EOOD

Unclassified RIPE

Upstreams 12 carry this network
Downstreams 2 this network carries
Adjacent (IPv4) 14
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 12

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 ADResidentialIPv4 IPv6400
AS3356Level 3 Parent, LLCTransitIPv4 IPv6178
AS6939Hurricane Electric LLCTransitIPv4 IPv6143
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv637
AS8280SYNAPSECOM S.A. Provider of Telecommunications and Internet ServicesHostingIPv46
AS24482SG.GSHostingIPv46
AS37721Virtual Technologies & SolutionsResidentialIPv46
AS49673Truenetwork LLCUnclassifiedIPv46
AS56655Gigahost ASUnclassifiedIPv46
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv46

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
AS394470Ecloud360UnclassifiedIPv4165
AS203954ITNS GLOBAL EOODUnclassifiedIPv451

Adjacency

Adjacent networks

All 14

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

ASNetworkTypeFamiliesPaths seen
AS57344Telehouse ADResidentialIPv4 IPv6561
AS3356Level 3 Parent, LLCTransitIPv4 IPv6227
AS394470Ecloud360UnclassifiedIPv4165
AS6939Hurricane Electric LLCTransitIPv4 IPv6143
AS203954ITNS GLOBAL EOODUnclassifiedIPv451
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv638
AS24482SG.GSHostingIPv47
AS37721Virtual Technologies & SolutionsResidentialIPv47
AS49673Truenetwork LLCUnclassifiedIPv47
AS56655Gigahost ASUnclassifiedIPv47

Provenance

Where this comes from

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