asn.dev

Observed topology

AS18209 CABLELITE-AS-AP Atria Convergence Technologies Ltd.

Residential APNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS18209: 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
AS4755TATA Communications formerly VSNL is Leading ISPHostingIPv4 IPv68,209
AS9498BHARTI Airtel Ltd.MobileIPv4966
AS9583Sify LimitedUnclassifiedIPv63

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS55577Atria Convergence Technologies Ltd.UnclassifiedIPv4 IPv610,465
AS54994Meteverse Limited.UnclassifiedIPv4 IPv696
AS13335Cloudflare, Inc.HostingIPv4 IPv695

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS4755TATA Communications formerly VSNL is Leading ISPHostingIPv4 IPv615,015
AS55577Atria Convergence Technologies Ltd.UnclassifiedIPv4 IPv610,465
AS9498BHARTI Airtel Ltd.MobileIPv4 IPv64,816
AS54994Meteverse Limited.UnclassifiedIPv4 IPv696
AS13335Cloudflare, Inc.HostingIPv4 IPv695
AS9583Sify LimitedUnclassifiedIPv63

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.