asn.dev

Observed topology

AS24016 RAAJJEONLINE-AS Focus Infocom Private Limited

Residential APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS24016: 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
AS7642DHIVEHI RAAJJEYGE GULHUN PLCResidentialIPv4 IPv62,377
AS45489Sri Lanka Telecom PLC, GLobal PeeringResidentialIPv4 IPv6132

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS150125Maldives internet exchangeUnclassifiedIPv4 IPv693
AS137981Bank of Maldives PlcUnclassifiedIPv412
AS133742State Trading Organization PlcUnclassifiedIPv48
AS137056Tree Top Health Pvt. Ltd.UnclassifiedIPv47
AS132218Maldives Customs ServiceUnclassifiedIPv46

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS7642DHIVEHI RAAJJEYGE GULHUN PLCResidentialIPv4 IPv62,377
AS45489Sri Lanka Telecom PLC, GLobal PeeringResidentialIPv4 IPv6354
AS150125Maldives internet exchangeUnclassifiedIPv4 IPv6189
AS137981Bank of Maldives PlcUnclassifiedIPv412
AS133742State Trading Organization PlcUnclassifiedIPv48
AS137056Tree Top Health Pvt. Ltd.UnclassifiedIPv47
AS132218Maldives Customs ServiceUnclassifiedIPv46

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.