# Akamai Published articles for Akamai. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Mapping major CDNs across the globe DevFeed: [Mapping major CDNs across the globe]() Original publisher: [Read original article]() Published: 2026-06-06T13:17:04Z Content type: article Language: en Sources: [Personal blog of Anurag Bhatia]() Topics: [BGP](), [networking](), [Networks](), [Routing (disambiguation)](), [TLS (Transport Layer Security)](), [data](), [Amazon Web Services](), [Google](), [Netflix](), [Microsoft](), [Pingora]() Tags: [akamai](), [apple](), [aws](), [bgp](), [cdn](), [data](), [dns](), [facebook](), [fna](), [ggc](), [google](), [major](), [mapping](), [microsoft](), [netflix](), [networks](), [oca](), [routing](), [tls]() ### AI overview This article maps major content delivery networks worldwide by examining routed IP prefixes, open port 443 services, TLS certificate names, autonomous system numbers, and geographic data. It reports global and India-specific coverage figures for Google GGC, Facebook FNA/MNA, Netflix, Akamai, Apple, Microsoft, and AWS CloudFront, while noting that certificate-based identification may miss some deployments. ### Source excerpt In Dec 2022 I mapped popular CDNs like Google GGC, Facebook FNA, Akamai, etc. across Indian networks (post here). Since it's been close to 4 years now, I wanted to do that again. This time, I decided to expand the scope to the entire globe instead of just the Indian networks. Mapping logic The logic here is simple: get unique prefixes from the global routing table, break them into /24s, uniquely sort out /24s, and this gives all routed IP addresses in the world in batches of /24s (256 IPs). Next, identify the ones with an open port 443 and then connect to each of them to figure out the TLS certificate common name. Next, map those IP addresses to AS numbers, locations, etc., using Maxmind's GeoIP Lite databases. Essentially, I am using the BGP routing table instead of scanning the entire 0.0.0.0/0 to avoid scanning for prefixes which are not routed in the global table as well as reserved private IPs, etc. Global stats CDN Provider No. unique ASNs TLS domain Details list URL Google GGC 4247 googlevideo.com csv & json Netflix OCA 2903 oca.nflxvideo.net, assets.nflxext.com csv & json Facebook FNA 2548 'fbcdn.net', fna.whatsapp.net csv & json Akamai 1094 edgesuite.net, edgekey.net, akamaized.net, akamaihd.net, akamaized.net, akamai.net csv & json Microsoft 1655 microsoft.com csv & json Apple 974 apple.com & itunes.apple.com csv & json AWS Cloudfront 217 *.amazonaws.com & *.awsstatic.com csv & json ASN-CDN Mapping table I have mapped ASNs with the presence of each of these CDNs like last time. This makes it easy to read the data instead of going through each of the files separately. Full data in Google Sheet link here and raw CSV is also published here. Notes: Facebook FNA serving Facebook with *.fbcdn.net is almost the same if I look for *.fna.whatsapp.net. Apple seems to have presence in over 236 locations with PCH/Woodynet for hosting their DNS over HTTPS endpoint: doh.dns.apple.com (detailed list here) GGC has a global coverage across 215 countries across the world, f ## Measuring IPv6 deployment on Indian Govt websites DevFeed: [Measuring IPv6 deployment on Indian Govt websites]() Original publisher: [Read original article]() Published: 2026-06-04T20:19:53Z Content type: article Language: en Sources: [Personal blog of Anurag Bhatia]() Topics: [Network](), [Internet](), [Website](), [Google](), [Cloudflare](), [amazon](), [Amazon Web Services]() Tags: [airtel](), [akamai](), [aws](), [cloudflare](), [dns](), [google](), [india](), [ipv6](), [jio](), [nixi](), [websites]() ### AI overview The article measures IPv6 support on Indian government websites using certificate transparency logs and checks for working IPv4 and IPv6 endpoints. Among 4,924 examined domains under gov.in and nic.in, 174, or about 3.5%, had working IPv6 web endpoints. ### Source excerpt India has done well on IPv6 deployment thanks to Jio taking the lead in 2016, along with Airtel & VI aggressively catching up. Many of us in the industry are very proud of the work done by these players, resulting in over 78% deployment of IPv6 when measured by APNIC / Google, etc. Jio and Airtel numbers are as high as 95% IPv6 preferred at this point in time. But that's one part of the Indian metrics. IPv6 deployment, DNSSEC usage or even Internet Exchange peering - one can find very different metrics depending on how one is measuring. Both APNIC & Google rely on Google's network and judge how (largely mobile) end users across India are connecting to their (IPv6-enabled) services, and this gives the "eyeballs" side of specs. One key element missing in the picture is IPv6 support on the Government of India websites. I am using "Govt. of India" loosely here. I mean the Central Govt, state governments, as well as UTs and any of their departments. I have always felt that deployment is very poor, as randomly looking across the critical government websites. The service either shows no DNS AAAA record or may have a AAAA record but does not respond to port 80/443, giving an idea of a broken deployment. Measuring deployment is hard since (as far as I know) there is no authoritative source of government domains. Likely NIXI or ERNET, etc. may hold them but then getting them may be a long process and may not work at all. Then I thought of certificate transparency logs. Most of the CAs would log TLS certificates issued in public logs. One can read these logs for *.gov.in and *.nic.in to get a list of all government. used domains under those well-known TLDs and the ones which took a TLS certificate. I did some extra checks, like verifying the A record, working website on IPv4, before looking for IPv6. That way I remove all non-existent/old/expired websites. Also, looked for and www. in some cases as TLS may be issued for both. In case of wildcard TLS certificates like *..gov.in ## Bringing AI to the Edge with WebAssembly - OpenInfra Korea 2025 DevFeed: [Bringing AI to the Edge with WebAssembly - OpenInfra Korea 2025]() Original publisher: [Read original article]() Author: Brandon Kang Published: 2025-10-02T12:00:00Z Content type: article Language: en Sources: [Fermyon - Experience the next wave of cloud computing.]() Topics: [Artificial Intelligence](), [WebAssembly](), [Edge](), [Cloud]() Tags: [2025](), [ai](), [akamai](), [cloud](), [edge](), [webassembly]() ### AI overview The article covers OpenInfra Days Korea 2025, focusing on bringing AI workloads to the edge with WebAssembly, SpinKube, and Akamai Cloud GPUs. It features commentary from Akamai's Brandon Kang. ### Source excerpt Hear from Akamai's Brandon Kang about OpenInfra Days Korea 2025 and the latest on ultra-fast workloads with SpinKube and Akamai Cloud GPUs ## Humans in AI Podcast - Matt Butcher on Cloud, Edge and AI DevFeed: [Humans in AI Podcast - Matt Butcher on Cloud, Edge and AI]() Original publisher: [Read original article]() Author: Matt Butcher Published: 2025-08-21T12:00:00Z Content type: article Language: en Sources: [Fermyon - Experience the next wave of cloud computing.]() Topics: [Networks](), [Cloud](), [Edge]() Tags: [ai](), [akamai](), [ceo](), [cloud](), [edge](), [evolution](), [networks](), [podcast]() ### AI overview A Humans in AI podcast episode featuring Matt Butcher discusses the evolution of content delivery networks, with particular attention to Akamai's innovations. ### Source excerpt In the latest podcast episode of Humans in AI our CEO, Matt Butcher discusses the evolution of content delivery networks, particularly focusing on Akamai's innovations ## HTTP/1.1 must die: the desync endgame DevFeed: [HTTP/1.1 must die: the desync endgame]() Original publisher: [Read original article]() Author: James Kettle Published: 2025-08-06T22:20:00Z Content type: article Language: en Sources: [PortSwigger Research]() Topics: [HTTP](), [Security](), [Vulnerabilities](), [Parser](), [Open Source]() Tags: [2025](), [akamai](), [cloudflare](), [http](), [issue](), [netlify](), [open-source](), [paper](), [protocol](), [security](), [tcp](), [tls](), [vulnerabilities](), [web]() ### AI overview This paper argues that HTTP/1.1 has a fundamental request-boundary flaw that enables HTTP desync and request smuggling attacks. It presents attack techniques, case studies involving Akamai, Cloudflare, and Netlify, an open-source detection toolkit, and the case for replacing HTTP/1.1 with HTTP/2 or later. ### Source excerpt Abstract Upstream HTTP/1.1 is inherently insecure and regularly exposes millions of websites to hostile takeover. Six years of attempted mitigations have hidden the issue, but failed to fix it. This p ## Snyk Supercharges API Discovery with New Akamai Integration DevFeed: [Snyk Supercharges API Discovery with New Akamai Integration]() Original publisher: [Read original article]() Author: Nuno Loureiro Published: 2025-08-06T04:00:00Z Content type: news Language: en Sources: [Blog RSS Feed | Snyk]() Topics: [API](), [Application Security](), [snyk-platform](), [Security](), [OpenAPI Specification]() Tags: [2025](), [akamai](), [analysis](), [api](), [api-discovery](), [api-security](), [api-testing](), [apis](), [application-security](), [awareness](), [blog](), [co-created](), [efficiency](), [executive](), [integration](), [openapi](), [openapi-specification](), [platform](), [scanner](), [snyk](), [snyk-platform](), [testing](), [web]() ### AI overview Snyk and Akamai announced an integration that automates API discovery and schema ingestion. Akamai API inventories and schemas are added to Snyk API & Web so teams can turn discovered APIs into scannable targets with a single click, improving API security testing coverage and efficiency. ### Source excerpt Snyk and Akamai partner to streamline API security. This integration automates API discovery and schema ingestion from Akamai to power Snyk's DAST engine, boosting scan coverage and efficiency. ## Gotta cache 'em all: bending the rules of web cache exploitation DevFeed: [Gotta cache 'em all: bending the rules of web cache exploitation]() Original publisher: [Read original article]() Author: Martin Doyhenard Published: 2024-08-08T22:27:46Z Content type: article Language: en Sources: [PortSwigger Research]() Topics: [web applications]() Tags: [akamai](), [attacks](), [cache](), [cdn](), [cloudflare](), [http](), [web]() ### AI overview The paper examines URL-parsing discrepancies between application servers and CDN proxies that can enable web cache poisoning and cache deception. ### Source excerpt Through the years, we have seen many attacks exploiting web caches to hijack sensitive information or store malicious payloads. However, as CDNs became more popular, new discrepancies between propriet ## Deploy Turso embedded replicas to Fly, Akamai, Koyeb, Railway, & Render. DevFeed: [Deploy Turso embedded replicas to Fly, Akamai, Koyeb, Railway, & Render.]() Original publisher: [Read original article]() Author: James Sinkala Published: 2024-04-11T00:00:00Z Content type: article Language: en Sources: [Turso Blog]() Topics: [Embedded Replicas](), [Turso](), [fly](), [Cloud](), [SQLite](), [libSQL]() Tags: [akamai](), [application-development](), [cloud](), [databases](), [deployment-guides](), [devices](), [documentation](), [embedded](), [embedded-replicas](), [fly](), [libsql](), [offline](), [platform](), [sdks](), [servers](), [sqlite](), [turso]() ### AI overview This article describes deploying Turso embedded replicas on Fly, Akamai, Koyeb, Railway, and Render. It also explains Turso's SQLite-based architecture, including querying databases over the network, syncing with devices and servers, offline support, and the distinction between database files and processes. ### Source excerpt Deploy Turso embedded replicas on your favourite platform. ## Speeding up a Remix website with Turso's embedded replicas hosted on Akamai's Linode DevFeed: [Speeding up a Remix website with Turso's embedded replicas hosted on Akamai's Linode]() Original publisher: [Read original article]() Author: James Sinkala Published: 2023-11-30T00:00:00Z Content type: article Language: en Sources: [Turso Blog]() Topics: [Turso](), [Embedded Replicas](), [Remix](), [Linode]() Tags: [akamai](), [embedded-replicas](), [linode](), [multitenancy](), [remix](), [turso]() ### AI overview An older post describes using Turso's embedded replicas to speed up a Remix website hosted on Akamai's Linode. The accompanying note explains that Turso has since been rewritten and now supports querying databases over the wire or syncing them with devices and servers for offline use. ### Source excerpt Using Turso's embedded replicas to speed up a Remix website hosted on Akamai's Linode ## CDNs: Speed Up Performance by Reducing Latency DevFeed: [CDNs: Speed Up Performance by Reducing Latency]() Original publisher: [Read original article]() Author: Austin Published: 2023-05-01T14:57:05Z Content type: tutorial Language: en Sources: [Back End - Austin Gil]() Topics: [Latency](), [Cache](), [Cloud](), [cloud-infrastructure](), [cloud-computing]() Tags: [akamai](), [architecture](), [back-end](), [cache](), [cloud](), [cloud-computing](), [coding](), [development](), [latency](), [optimization](), [performance](), [programming](), [software](), [speed](), [uploads](), [web](), [web-development]() ### AI overview This tutorial explains how content delivery networks reduce latency for files stored in object storage. It describes caching copies near users and reports a reduction in one Japan-based request from 1.1 seconds to 0.2 seconds when served through a CDN. ### Source excerpt This post covers what CDNs are, how they work, and why you need one. I also show you how to connect Akamai CDN to Object Storage. ## Caching GraphQL results in your CDN DevFeed: [Caching GraphQL results in your CDN]() Original publisher: [Read original article]() Author: Sashko Stubailo Published: 2018-04-06T21:05:00Z Content type: tutorial Language: en Sources: [Apollo Blog]() Topics: [GraphQL](), [Caching](), [HTTP](), [API]() Tags: [akamai](), [announcement](), [api](), [caching](), [cdn](), [cloudflare](), [graphql](), [http](), [optimization](), [rest-apis]() ### AI overview This tutorial explains how to cache GraphQL API results in a CDN. It describes using edge caching for infrequently changing public data, improving load times and reducing server load, while noting that caching is less useful for frequently changing or private data. ### Source excerpt At first glance, it might seem like GraphQL is so different from REST and other HTTP API technologies that you have to rethink all of your infrastructure from scratch. But it turns out that it's not hard to add GraphQL to your existing setup and start getting the benefits you want right away, without having to rebuild anything you already have. - You can keep your existing backends and business logic, since you can put GraphQL over REST APIs.