asn.dev

Observed topology

AS46015 EXABYTES-AS-AP Exa Bytes Network Sdn.Bhd.

Hosting APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS46015: 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
AS9930TIME dotCom Berhad No. 14, Jalan Majistret U1/26 Hicom Glenmarie Industrial Park 40150 Shah Alam Selangor, MalaysiaUnclassifiedIPv4 IPv61,275
AS38182Extreme Broadband - Total Broadband ExperienceResidentialIPv4152
AS24482SG.GSHostingIPv414
AS55720Gigabit Hosting Sdn BhdHostingIPv414
AS6939Hurricane Electric LLCTransitIPv48
AS38001NewMedia Express Pte LtdHostingIPv48

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS9930TIME dotCom Berhad No. 14, Jalan Majistret U1/26 Hicom Glenmarie Industrial Park 40150 Shah Alam Selangor, MalaysiaUnclassifiedIPv4 IPv61,275
AS38182Extreme Broadband - Total Broadband ExperienceResidentialIPv4152
AS24482SG.GSHostingIPv414
AS55720Gigabit Hosting Sdn BhdHostingIPv414
AS6939Hurricane Electric LLCTransitIPv48
AS38001NewMedia Express Pte LtdHostingIPv48

Provenance

Where this comes from

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