asn.dev

Observed topology

AS45410 ALLOTECH-AS-MY ALLO TECHNOLOGY SDN. BHD.

Residential APNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS45410: 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
AS6939Hurricane Electric LLCTransitIPv4 IPv6332
AS174Cogent Communications, LLCTransitIPv4240
AS2914NTT America, Inc.TransitIPv4 IPv6216
AS24482SG.GSHostingIPv4 IPv626
AS38001NewMedia Express Pte LtdHostingIPv4 IPv626
AS35280F5 Networks SARLHostingIPv4 IPv617
AS55720Gigabit Hosting Sdn BhdHostingIPv416

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS133408UNIVERSITI TENAGA NASIONAL SDN BHDUnclassifiedIPv4174
AS55951Lembaga Hasil Dalam Negeri MalaysiaUnclassifiedIPv450
AS140971Tenaga Nasional BerhadUnclassifiedIPv48

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6365
AS174Cogent Communications, LLCTransitIPv4336
AS2914NTT America, Inc.TransitIPv4 IPv6307
AS133408UNIVERSITI TENAGA NASIONAL SDN BHDUnclassifiedIPv4174
AS55951Lembaga Hasil Dalam Negeri MalaysiaUnclassifiedIPv450
AS24482SG.GSHostingIPv4 IPv631
AS38001NewMedia Express Pte LtdHostingIPv4 IPv631
AS55720Gigabit Hosting Sdn BhdHostingIPv420
AS35280F5 Networks SARLHostingIPv4 IPv617
AS140971Tenaga Nasional BerhadUnclassifiedIPv48

All 11 adjacent →

Provenance

Where this comes from

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