asn.dev

Observed topology

AS60924 ORIXCOM Orixcom Limited

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS60924: 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
AS8966EMIRATES TELECOMMUNICATIONS GROUP COMPANY (ETISALAT GROUP) PJSCMobileIPv4 IPv6222
AS3356Level 3 Parent, LLCTransitIPv4 IPv6151
AS4637Telstra GlobalUnclassifiedIPv4 IPv6116
AS29119AIRE NETWORKS DEL MEDITERRANEO SL UNIPERSONALUnclassifiedIPv4 IPv693
AS35280F5 Networks SARLHostingIPv414
AS8529Zain Omantel International FZ-LLCUnclassifiedIPv4 IPv610

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS60140Buzinessware FZCOUnclassifiedIPv4277
AS11179Aryaka Networks, Inc.HostingIPv460
AS26178AtkinsRealisUnclassifiedIPv414

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS8966EMIRATES TELECOMMUNICATIONS GROUP COMPANY (ETISALAT GROUP) PJSCMobileIPv4 IPv6499
AS60140Buzinessware FZCOUnclassifiedIPv4277
AS4637Telstra GlobalUnclassifiedIPv4 IPv6170
AS3356Level 3 Parent, LLCTransitIPv4 IPv6151
AS29119AIRE NETWORKS DEL MEDITERRANEO SL UNIPERSONALUnclassifiedIPv4 IPv693
AS11179Aryaka Networks, Inc.HostingIPv460
AS8529Zain Omantel International FZ-LLCUnclassifiedIPv4 IPv630
AS26178AtkinsRealisUnclassifiedIPv414
AS35280F5 Networks SARLHostingIPv414

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.