2026-10-01 — A third Kyiv data center goes down as dline.ua’s is destroyed

• The dline.ua data center on Predslavynska Street in Kyiv was destroyed in a Russian strike on 10-01, the company said, with all services and customer data moved to backup facilities Ukrinform counts it as the third Kyiv data center to report suspending operations in recent days; the Parkovy business-center facility ceased operations on 10-01 after critical damage. (Ukrinform)

2026-09-30 — Russia strikes the Bi-mobile and Parkovy data centers in Kyiv

• Russia’s overnight attack on Kyiv hit the Bi-mobile data center, which Russia’s Defense Ministry called one of the city’s main internet exchange points, and the Parkovy data center CNBC reports Russia has stepped up strikes on Ukrainian data centers and internet providers in recent days to disrupt the flow of information; the Ministry’s descriptions are its own claims. (CNBC)

2026-09-27 — Russia hits Kyivstar’s headquarters and claims a strike on Vodafone Ukraine’s data center

• A Russian drone struck the headquarters of Ukraine’s largest mobile operator Kyivstar on 09-27, and Russia’s Defense Ministry claimed it also targeted the data center of Vodafone Ukraine Breaking Defense, citing Reuters for the ministry claim, reports a recent surge in Russian attacks on Ukrainian data centers; Ukraine’s former deputy defense minister Kateryna Chernohorenko says the answer is more underground facilities and far more anti-ballistic and counter-drone capacity, which she calls critically short. (Breaking Defense)

2026-09-23 — A Russian strike on Kyiv damages two internet providers’ data centers

• Russian strikes on Kyiv on the morning of 09-23 damaged data centers run by the internet providers Pavutyna and UTELS, leaving about 100,000 households in the capital region with unstable internet, Ukraine’s Ministry of Digital Transformation said. UTELS said the data center holding its core network equipment lost power and Pavutyna said its engineers were working to restore connectivity; the same attack killed two people and wounded about 25, according to Kyiv’s mayor. (Interfax-Ukraine, UA.NEWS)
• Russian strikes overnight into 09-24 hit more data centers in Kyiv, destroying CityHost.UA equipment and the Ukrainian data center that housed MiroHost’s capacity, a day after strikes damaged the Pavutyna and UTELS facilities. Ukraine’s telecom regulator warned of temporary network disruptions; KIEVNET, Domonet, FAUST and Crazy Network (which said a missile hit a central traffic-exchange data center) reported outages, CityHost said it was rushing to deploy backups on equipment abroad, and MiroHost said about 95% of its clients are outside Ukraine and unaffected. (The New Voice of Ukraine)

2026-09-18 — AWS confirms permanent data loss at Bahrain, no restoration before 2027; the UAE responds by redesigning its flagship AI campus around the strike risk

• AWS posted its first public update since April on its own health dashboard (2026-09-15): it cannot restore access to resources and data hosted exclusively in its Bahrain region, and separately cannot recover one of three affected UAE availability zones (mec1-az2). Direct quote: “After a thorough assessment, we have determined that we are unable to restore access to the resources and data hosted exclusively in this region.” AWS said the Bahrain damage “spanned multiple Availability Zones and exceeded what our regional and multi-AZ services are designed to withstand” — the company’s own words confirming the strikes beat the design tolerance of a multi-AZ region, not just a single site. Bahrain customers get their next update in early 2027; the two other UAE zones remain under repair with updates promised “in the coming months.” Most customers had already migrated workloads or restored from backup after the March strikes, per AWS, but this is the first confirmation that some resources and data are gone for good, seven and a half months after the attacks and directly on this thread’s own “whether any hyperscaler discloses it” watch line. ⚠️ The widely-recirculating “$150 million loss, insurance won’t cover it” figure (Yahoo Finance, Moneywise, AOL and others, all published under September-looking URLs) is not new reporting — the underlying Yahoo Finance piece carries a machine-readable publish date of 2026-04-24; it is the same aggregator-recycling pattern this map has flagged before on this exact story, not a fresh disclosure. (CNBC, Insurance Journal)
• Separately, Reuters reported (2026-09-11) that the UAE is quietly redesigning its flagship 5-gigawatt Stargate AI campus — one of the largest AI infrastructure projects outside the US, a joint venture of OpenAI, Oracle and SoftBank — specifically because of the strikes. Originally planned as a single 10-square-mile Abu Dhabi campus, the project will now likely be a dispersed network of smaller sites; measures under consideration include underground construction, blast-resistant materials, backup power/cooling, drone- and missile-defense equipment, and siting the most sensitive facilities inside mountains. This is exactly the “siting decisions that cite geopolitical risk” this thread’s watch line has been waiting to see, and the first case of it landing on a named, dollar-figured flagship project (Stargate UAE’s first phase is $30bn/1GW) rather than a generic industry-wide warning. (Reuters, via U.S. News)
• Insurance broker Howden reported that data-centre capacity within 10 to 15 kilometres of active conflict zones in 2025 equalled about 60% of everything recorded in the previous five years combined, after Iranian drones struck five data centres in the UAE and Bahrain earlier this year. Howden urged insurers to align cyber, property and war policy wording as data-centre risk turns physical as well as digital, and separately counted large data-centre lawsuits rising from four in 2021 to 14 in the first half of 2026, mostly planning and noise disputes. Coverage of the research began on 09-18. (London Insider, reporting the Howden research, OilPrice)

2026-07-30 — The thread’s own live test came back: no disclosure

Logged 2026-08-18 by the cold rotation, nineteen days after the answer became available. This thread named Amazon’s 07-30 earnings as “the first live test” of whether any hyperscaler would disclose the strikes.

• Amazon disclosed nothing. Not in the 10-Q, not on the call. Checked directly against both primary documents: the Form 10-Q for the quarter ended 2026-06-30 and the 2026-07-30 Q2 earnings-call transcript contain no mention of Iran, drones, missiles, Bahrain, the UAE, war risk, or physical attacks on AWS facilities — not in risk factors, not in legal proceedings, not anywhere in the call. (Amazon 10-Q)
• What makes the null meaningful is that AWS did acknowledge the strikes — to reporters, through a spokesperson, at the time they happened. A PR-channel acknowledgement and a securities-filing disclosure are different acts with different consequences, and the gap between them is now on the record for this thread. The war-risk term this thread argues sits unpriced across every capex thread is, on this evidence, also undisclosed.
• First commercial response to the vector: a Y Combinator-backed startup launched a missile-intercepting drone-defence service marketed to data centres and grid operators (2026-08-06). Adjacent: the FT reported 2026-08-17 that Meta and BlackRock’s $14bn data centre “exposes lenders to insurance gap” — financing-structure risk rather than war-risk premia specifically, but the first sign of lenders pricing physical exposure at all.
• ⚠️ Not new, recorded so it is not re-counted: the 07-28→30 wave of “satellite imagery confirms Amazon Bahrain data center hit” coverage re-reports the same 07-28 corroboration already in this thread.

2026-08-03 — Strike toll widens to “at least five”; first named underwriters go on record on war-risk pricing

• CNN reports the running toll has widened to “at least five” data centers struck in the Gulf region, framing it as both Iran and the US hitting data centers in this war — not only Iran striking Western hyperscalers — a wider framing than this thread has carried so far; Amazon’s Bahrain facility has now been hit twice (04-30 and 07-21). The same report cites an IRGC target list of 29 regional tech sites naming Amazon, Google, Microsoft, Nvidia and Palantir — Palantir wasn’t in this thread’s recorded 03-31 name set, worth verifying against the original Tasnim/Fars list rather than treating as confirmed-new (CNN’s citation may just be an abbreviated subset of the same 29). (CNN)
• First named underwriters on record about war-risk pricing — the exact effect this thread has been watching for: Marsh’s US property digital-infrastructure lead Joe Macejak said “some clients are looking at recent events and they’re thinking twice about whether they move forward, and some insurers aren’t comfortable taking on certain risks”; MSIG USA’s property head Philip Wray said data centers are “giant warehouses with really expensive equipment inside” with limited hardening options. First sourced confirmation of insurance-market reaction, not yet a filed premium number. (CNN)
• Checked and ruled out: Amazon’s Q2 earnings call (reported ~07-30) did not address the Bahrain strikes. CFO Brian Olsavsky’s only Middle East mention was generic (“heightened transportation costs driven by fuel inflation from the conflict in the Middle East”) — no reference to AWS facilities, Bahrain or Iran by name. Closes this thread’s “first live disclosure test” watch item with a negative finding, not a disclosure.

2026-07-29 — Opened

• Opened because the story had surfaced with no owner — it had been landing across Datacenter Sites, AWS Capex and Red Sea Shock, none of which could carry it as a standing variable. Scoped to physical targeting of compute infrastructure; the cyber/sabotage angle is adjacent and would widen it.

2026-07-28 — Satellite imagery corroborates the strikes on AWS Bahrain

• Imagery shows significant damage to two Amazon data centres in Bahrain — Zallaq and Askar — corroborating IRGC claims released via Tasnim. (Bloomberg · Tom’s Hardware)
• ⚠ The imagery is the 07-28 development, not the attack. The strikes were claimed around 07-21. Recorded as corroboration of an older event — the distinction matters because the campaign, not the incident, is what this thread tracks.
• Landed the same day Iran struck a US base in Jordan (5:45pm ET, all intercepted) — the first ballistic-missile attack on a US base since the 07-24 pause. Compute infrastructure and conventional military targets in the same 24 hours. The recall lesson is logged in coverage-log.md.

← Backstory

2026-04-01 — A further drone strike on Amazon in Bahrain

• An Iranian drone struck an Amazon data centre in Bahrain (FT).

2026-03-31 — Iran names its corporate target list

• Iranian state media said it would target American companies including Microsoft, Google, Apple, Meta, Oracle, Intel, HP, IBM, Cisco, Dell, Palantir and Nvidia — the declaration that turns individual strikes into a stated campaign.

2026-03-01 — The first strikes: AWS sites in the UAE

• Before dawn, Iranian Shahed drones struck two Amazon Web Services data centres in the United Arab Emirates; a third commercial data centre in Bahrain was hit, though whether it was deliberately targeted is less clear. Reported as the first time a country has deliberately targeted commercial data centres in wartime.