UnclassifiedExpires Jun 30, 2026
Creator

AWS service disrupted by June 30?

Probability

33¢

1h

+0.0pp

24h

-18.0pp

24h Vol

$2.2K

Liquidity

$23.1K

Resolution & Risk

LOW risk
End date
Jun 30, 2026
UMA status
n/a
Resolution source
Primary
the first such classification published
Type
Ambiguous wording
Confidence
extracted · low
Market type
Binary
  • No obvious resolution-risk signals in metadata.
Read full market rules on Polymarket

Probability (last 7 days)

+0.0pp 7d
Apr 30, 2026, 20:00May 2, 2026, 03:46
updated 0s ago·src:Polymarket CLOB

Why did it move?

Structured · 3 factors
  • 01
    Price move

    Down 18pp over 24h

    Now 33¢; flat in the last hour.

  • 02
    Active signal

    Resolution-risk signal firing

    Resolution source is ambiguous or relies on public-figure statements — verify before treating price as the market view.

  • 03
    Liquidity

    Thin liquidity

    Only $23.1k of visible book — small orders can move the line. Treat the probability as a soft estimate.

What to track next

  • Verify the resolution source on this page — exchange feed, official release, news consensus — before treating any move as new information.

Verification actions only — never trade recommendations.

Each factor is grounded in a single named metric you can verify on this page — probability, volume, liquidity, signal, resolution state. No predictions, no prose hallucinations.

Timeline

critical · price · trade flow

Critical

  • 0s agoResolve

    Market resolves in 1412.2h

    LOW
  • 03:46Signal

    Resolution risk

    Resolution source is ambiguous or relies on public-figure statements — verify before treating price as the market view.

    LOW

Price movement

-18.0pp over the last 24h, now 33¢.

updated 0s ago·src:Polymarket CLOB·Polymarket Data

Active signals

Recent Trades

No recent trades visible from the Data API for this market. That usually means liquidity is thin or this market is between event windows.

updated 0s ago·src:Polymarket Data

Market Description

This market will resolve to “Yes” if Amazon Web services experiences any service interruption event with a severity classification of “disrupted” by June 30, 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).

Alerts

¢
Deliver

In-app banners fire as soon as a rule is satisfied. Email, Telegram, and Discord delivery are coming soon — every existing rule will keep working without changes.