CDNs and Cloud Infrastructure

With the aim of creating a more comprehensive picture of global cloud and CDN infrastructure, I have collected data scraped from various service provider websites into CSV and GeoJSON format. So far, I have collected information from:

• Cloudflare's Global Network
• Amazon Global Edge Network
• Microsoft Edge Locations
• Google Edge Network and GGC Locations
• Google Owned Data Center Locations
• Fastly PoPs
• Facebook (now Meta) Network Appliances
• Akamai
• Netflix Open Connect Appliances (OCAs)
• CacheFly

For the above, I took the cache locations from the websites and geolocated them. Thus the map is only accurate to city level. The dates in the filenames indicate the last time the relevant website was checked.

For the Facebook Network Appliances, I have drawn on Anurag Bhatia's very creative work in work in locating them by the airport code in their names.

For the Netflix Open Connect Appliances, I used SecurityTrails to look for subdomains under oca.nflxvideo.net. A typical OpenConnect appliance subdomain looks like http://ipv4-c008-muc001-ix.1.oca.nflxvideo.net/. Similar to the Facebook Network Appliances, there is a three-letter airport code embedded in the url. I used the airport codes to geolocate the OCAs. There is no guarantees that all of those domains are actual live appliances but it is a place to start. I should also say that the maximum number of subdomains that SecurityTrails would list was 10,000. Thus this list is not exhaustive as there were clearly more. Other handy information in the url includes whether the appliance is located at an IXP or and ISP and whether it is IPv4 or IPv6.

This is very much an exploration so comments and suggestions are extremely welcome. Feel free to reach out to me here or on social media @stevesong@mastodon.cloud or @stevesong

The repository's original dataset is published under the Open Data Commons Attribution License (ODC-By) v1.0. Provider snapshots and independent research downloads may remain subject to their source-specific terms; provenance files record known licensing status, and no blanket relicensing is assumed.

Repository layout

• data/ contains the current provider snapshots.
• data/manifest.20260805.json is the current consolidated hash/count/source manifest for 28 location-schema layers, five derived views, three network-evidence layers, and the China assessment artifacts. It preserves the actual 2026-08-04 tags of older layers.
• Schema-normalized location layers are committed as canonical GeoJSON and network assertions as canonical JSON; their CSV projections are generated on demand with jq and make.
• data/google/ contains schema-normalized Google Edge and Google Data Center layers.
• Provider subdirectories under data/ contain schema-normalized authoritative refreshes dated 2026-08-04 or 2026-08-05; each manifest entry records its actual snapshot tag.
• data/china/ records the ten-provider mainland public-cloud assessment; provider directories contain generated cloud layers and explicit mainland views.
• data/china-edge/ records the separate ten-provider CDN/edge assessment without manufacturing POPs from fleet totals or province coverage.
• data/china-colocation/ records the separate GDS, VNET, and Chindata assessment; data/chindata/ contains the partial code-based current directory.
• data/observations/ contains independent evidence kept separate from provider declarations, including Apple CDN presence.
• data/network/ contains non-spatial provider-prefix, RIPEstat routing/RPKI, and bounded PeeringDB relationship evidence. These records are not locations.
• data/quarantine/ preserves unsupported or provenance-conflicted layers without presenting them as current.
• data/raw/ contains immutable upstream snapshots used for reproducible recovery.
• data/recovered/ contains derived records that restore discarded identity and network fields. The original provider snapshots remain unchanged.
• archive/ contains superseded historical snapshots.
• schema/ contains separate canonical location and network-evidence contracts and field semantics.
• scripts/ contains deterministic recovery and provider-update tools; tests/ validates their checked-in outputs.
• docs/ contains coverage assessments, methods, recovery notes, and operator guidance.
• docs/methods.md documents source selection, refinement rules, coordinate policy, parsing exceptions, observation limits, quarantine, and reproducibility.
• docs/hyperscalers.20260804.md assesses core-cloud coverage for a ten-provider hyperscaler cohort and proposes a staged enrichment plan.
• docs/hyperscalers.implementation.20260805.md records the implemented CoreWeave, AWS, Google Cloud, Azure, OCI, IBM, IBM classic, and Meta layers.
• docs/network-evidence.20260805.md records the ASN correction, partial city map, provider prefixes, RIPEstat/RPKI pilot, bounded PeeringDB pilot, and RIPE Atlas measurement gate.
• docs/make.md documents CSV generation, cleanup, validation, refresh usage, and troubleshooting.

The 2024 Meta FNA source fields and the reconstructable 2023 Netflix OCA hostnames have been recovered. See the recovery record for provenance, confidence levels, limitations, and regeneration commands.

Google Edge and owned data centers are now separate normalized layers. See the Google layer record for source semantics, updater options, null-geometry handling, and validation commands.

Cloudflare, Azure Front Door, AWS CloudFront and Local Zones, Fastly, CacheFly, Alibaba, Tencent, Baidu, Huawei, Volcano, Kingsoft, JD, Tianyi, and the partial Chindata directory have normalized refreshes dated 2026-08-04. Google Edge and owned data centers remain distinct options. China Mobile and China Unicom are explicit public-cloud source gaps; China edge/CDN marketing aggregates and the GDS/VNET portfolio totals remain assessments rather than speculative points. The corrected June 2026 ASN layer adds 13,631 valid Google, Netflix, Meta, Akamai, Microsoft, Apple, and CloudFront observations. A separate partial KML contributes 11,659 MaxMind city observations for Google, Meta, and Netflix. Provider prefixes, sampled RIPEstat routing/RPKI state, and bounded PeeringDB registrations remain separately counted non-spatial evidence. See the immutable baseline assessment, the implemented reassessment, and methods.

The hyperscaler assessment identified the missing core hierarchy, and the implementation report records 613 new provider-declared records across eight layers. These include seven CoreWeave super regions and 56 AZs; 39 AWS regions and 108 itemized stable AZ IDs; 43 Google regions and 130 zones; 57 Azure regions; 45 OCI regions; 13 IBM regions and 40 universal zones; 42 separate IBM classic data centers; and 33 Meta directory locations. All new geometry is intentionally null.

The refinement pipeline uses provider-approved, licensed, public filing/tender, and reproducible measurement evidence. Unauthorized or leaked inventories are not used to fill gaps; source and authorization rules are documented in methods.

To generate every normalized CSV projection, run make csv. To generate one file, name it directly, for example make data/network/provider-prefixes.20260805.csv. Column order comes from the applicable schema, and arrays or objects are emitted as compact JSON. These generated files are ignored by Git. Raw source CSVs, recovered outputs, and historical CSVs remain retained because they contain evidence or fields that cannot necessarily be reconstructed from canonical JSON. See Make usage for cleanup, validation, refresh, and troubleshooting details.

I am grateful to Mozilla for affording me the time to produce this map. Any errors are of course my own responsibility.