asn.dev

Observed topology

AS55482 DIGITAL-WAVE-MY - Level 12 Menara Sunway, Jalan Lagoon Timur,

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS55482: 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
AS2914NTT America, Inc.TransitIPv4 IPv6313
AS5511Orange S.A.TransitIPv4 IPv6203
AS6939Hurricane Electric LLCTransitIPv4 IPv694
AS4788TM TECHNOLOGY SERVICES SDN. BHD.MobileIPv458
AS38001NewMedia Express Pte LtdHostingIPv4 IPv611

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS21433Accenture UK LimitedUnclassifiedIPv460

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS2914NTT America, Inc.TransitIPv4 IPv6343
AS5511Orange S.A.TransitIPv4 IPv6224
AS6939Hurricane Electric LLCTransitIPv4 IPv6102
AS21433Accenture UK LimitedUnclassifiedIPv460
AS4788TM TECHNOLOGY SERVICES SDN. BHD.MobileIPv458
AS38001NewMedia Express Pte LtdHostingIPv4 IPv612

Provenance

Where this comes from

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