asn.dev

Observed topology

AS12222 AKAMAI

Hosting ARIN

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

Transit

Upstream networks

All 30

Networks observed carrying traffic for AS12222: 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
AS8220COLT Technology Services Group LimitedHostingIPv4 IPv6661
AS7922Comcast Cable Communications, LLCResidentialIPv4 IPv6417
AS174Cogent Communications, LLCTransitIPv4 IPv6348
AS9498BHARTI Airtel Ltd.MobileIPv4 IPv6322
AS3356Level 3 Parent, LLCTransitIPv4 IPv6319
AS12741Netia SAResidentialIPv4 IPv6314
AS7015Comcast Cable Communications, LLCResidentialIPv4 IPv6312
AS6461Zayo BandwidthTransitIPv4 IPv6300
AS9583Sify LimitedUnclassifiedIPv4 IPv6260
AS9255Singapore TelecomUnclassifiedIPv4 IPv6234

Transit

Downstream networks

inferred

Networks for which AS12222 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 30

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

ASNetworkTypeFamiliesPaths seen
AS8220COLT Technology Services Group LimitedHostingIPv4 IPv6661
AS7922Comcast Cable Communications, LLCResidentialIPv4 IPv6417
AS174Cogent Communications, LLCTransitIPv4 IPv6348
AS9498BHARTI Airtel Ltd.MobileIPv4 IPv6322
AS3356Level 3 Parent, LLCTransitIPv4 IPv6319
AS12741Netia SAResidentialIPv4 IPv6314
AS7015Comcast Cable Communications, LLCResidentialIPv4 IPv6312
AS6461Zayo BandwidthTransitIPv4 IPv6300
AS9583Sify LimitedUnclassifiedIPv4 IPv6260
AS9255Singapore TelecomUnclassifiedIPv4 IPv6234

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-25 12: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.