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 on Ben’s steer (“A. Yes. add it.”) after the story 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.
• Caught by the broad collector sweep, not the cluster agents — all four tier-2/3 agents were pointed at memory, macro and mental health and missed it. 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.