How Much of the Web Runs on Virginia's Grid? 3.6% of 290 Million Websites — and Nearly Half Answer From No Single Grid at All

On September 16 the House passed the Ratepayer Protection Act 417–3. The next day Senator Martin Heinrich objected when it came up for unanimous consent in the Senate, and offered his own GRID Savings Act, which would give federal regulators authority over any single load of 150 megawatts or more (CBS News, CNBC, Utility Dive). The fight is about who pays for the power data centers draw, and it is argued in megawatts and dollars. Data centers were 28% of Dominion Energy Virginia's electricity sales in 2025, up from 21% in 2022 (Dominion 2025 10-K, 2023 annual report). PJM's capacity auctions have cleared at their price cap three times in a row, and PJM's independent market monitor attributes $23.1 billion of the cost of three auctions to data-center load (Monitoring Analytics).

The other side of that ledger is almost never measured: how much of the Internet itself depends on that grid. The usual answer is a slogan. Loudoun County's economic-development office still says that "more than 70% of the world's internet" courses through the networks of its companies (Loudoun Economic Development). TeleGeography said in 2019 that "there's just no way" this is true (TeleGeography), and when Cardinal News traced it in 2025, Virginia's own economic-development agency did not know where the figure came from. What is verifiable is that the region is the world's largest data-center market: about 13% of reported global operational capacity (JLARC) and nearly 7 GW of inventory (JLL). And when one AWS region there, us-east-1, published an empty DNS record for its DynamoDB endpoint on October 20, 2025, Reddit, Snapchat, Venmo, Disney+ and the UK's tax portal failed with it (AWS, CNBC).

We could not find a published measurement of how many websites are served from Northern Virginia. The nearest is a 2013 study that found 74% of EC2-hosted subdomains in AWS's US East region, and at least 2.3% of the Alexa top million depending on it (He et al., IMC 2013). Traffic is not measurable from DNS, and neither is power. What DNS does show is where each website answers from.

We measured that. For each of 29 full A-record crawls of the DomainsProject corpus, April 2023 to September 2026, we took the website record of every registrable domain — the same 169 to 290 million websites as How Many Computers Host the Web? — and located every address in it. We used the best evidence available for each address, in this order: anycast and CDN edge lists; 213 Globalping round-trip measurements; the cloud providers' own region tags, in the version current at each crawl; RFC 8805 geofeeds; and geoIP. Each location then maps to a metro, a US state and a grid operator. This is not an energy estimate. A website count says nothing about megawatts, and this post does not convert one into the other. It measures dependency: where the web goes dark if one place, or one grid, does.

The headline: Northern Virginia serves 3.60% of the world's websites — 10.4 million in September 2026 — which is more than any country except the United States and Germany, 6.8% of all websites we can place anywhere, and 21.0% of those we can place in the US. It is the largest single hosting metro on the map. But it is not growing. Its share was 3.77% in April 2023 and has stayed between 3.40% and 4.10% in every crawl since. For live, non-parked websites it fell by more than a quarter (3.79% → 2.70%). What grew in Virginia is parked inventory: a third of the websites answering from Northern Virginia are HugeDomains for-sale pages on AWS us-east-1. The fastest-growing place on the map is no place at all: 47.0% of websites now answer only from anycast and CDN front doors with no single location and no single grid, up from 30.6%.

The Data

A website is a registrable domain with a website record in that crawl: the addresses its bare apex resolves to, or its www if the apex does not resolve. The universe, exclusions and parked/live split are exactly those of How Many Computers Host the Web?, Where the Web Moves and The Parking Lot. Our scanner reproduces that post's website count to the domain in every crawl (289,735,675 in September 2026). The corpus grew 1.7× over the window, most of it in one December 2024 expansion of the crawler's known-name list, so this post reports shares and controls for composition with a fixed panel of the 108.5 million websites present at both ends.

Methodology

Definitions.

• Share of websites. A website with k addresses counts 1/k at the location of each. Shares add up to 100%. "Answers only from X" means every address in the record is in X.
• Location. Where the address that answers is served from. It is not where the company is, not where a CDN's origin server sits, and not where the visitors are.
• Edge / anycast. An address announced from many sites at once (anycast), or handed out per resolver by a CDN (DNS-steered). It has no single location and no single grid. The same Cloudflare address serves a Virginia visitor from Ashburn and a Frankfurt visitor from Frankfurt.
• Metro. A data-center cluster. Northern Virginia is everything within 80 km of Ashburn on the Virginia side: Loudoun, Prince William and Fairfax counties and their neighbours. Washington DC–Maryland is a separate metro, which geoIP matters for (see below). Microsoft places its East US and East US 2 regions only in "Virginia", with no city (Microsoft). Our pings put East US in Northern Virginia (1.1–1.7 ms from two Ashburn probes) and East US 2 outside it (5.1–5.7 ms). So East US counts to the metro, and East US 2 only to Virginia, the state.
• Grid. In the US, the ISO/RTO — PJM, ERCOT, MISO, SPP, NYISO, ISO-NE — or the non-RTO West and Southeast. California is labelled "CAISO + municipal BAs" because Los Angeles's DWP and Sacramento are separate balancing authorities. Assignment is by state, overridden by metro where a state is split (Chicago → PJM via ComEd, Kansas City → SPP, Council Bluffs → MISO). Outside the US, a location maps to its national grid. Northern Virginia sits in PJM's Dominion zone, which the EIA calls "the largest concentration of data centers in the world" (EIA).
• Parked / live. A website whose addresses are a parking, for-sale or expiry front door in the registry of The Parking Lot is parked. Everything else is live.

Evidence tiers. Each address takes its location from the best evidence available:

1. Edge lists. Cloudflare's ips-v4 list and AS13335; Fastly's public list and AS54113; Akamai's edge ASNs; AWS ip-ranges.json prefixes with region GLOBAL (CloudFront, Global Accelerator); Google Cloud cloud.json scope global; Google ranges outside cloud.json (Google's own front ends); Azure Front Door.

2. RTT measurements. Globalping pings of 154 addresses, 213 measurements in all.

   • Screen. Eighty addresses were pinged from seven probes, one per city: the 78 heaviest that only geoIP or a geofeed could place, and two controls of known location. The probes were in Ashburn, New York, Dallas, Los Angeles, Frankfurt, Singapore and São Paulo.
   • Northern Virginia sample. Twenty geoIP-only Northern Virginia addresses, pinged from Ashburn (see below).
   • Review checks. After publication, a reviewer's questions prompted 81 more measurements of 54 addresses, from probes in the claimed cities themselves. They covered weight-proportional samples of 20 geoIP-only Hong Kong and Phoenix addresses, Azure's East US regions, and the refuted "Ashburn" addresses, tested from the cities where their operators run data centers.

   Light in fibre covers about 200 km per millisecond one way, so a target is at most 100 km from a probe for every millisecond of round trip.

   • Anycast. If two probes' discs cannot intersect, the address is anycast, and its whole /24 moves to edge: anycast is a property of the announced prefix, and /24 is the smallest prefix routed globally.
   • Pinned. A unicast address within 2 ms of a probe takes that probe's metro. This is a speed-of-light proof.
   • Refuted. An address loses the metro geoIP gave it if no probe in that metro reaches it in under 5 ms, while the same probes reach hosts in their own city in 0.5–1.9 ms. This is a strong heuristic, not a proof: a round trip bounds distance only from above, and bad peering could make a local host look far away. Every Northern Virginia refutation was re-tested from three Ashburn probes on three networks (Oracle Cloud, AWS and Hetzner Cloud), over TCP as well as ICMP. A refutation is a proof only when a probe's disc excludes the claimed city.

3. Region tags. The cloud provider's own published region for the prefix: AWS region and network_border_group (so a Local Zone in Boston or Dallas is not counted as us-east-1), Google Cloud scope, Azure service tags, Oracle regions. The AWS, Google and Oracle files are the Wayback Machine captures nearest each crawl — AWS within 23 days, Google within 45, Oracle within 95 — so every crawl is labelled with the region map in force at the time.

4. Geofeeds. RFC 8805 files self-published by DigitalOcean, Linode/Akamai and Vultr.

5. GeoIP. DB-IP City Lite (CC BY 4.0), September 2026 edition, for everything else.

What the RTT checks changed. Speed of light proved 15 /24s anycast, and each was a platform geoIP had pinned to a single city. Squarespace ("New York") answered in 1.6 ms from Dallas and 1.3 ms from Singapore. Wix ("Washington DC") answered in 1.3 ms from Ashburn and 25 ms from Frankfurt. Vercel's four prefixes ("Atlanta", "Los Angeles"), WordPress.com ("San Francisco"), Hostinger's two parking prefixes ("Vilnius"), Render, Nameshift ("Amsterdam"), Bodis ("Tampa") and a small GoDaddy block ("Phoenix") behaved the same way. Together these carry 8.96% of all websites in September 2026. A map built on geoIP alone would have put them in specific cities, and on specific grids.

Were they anycast in 2023 too? The verdicts come from September 2026 pings but are applied to all 29 crawls. So we checked them against public RIPE Atlas pings of the same prefixes made during the series, with the same disc test:

• Wix and Squarespace were already anycast in 2023. A Wix address answered in 0.32 ms from the US and 10.3 ms from the UK, 7,705 km apart, in May 2023 (#54212174). Squarespace failed the test the same month (#54564975).
• So were the others with 2023 websites. Render (April 2023), Hostinger's parking prefix (June 2023) and Vercel's original prefix (August 2023) all failed the single-location test then.
• Bodis's prefix held the same verdict until Bodis shut down. Bodis closed on January 31, 2026, but its /24 is still announced, by Amazon (AS16509), which has originated it without a break since February 2021 (RIPEstat). Public pings of it fail the single-location test every time from April 2023 to November 2025: its lander of October 2023 answered in 0.62 ms from the US and 1.08 ms from Australia (#61808255).
• The newer prefixes carried websites only after they were anycast. That covers Vercel's three newer prefixes, Hostinger's newer parking prefix and Nameshift.
• One prefix is untested. WordPress.com's (0.87% of websites in April 2023) has no public measurement. Automattic has announced it from its own network since 2013.

Nor can these verdicts manufacture the edge trend. RTT-proved platforms carry 8.1% of websites in April 2023 and 9.0% now. Without them the edge would still rise from 22.5% to 38.1%.

Unicast checks re-located another 2.45% of websites, either pinning them to a probe's metro or taking away a metro geoIP had wrongly given them:

• Pinned elsewhere. Confluence Networks' parking fleet is in Dallas (0.8 ms), not Jacksonville. BuyDomains' for-sale lander, which DB-IP puts in Ashburn, answers two Boston datacenter probes in 1.7 ms, and its traceroute hands off to Newfold in Boston.
• Not in Ashburn. Newfold's Network Solutions block 209.17.116.0/24, which DB-IP also puts in Ashburn, answers an Atlanta probe in about 1 ms.
• Not in Phoenix. Namecheap's URL-forwarding service (162.255.119.0/24, 0.78% of all websites) is a third of what geoIP calls Phoenix. No probe anywhere reaches it in under 22 ms, and two Phoenix probes that reach real Phoenix hosts in 0.6–1.9 ms take 23–44 ms. It cannot be pinned anywhere, so it is unresolved.
• Not in Melbourne. Trellian's "Melbourne" parking servers are within 450 km of Los Angeles.

Refuted addresses keep their country when a probe bounds it, but lose their metro, state and grid ("unresolved", 1.29% of websites).

How good is the geoIP tier? Where a cloud region tag gives the answer, DB-IP names the same metro for 94.3% of the websites whose region maps to one of our metros, and 88.9% overall (the rest are place-name mismatches such as Eemshaven/Groningen). For the websites AWS places in us-east-1 the agreement is 99.9%. It falls to 49.9% for us-west-2, which DB-IP spreads across Portland and Silicon Valley. And it is 0% for Google's us-east4, which Google documents as Ashburn but DB-IP (following Google's own geofeed) places in "Washington DC".

For the geoIP-only part of Northern Virginia itself, we drew a weight-proportional sample of 20 addresses from its 909 heaviest, separate from the 80 above. We tested each from two Ashburn probes:

• Confirmed: 14 answered in 0.5–1.9 ms.
• Refuted: 5 answered in 14–19 ms at best, and again on a re-test from three Ashburn probes over ICMP and TCP. Four have since been ruled out by speed of light. Two Network Solutions addresses answer an Atlanta probe in about 1 ms. A third answers it too fast to be anywhere in Northern Virginia. A TotalChoice server answers a Detroit probe in 0.44 ms. The fifth, a ServerCentral address with 256 websites, answers no probe faster than 19 ms, and its traceroute ends at ServerCentral's Chicago routers.
• No reply: 1.

That is 74% precision among the 19 that answered (70% if the silent one counts as a miss), with a 95% interval of 49–91%.

• What the correction applies to. Refuted addresses are already excluded from the metro, so the correction applies only to the 0.68 points of Northern Virginia that rest on unverified geoIP.
• How big it is. At the point estimate, Northern Virginia's 3.60% overstates by 0.18 points; across the interval, by 0.06–0.35 points.
• What the sample covers. It came from the heaviest addresses, which hold a third of that geoIP weight; the long tail of 78,000 smaller addresses is untested.

The region-tagged part alone is 2.86%.

At country level, DB-IP agrees with the crawler's own geoIP (taken at crawl time) for 91.5% of geoIP-tier websites in April 2023 and 90.4% in September 2026. The disagreement is between databases, not a decay with age. At metro level the two agree far less. We geocoded the crawler's own city for a sample of crawl shards (167 of 1,206 in April 2023, 200 of 3,170 in September 2026). By answers, the crawler's city matches DB-IP's metro for 94–98% of Northern Virginia placements, but for only 37–61% of London, Amsterdam and Paris placements, and 18–20% of Frankfurt's, in both years. Where the two disagree about a trend, we say so (see the Dublin section). Applying the September 2026 AWS, Google and Oracle files to the April 2023 crawl, instead of the contemporaneous ones, changes Northern Virginia's share by less than 0.001 points.

Known limitations.

• Front door only. We see the address a website's name resolves to, not the origin server behind a CDN, and not the backend a site calls. The October 2025 outage broke sites through DynamoDB, not through their A records. Everything here is a lower bound on dependency.
• Domains, not traffic or power. A parked page and a bank count the same. Nothing here converts to megawatts, and nothing here tests the "70% of traffic" claim, which is about packets.
• IPv4 only. Website records here are A records; a website reachable only over IPv6 is not measured (see The IPv6 Mirage for how far the two address families diverge).
• Current files applied backwards. The Azure, geofeed, edge and DB-IP files are September 2026 versions, and so are the RTT verdicts. The AWS/Google/Oracle test and the RIPE Atlas back-dating above suggest the effect is small, but an address reassigned between providers during the window would be misplaced.
• Grid by state. Split states follow their main data-center metro. Azure East US 2 is counted to Virginia but not to Northern Virginia: it answers Ashburn in 5.1–5.7 ms, which fits Microsoft's southern Virginia campus but does not prove it. AWS lists a us-east-1 zone "coming in 2026" in Maryland (AWS), which is also PJM.
• Excluded. Russian-administered TLDs are excluded from every figure.

Reproducibility. Per-chart CSVs are linked under each chart. The full 29-crawl series (grid-series.csv), the per-TLD cut (grid-tlds.csv) and every RTT measurement, including the review checks, with its verdict, probe set and Globalping measurement ID (grid-rtt-verdicts.csv) are published alongside.

The Scorecard

One website in 28 answers from Northern Virginia. That is a lot for one metro, and nowhere near "most of the Internet". The region serves more websites than any country except the United States and Germany: 3.60%, against Hong Kong's 3.08%, the Netherlands' 2.32% and France's 2.21%. Among the websites we can place in the US, one in five is there. Data → inference: at the level of registered names, Northern Virginia is the largest single place the web lives, and its dependency footprint is 10.3 million websites answering from nowhere else. Implication: a regional power or network event in Loudoun and Prince William counties has a direct, DNS-visible blast radius of about 3.5% of the web, before counting the backends, APIs and CDN origins that DNS cannot see.

Where the web answers from

Download: grid-metros.csv — share of 289.7M websites, September 18, 2026 crawl; notes give the evidence tiers behind each metro.

Northern Virginia is first by 0.52 points, and the order survives the uncertainty in both places. Even at the low end of the 95% interval for its geoIP-only part (see Methodology), Northern Virginia stays at 3.25%. Hong Kong's 3.08% is 88% geoIP, spread thinly over many addresses, but it held up when tested: all 16 addresses that answered, from a weight-proportional sample of 20, were within 3.4 ms of a Hong Kong probe. Its rise from 1.76% in 2023 comes mostly from names new to the crawl, hosted by small Hong Kong networks. On the fixed panel of websites present in both years it moved only from 1.15% to 1.41%.

Northern Virginia is also the best-evidenced entry on the list: four-fifths of its weight comes from AWS, Google, Oracle and Azure's own region tags, while almost every other metro rests on geoIP. That matters for three of the names below it:

• Phoenix. It ranked third at 2.45% before local probes showed that a third of it, Namecheap's URL-forwarding block, is not there (see Methodology). Of the other 13 sampled addresses, 9 answered Phoenix probes within 2 ms.
• New York–New Jersey. A geoIP-only map would rank it second at 3.9%. It falls to 0.74% once Squarespace's four addresses are recognised as anycast.
• Washington DC. GeoIP gives it 2.7%. It falls to 0.18% once Wix's addresses are recognised as anycast.

Both platforms were already anycast in 2023.

Ashburn Is Not a Country, But It Beats Most of Them

Download: grid-tlds.csv — the 58 TLDs with at least 250,000 websites plus all others combined, for all and live websites, with edge shares and shares of located websites.

Virginia's weight is an American weight, and parking distorts the raw TLD numbers. More than half of the .com (52.5%) and .ai (56.1%) websites answering from Northern Virginia are parked or for sale; for .com, most of that is HugeDomains' inventory. On the live web, where Northern Virginia's average is 2.70%, it serves 17.4% of .us websites and 3.9–4.8% of .co, .ca, .org and .com. Two Latin American ccTLDs, .ar (5.4%) and .mx (4.3%), rank above .com. The startup TLDs are not especially exposed: .io is at 3.04%, and .ai, at 2.69%, is at the average. They look high only as a share of located websites, because more than half of live .io and .ai sites answer from the edge. European ccTLDs barely touch Northern Virginia: 0.22% of live .de websites and 0.38% of .fr answer from there, because Germany and France host their own. Data → inference: Northern Virginia's footprint is geographic, weighted to the Americas and to .us above all, not a startup or SaaS footprint. Implication: an outage in us-east-1 lands hardest on the American web and hardly at all on the European small-business web. It does not fall disproportionately on .io and .ai names.

The Fortune 500 is more exposed than the average website, and moving away. 9.7% of Fortune 500 corporate websites answer from Northern Virginia (11.2% in 2023). A quarter of those are on Azure East US, which our pings place there. Another 1.3% sit in Azure East US 2, elsewhere in Virginia. But half of the Fortune 500 (50.4%, up from 32.8%) now answers only from edge networks — Cloudflare 17.9%, Akamai 14.7%, Fastly 6.8% — which hide their origins from DNS.

Virginia's Biggest Web Tenant Is a For-Sale Sign

Download: grid-nova-who.csv — share of the 10.4M websites answering from Northern Virginia, September 2026; operator from exact-address labels and /24 → ASN.

The largest single tenant of Northern Virginia's data centers, counted by websites, is a domain-for-sale marketplace. HugeDomains serves 3.46 million for-sale pages from two AWS us-east-1 addresses, up from 0.61 million in 2023. It ran a 12-address EC2 fleet until August 2025 (The Parking Lot). With Atom.com and GoDaddy's us-east-1 front doors, 43.9% of the websites answering from Northern Virginia are parked or for sale, up from 16.2%. That figure counts each website by its parked classification. The operator shares in the table are per address and sum to 44.1%, because a few websites mix a front-door address with a live one. Meanwhile, websites on AWS us-east-1 addresses outside the front-door registry — the customer web — grew 9.7% in count while the corpus grew 71%.

Data → inference: the growth in Virginia's website count since 2023 is almost entirely inventory, not publishing. Implication: for the grid and ratepayer debate, the web's dependency on Northern Virginia is smaller, and less valuable, than a raw count suggests. For registrars and marketplaces, one region holds a large share of the aftermarket's shop windows.

Did the Web Leave Virginia? Not Overall. Live Sites Did.

Download: grid-nova-trend.csv — share of websites answering from Northern Virginia per crawl, by group, with the evidence split (AWS / Google / Oracle / Azure region tag vs geoIP).

Over three and a half years, the web neither concentrated in Northern Virginia nor left it. The all-websites line never left a 3.40–4.10% band. Its one spike, December 2024, is the crawl expansion: the newly added names were disproportionately parked, and parked pages sit disproportionately in us-east-1. Under that flat line, two opposite movements cancel:

• The live web is leaving. Live websites answering from Northern Virginia fell from 3.79% to 2.70%. The composition-controlled line, live websites present in both 2023 and 2026, fell from 3.73% to 3.36%, so existing websites moved out, not only new ones arriving elsewhere.
• Inventory is arriving. Parked pages in Northern Virginia went from 3.68% to 6.28% of the parked web.

Where did the live websites go? We followed every live website that answered only from Northern Virginia in April 2023 to its record in September 2026:

The share that vanished is close to the corpus-wide rate: 35.4% of all live websites of April 2023 have no record in September 2026. The corpus is built from known names, so a missing record means the name stopped resolving or left the crawl, not proven deregistration. Of the 1.06 million that stayed live and left Northern Virginia entirely:

• 43% went to the edge, the largest single destination.
• 27% went abroad, led by Brazil and Canada.
• 27% went elsewhere in the US.
• Only 4% moved to another AWS region. They did not move to Ohio or Oregon; AWS's regional share of the live web fell from 4.96% to 3.55%.

The edge is where the most leavers went, but most leavers went somewhere with a location.

Within AWS, Virginia gained. us-east-1's share of the live websites on AWS regional addresses rose from 35.5% to 42.4%. Counting parked pages, it went from 30.8% to 58.4%. That happened while us-east-1's share of AWS's own EC2 address space fell from 28.1% to 26.9% (AWS ip-ranges.json, March 2023 vs September 2026). The October 2025 outage is not clearly visible. The live share dipped from 3.05% in the crawl before it to 2.87% in the crawl after, and was fully back by January 2026 (3.05%). One-month moves of that size happen without an outage: the live share fell 0.15 points between the January and February 2026 crawls. With one crawl on each side, we cannot separate a response to the outage from noise, and the full rebound makes noise the likelier reading. Data → inference: the live websites leaving Virginia mostly stop resolving or move to other hosts, with the edge the largest single destination, while the websites staying on AWS increasingly stay in its default region. Implication: the concentration risk inside AWS is growing even as Virginia's share of the whole web holds still.

The Web Is Leaving the Map

Download: grid-edge-trend.csv — share of websites answering only from edge/anycast front doors per crawl, by group.

Almost half of all websites now answer from networks that have no single location, and therefore no single grid. The share rose from 30.6% to 47.0%. For live websites it rose from 23.1% to 35.3%. On the fixed panel of websites present in both years it rose from 28.2% to 35.9%, so existing sites are switching, not only new ones arriving on edge platforms. Parked pages were already mostly anycast (67.7%) and are now 81.9%, after GoDaddy moved its landers from a Google global load balancer to AWS Global Accelerator in 2023 (Where the Web Moves).

Anycast is not "nowhere". A Cloudflare website is served to Virginia visitors from Ashburn and to Frankfurt visitors from Frankfurt. In an Ashburn power event its Virginia traffic fails over to the next city. What anycast removes is a single grid dependency, not a physical one. Data → inference: the growth of the edge bucket, not any drift between regions, is the dominant change in where the web lives. Implication: "which grid is this website on?" has become the wrong question for half the web. The right one is "where is its origin?", and DNS cannot answer it. The providers can.

The Grid Map: PJM, Germany, and No Grid at All

Download: grid-operators.csv — share of 289.7M websites by US grid operator (state/metro rule) or national grid, September 2026.

PJM is the largest US grid for websites, and Germany's grid is larger than any US one. PJM carries 5.40% of all websites, and two-thirds of that is Northern Virginia. Germany carries 8.98%, on Hetzner, IONOS, Strato and the country's many regional hosts. Germany is one country with four transmission operators and PJM is one operator across thirteen states, so the comparison is between grids as a website would experience them, not between organisations. ERCOT, where Texas's data-center boom is sited, carries 1.07% of websites, down from 1.68%. Data → inference: the grids where data-center load is growing fastest are not where the registered web lives; that load is AI training, cloud backends and enterprise workloads, not websites. Implication: ratepayer arguments that invoke "keeping the Internet on" overstate what is at stake for the web itself, and in particular for Texas.

Dublin's Grid Problem Is Not a Web Problem

Ireland's data centres used 23% of the country's metered electricity in 2025, up from 5% in 2015 (CSO). Ireland serves 0.28% of the world's websites, down from 0.96% in April 2023; Dublin (AWS eu-west-1 and Azure North Europe) serves 0.27%, down from 0.93%.

The drop has two identifiable causes. We sampled tenants of Dublin's five busiest AWS addresses in April 2023 and looked them up live:

• Jimdo sites now answer from Cloudflare (162.159.128.70, the address How Many Computers Host the Web? traced to Jimdo).
• Customers of the Dutch host Mijndomein now answer from Mijndomein's own addresses in the Netherlands.

Europe's hub cities shrank on our map: Frankfurt 2.89% → 1.48%, Amsterdam 1.91% → 1.28%, London 1.78% → 0.90%, Paris 0.93% → 0.64%. Only two of those declines survive a second opinion:

• Frankfurt's is solid. It rests on AWS's own region files. In April 2023, 1.50 points of Frankfurt were GoDaddy front doors in eu-central-1, which later moved to AWS Global Accelerator; the geoIP-placed part of Frankfurt actually grew.
• Amsterdam's is solid. It also appears when the same crawl answers are located with the crawler's own geoIP, recorded at crawl time (0.60× against DB-IP's 0.70×).
• London's and Paris's are not. Under the crawler's geoIP, London grew (1.18×) and Paris held level (0.97×). At metro level the two geolocators agree on well under two-thirds of European placements, in both years, so these two declines may belong to DB-IP rather than to the web.

Data → inference: Ireland's electricity problem is driven by hyperscale workloads that have little to do with serving websites, and the websites it did serve are moving to the edge or home to their own countries. Implication: the European analogue of the Virginia debate is even further removed from the web than the American one.

What's at Stake

• About 10.3 million websites have no location outside Northern Virginia — 3.54% of the web. A regional event there — power, cooling, a transit cut, or another control-plane failure like October 2025 — has a direct, DNS-visible reach of one website in 28, before counting the backends those websites call. That is large for one place, and small next to the "70% of the Internet" slogan the region's boosters still use.
• Inside AWS, concentration is rising. 42.4% of the live websites on AWS regional addresses are in us-east-1, up from 35.5%. The companies still hosting on AWS increasingly pick its default region. The October 2025 outage did not measurably change that.
• Half the web's grid dependency is invisible. For the 47% on anycast and CDN front doors, the edge fails over, but the origin behind it sits somewhere DNS cannot see. The cloud edge providers know where their customers' origins are; nobody publishes the aggregate. Any statement about "how much of the web depends on Virginia" that ignores this half is guessing.
• Virginia's web growth is inventory. 43.9% of the websites answering from Northern Virginia are parked or for sale, up from 16.2%. Arguments that data-center growth there serves the public web should say which web.
• GeoIP maps of hosting are wrong where it matters most. Nine percent of all websites sit on platform addresses that geoIP pins to one city but that answer from many; one in four of the geoIP-only "Ashburn" addresses we sampled is not in Ashburn, and a third of geoIP's "Phoenix" is a redirect service that no probe reaches in under 22 ms. Hosting-geography statistics without a speed-of-light check overstate New York, Washington, Tampa and Phoenix, and misplace whole parking fleets.

What Would Help

1. Policymakers and utility commissions: ask for dependency data, not slogans. The "70% of the world's Internet" figure is still on a county website, and it reappeared in December 2024 in the consultant's deck for Virginia's legislative data-center study, attributed to "certain estimates" (E3 for JLARC, p. 8). A measured number exists: 3.6% of websites, 21% of US-located websites, and a rising share of AWS's. Ratepayer and siting decisions should cite measured shares and be explicit that website hosting is a small part of what the new load is for.

2. Cloud providers: publish region shares of customer workloads. AWS, Google and Microsoft publish address ranges by region, and those ranges made this study possible. Publishing the share of customer endpoints or origins per region, even as a coarse annual figure, would let resilience planners measure the concentration this post can only see at the front door. Microsoft could also say where its "Virginia" regions are; we had to ping East US to find it in Northern Virginia.

3. CDN and anycast platforms: disclose origin geography in aggregate. For 47% of websites the location that matters is the origin, and only the edge provider knows it. An annual "origins by metro" table from Cloudflare, Squarespace, Wix and Vercel would complete the dependency map, and it would not reveal any individual customer.

4. Measurement researchers: verify geoIP with speed of light before mapping hosting. 213 Globalping measurements of 154 addresses moved 9% of all websites from specific cities to the edge, refuted a quarter of sampled "Ashburn" placements and a third of "Phoenix", and confirmed Hong Kong. Probe from the claimed city itself, not only from the nearest hub, and check verdicts against public RIPE Atlas history before applying them to old crawls. Region tags from the providers themselves are far better than geoIP where they exist. Use the version current at each crawl (the Wayback Machine has them), and use AWS's network_border_group, not region, so Local Zones are not counted as us-east-1.

5. Site owners: know your single points of location. If every address in your website record is in one region, your site shares a fate with that region's grid and control plane. A second region, or an edge provider with a documented origin failover, removes a dependency that 10.3 million websites still have on Northern Virginia alone.

Methodology: 29 full A-record crawls of the DomainsProject corpus (April 7, 2023 – September 18, 2026), reduced to one website record per ICANN-registrable domain — bare-apex A record, else www — using the same merged tables, exclusions and parked/live classifier as How Many Computers Host the Web?, Where the Web Moves and The Parking Lot. Each address was located by edge list, RTT measurement (213 Globalping measurements of 154 addresses; 15 anycast /24s proved and back-dated with public RIPE Atlas pings), the AWS/Google/Oracle region file in force at each crawl (Wayback Machine captures) and the current Azure service tags (East US placed in Northern Virginia by RTT), RFC 8805 geofeeds, then DB-IP City Lite (CC BY 4.0). Registry-wildcard TLDs, private-suffix pseudo-apexes, DNS-filter sinkhole answers and Russian-administered TLDs are excluded from every figure. Data: series, metros, grids, Northern Virginia trend, edge trend, who is in Northern Virginia, TLDs, RTT verdicts. For where the web moved between providers see Where the Web Moves; for the country-level map see Where the Web Lives; browse the corpus on the TLD statistics pages or get the data on the dataset page.

Updated September 24, 2026, after an outside methodology review:

• Azure East US is now counted to Northern Virginia on RTT evidence. Northern Virginia goes from 3.53% to 3.60% in September 2026, and its Fortune 500 share from 7.3% to 9.7%.
• Namecheap's URL-forwarding block is no longer placed in Phoenix, which falls from 2.45% to 1.67%.
• Refuted "Ashburn" addresses were located elsewhere, and the anycast verdicts were checked against 2023–2025 RIPE Atlas pings.
• The TLD, precision, European-metro and live-web passages were corrected.