AWS Can't Restore Bahrain, UAE Data After Iran Strikes
financefeeds.com · Thu Sep-17 15:12:49 published · Thu Sep-17 15:20:19 alerted · alerted 7m after publish · read at financefeeds.com ↗ · other · mat 65
Amazon Web Services confirmed that data stored in its Bahrain and UAE data centers is permanently lost following Iranian drone strikes, raising significant concerns about cloud reliability for regulated industries.
overnight drift: short AMZN at close, exit next close (other: Amazon Web Services confirmed that data stored in its Bahrain and UAE data centers is permanently lost following Iranian drone strikes, raising significant concerns about cloud reliability for regulated industries.) [skipped at close: stale at close-fill — wanted short, verdict now PRICED (+2.24% since close, 335m after decision), order not placed]
📈 Trades
no trades spawned
📖 Glossary
S1 primary — trades the alert's primary ticker in the direction the article itself indicates; exits at the same day's close.
S2 counterparty — trades the inferred counterparty ticker (weakest signal, LLM-inferred sympathy); exits at the same day's close.
S3 peer — trades an inferred peer ticker (also LLM-inferred sympathy); exits at the same day's close.
S4 overnight — holds the primary ticker from today's close to the NEXT day's close.
Verdicts are decided top-to-bottom, first match wins; REPRICING is also the fallback when nothing else matches (2026-08-08 #220).
UNKNOWN — a needed price input (move since close or move in the last 30m) is missing.
PRICED — |move since previous close| ≥ 2.0%: already reflected in price.
REPRICING — |move in the last 30m| ≥ 0.5%: the tape is actively moving on it. Also covers a quieter move — |move since previous close| in [1.0, 2.0) with a quiet last-30m tape: still developing, not yet priced.
FRESH — |move since previous close| < 1.0%: a genuinely new move.
materiality — how market-moving the story was judged, 0-100 — alerts require materiality ≥ 70.