UnclassifiedExpires May 31, 2026
Creator

Critical Discord Incident by May 31?

Probability

19¢

1h

+0.0pp

24h

+0.0pp

24h Vol

$465.17

Liquidity

$2.6K

Resolution & Risk

LOW risk
End date
May 31, 2026
UMA status
n/a
Resolution source
Primary
consensus of credible reporting
Type
News consensus
Confidence
extracted · medium
Market type
Binary
  • No obvious resolution-risk signals in metadata.
Read full market rules on Polymarket

Probability (last 7 days)

+0.0pp 7d
Apr 27, 2026, 23:00May 1, 2026, 12:43
updated 0s ago·src:Polymarket CLOB

Why did it move?

Structured · 1 factor
  • 01
    Liquidity

    Thin liquidity

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

What to track next

  • Set an alert at the next ±5pp probability move so you find out before the next leg.
  • Add to your watchlist — Home will show probability deltas since your last visit.
  • Compare against sibling markets in the same event below — divergent pricing across related contracts is the cleanest tell.

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 707.3h

    LOW

Price movement

+0.0pp over the last 24h, now 19¢.

Biggest hourly move: -33.5pp at 09:00 (to 19¢).

Show top 8 of 14 hourly moves
  • 12:00 · -13.0pp → 19¢
  • 11:00 · -13.0pp → 19¢
  • 09:00 · -33.5pp → 19¢
  • 08:00 · -7.5pp → 19¢
  • 02:00 · +4.0pp → 19¢
  • 00:00 · +4.0pp → 19¢
  • 13:00 · +6.5pp → 19¢
  • 1d ago · -6.0pp → 19¢
updated 0s ago·src:Polymarket CLOB·Polymarket Data

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 Discord experiences any incident classified as Critical (red) by the listed date, 11:59 PM ET. Otherwise, this market will resolve to “No”. Qualifying incidents may include outages and other issues that Discord classifies as Critical. Revisions to the impact classification of any such incident will be considered as long as those revisions are published within this market’s timeframe. However, revisions of a previously published incident impact classification of Critical (red) to another classification will not disqualify an incident from counting. If an incident is ongoing at this market’s resolution time, the market may remain open until that incident receives an official impact classification, and it will resolve based on the first such classification published, regardless of subsequent revisions or corrections. The primary resolution source for this market will be official information from Discord (for example, on discordstatus.com or discordstatus.com/history); however, a consensus of credible reporting may also be used. Note: Discord impact classifications of Major (orange) and Critical (red) are not equivalent.

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.