asn.dev

Observed topology

AS9312 XTOM - xTom

Hosting APNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS9312: 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
AS137409GSL Networks Pty LTDUnclassifiedIPv4 IPv62,401
AS6939Hurricane Electric LLCTransitIPv4 IPv6402
AS24482SG.GSHostingIPv4 IPv649

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS149440Evoxt Sdn. Bhd.UnclassifiedIPv4 IPv6261
AS23959Owl LimitedUnclassifiedIPv4 IPv6122
AS8888xTom Pty LtdHostingIPv4116
AS212164Jiaxian HeUnclassifiedIPv459
AS212512Detai Prosperous Technologies LimitedUnclassifiedIPv4 IPv63

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS137409GSL Networks Pty LTDUnclassifiedIPv4 IPv62,817
AS6939Hurricane Electric LLCTransitIPv4 IPv6561
AS149440Evoxt Sdn. Bhd.UnclassifiedIPv4 IPv6261
AS23959Owl LimitedUnclassifiedIPv4 IPv6122
AS8888xTom Pty LtdHostingIPv4116
AS24482SG.GSHostingIPv4 IPv659
AS212164Jiaxian HeUnclassifiedIPv459
AS3204xTom OUHostingIPv639
AS7713PT Telekomunikasi IndonesiaResidentialIPv410
AS9304HGC Global Communications LimitedHostingIPv45

All 11 adjacent →

Provenance

Where this comes from

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