Analytics
“AWS service disrupted by July 31?” is a prediction market on Polymarket with two tradeable outcomes, Yes and No. It belongs to the event “AWS service disrupted by...?”. The Yes price is the market's implied probability that the question resolves Yes. Quotes can change as orders are updated or filled; a quoted price does not guarantee an available fill at that price.
This market resolved No on 2 Aug 2026. $775.71 traded over its life. The price history, the holders still on the books and the trade tape below are kept as the record of how the crowd priced the question while it was open.
Vultax observes this market from Polymarket's public order book and data API and keeps its own record: 32 daily price points from Jul 1, 2026 UTC to Aug 2, 2026 UTC (Yes between 15.0% and 50.0%); 5 wallets still holding shares after settlement, the largest ten holding 100.0% of the loaded shares; 17 recent public fills from 7 wallets. Each figure carries its observation time; nothing here is a return forecast.
This market will resolve to “Yes” if Amazon Web services experiences any service interruption event with a severity classification of “disrupted” by July 31, 2026, 11:59 PM ET. Otherwise, this market will resolve to “No.” The severity classification of an AWS service interruption event may be found on the AWS Health Dashboard (https://health.aws.amazon.com/health/status) when the relevant event is selected under “List of events.” Only publicly visible service events listed on the AWS Health Dashboard status page qualify. Account-specific AWS Health events do not count. Qualifying incidents may include outages and other issues whose severity AWS classifies as “disrupted.” This market will resolve as soon as the severity of any service interruption is classified as “disrupted”, regardless of subsequent revisions or corrections. Revisions to the severity classification of any event to a classification of “disrupted” will be considered as long as those revisions are published within this market’s timeframe. If an incident is ongoing at this market’s resolution time, the market may remain open until that incident receives an official severity classification, and it will resolve based on the first such classification published. The resolution source for this market will be official information from the Amazon Web Services Health Dashboard (https://health.aws.amazon.com/health/status).
Official listing: polymarket.com/event/aws-service-disrupted-by-june-30
Public Polymarket market/event context is available; Vultax source-pack coverage is tracked separately.
This closed market has no live orderbook depth; the public close quote is shown for context.
Nine stops, one per figure on this page. Each stop says what the number is, why it matters, and what it reads right now for this market.
Each outcome trades as a share that pays $1 if it wins and nothing if it loses. Prices are quoted in cents, and Yes plus No add up to about one dollar.
Daily closes of the Yes price, Polymarket CLOB · 32 points · 1 Jul 2026 – 2 Aug 2026
| Observed | Yes price |
|---|---|
| 1 Jul 2026 | 49.0% |
| 2 Aug 2026 | 49.0% |
| Trader | Outcome | Shares |
|---|---|---|
| TENETENET | Yes | 100 |
| 44444444ben | Yes | 79.93 |
| .Menthe | Yes |
The Yes price read as a chance. A share at 21.5¢ implies 21.5%, but fees, available depth and who participates can affect that price. A market price is not a calibrated forecast or a verdict.
Dollar value of shares that changed hands in the last 24 hours. High volume means the price is being tested by real money; low volume means a few trades can move it.
Reported dollars resting in the order book. The available size on your side, at the prices you would accept, determines what can fill. A large total alone does not guarantee an execution near the quoted price.
The gap between the best bid and the best ask. A tight spread makes entry and exit cheap; a wide spread is a cost paid on every round trip.
The wallets holding the most shares on each side, and how much of the loaded sample the largest ten control. Concentration shows whether a market is a crowd or a handful of large positions.
The public fills, newest first: which wallet bought or sold which outcome, at what price, and when. It is the market's own diary, and every wallet on it links to a trader profile.
Observed closes of the Yes price over the market's life. The range shows how sure or split the crowd has been; the move shows which way it has been changing its mind.
Trading stops at the close time. The outcome is then settled by the resolution source named in the rules. A closed market is not resolved until the venue reports it, so the two states are shown separately.
| 50 |
| triklozoid | Yes | 15 |
| rocketcrypto | Yes | 5 |