All
Outcomes
Market
Price
AI Fair
Value
Value
Edge
YesNo
AI Insights:
03.04 04:51 UpdatedFair Value Reasoning:
According to the latest public information dated March 3, 2026 (e.g., reports from The Times of India and AWS Health Dashboard snapshots), AWS data centers in the Middle East (UAE and Bahrain) experienced severe fires due to external attacks, and AWS explicitly classified the severity of this incident as 'Disrupted'. Per the market rules, any public service interruption classified as 'Disrupted' on the AWS Health Dashboard triggers a 'Yes' resolution. Since this event has already occurred and been confirmed within the timeframe, the intrinsic value of 'Yes' is 100 cents (adjusted to 99 for nominal settlement risk), making the current price of 29 cents a massive mispricing.
Sign up to view more information
Rule Risk
There is significant definition risk. Resolution relies solely on the official classification on the AWS Health Dashboard. The risk lies in the frequency of the specific 'Disrupted' label. AWS often uses milder terms like 'Degraded' or 'Informational' even during significant outages. If an outage occurs but is labeled only as 'Degraded', the market resolves 'No', potentially conflicting with the common perception of an outage.
Hedging
AMZN
AWS contributes the majority of Amazon's operating income, so a severe service interruption classified as 'Disrupted' typically triggers a short-term panic sell-off or reputational damage for AMZN stock, creating tradable volatility. For the Nasdaq 100, given AWS hosts a vast amount of internet infrastructure, a widespread outage could cause minor systemic jitters across the tech sector.
Divergence
Extreme divergence. The market price implies a 29% probability for 'Yes', whereas the triggering event (Middle East data center attacks causing 'Disrupted' status) has already occurred in reality, making the true probability 100%. This discrepancy is entirely due to information latency or a lack of active market participants.
