Critical Discord Incident by April 30?

1. 1

   Up 1pp over 24h

   Now 11¢; +1.5pp in the last hour.

2. 2

   Resolution-risk signal firing

   Expires in 106h with open resolution ambiguity.

3. 3

   Thin liquidity

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

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.

Prose narration of the same metrics shown in the structured breakdown above. Cites only the market data on this page — no news, no predictions. Use the structured factors as the canonical answer; this is here for readability.

No recent trades visible from the Data API for this market.

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.