asn.dev

Observed topology

AS55944 OOREDOO-MV Ooredoo Maldives Plc

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS55944: 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
AS174Cogent Communications, LLCTransitIPv4 IPv61,126
AS3491PCCW Global (HK) Ltd.TransitIPv4 IPv6828
AS13335Cloudflare, Inc.HostingIPv4601
AS6939Hurricane Electric LLCTransitIPv4 IPv6497
AS6453TATA COMMUNICATIONS (AMERICA) INCTransitIPv4458
AS24482SG.GSHostingIPv4 IPv649
AS38001NewMedia Express Pte LtdHostingIPv4 IPv649
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv636
AS1299Arelion Sweden ABTransitIPv421
AS132132MyRepublic Ltd.ResidentialIPv420

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS136234Media Net Pvt LtdHostingIPv4118
AS14789Cloudflare, Inc.UnclassifiedIPv4 IPv692

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS174Cogent Communications, LLCTransitIPv4 IPv61,223
AS3491PCCW Global (HK) Ltd.TransitIPv4 IPv6897
AS13335Cloudflare, Inc.HostingIPv4601
AS6453TATA COMMUNICATIONS (AMERICA) INCTransitIPv4 IPv6497
AS6939Hurricane Electric LLCTransitIPv4 IPv6497
AS136234Media Net Pvt LtdHostingIPv4118
AS14789Cloudflare, Inc.UnclassifiedIPv4 IPv692
AS24482SG.GSHostingIPv4 IPv649
AS38001NewMedia Express Pte LtdHostingIPv4 IPv649
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv636

Provenance

Where this comes from

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