asn.dev

Observed topology

AS63949 AKAMAI-LINODE-AP - Akamai Connected Cloud

Hosting APNIC Content

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

Transit

Upstream networks

All 50

Networks observed carrying traffic for AS63949: 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
AS20940Akamai International B.V.HostingIPv4 IPv619,191
AS6939Hurricane Electric LLCTransitIPv4 IPv62,481
AS9498BHARTI Airtel Ltd.MobileIPv4 IPv6566
AS9002RETN LimitedUnclassifiedIPv4 IPv6456
AS24482SG.GSHostingIPv4 IPv6185
AS3303Swisscom (Schweiz) AGResidentialIPv4 IPv6166
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv6155
AS4637Telstra GlobalUnclassifiedIPv4 IPv6142
AS33891Core-Backbone GmbHHostingIPv4137
AS1273IDDQD-ASBusinessIPv4 IPv680

All 50 upstreams →

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

All 50

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

ASNetworkTypeFamiliesPaths seen
AS20940Akamai International B.V.HostingIPv4 IPv619,191
AS6939Hurricane Electric LLCTransitIPv4 IPv62,481
AS9498BHARTI Airtel Ltd.MobileIPv4 IPv6566
AS9002RETN LimitedUnclassifiedIPv4 IPv6456
AS24482SG.GSHostingIPv4 IPv6185
AS3303Swisscom (Schweiz) AGResidentialIPv4 IPv6166
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv6155
AS4637Telstra GlobalUnclassifiedIPv4 IPv6142
AS33891Core-Backbone GmbHHostingIPv4137
AS1273IDDQD-ASBusinessIPv4 IPv680

All 50 adjacent →

Provenance

Where this comes from

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