Analytics
Resolved Yes on 25 Mar 2026.
The last daily price before settlement had Yes at 17.5%. Yes opened at 47.5% on 15 Jan 2026. Before it settled, across the 64 daily closes on record from 15 Jan 2026 to 25 Mar 2026 (6 days in that span have no close), the highest close was 50% on 20 Jan 2026 and the lowest 10% on 16 Mar 2026. Its largest one-day move was 27 points up, to 39.5% on 19 Mar 2026.
38 wallets still hold shares. Winners redeem theirs after settlement, so what is left is mostly the losing side.
Polymarket record as of Mar 26, 10:10 PM UTC
Daily closes of the Yes price, Polymarket CLOB, 64 points, 15 Jan 2026 – 25 Mar 2026
| Observed | Yes price |
|---|---|
| 15 Jan 2026 | 47.5% |
| 25 Mar 2026 | 17.5% |
Winners have redeemed their shares, so most of what is left is the losing side.
| Trader | Outcome | Shares |
|---|---|---|
| LukeGamma | No | 500 |
| FernandoCoimbra | No | 129.87 |
| hoppytrak | No | 90 |
Open a trader’s name to inspect the wallet’s available P&L, positions and recorded trades, with source dates and coverage. A large position alone does not establish a winning track record.
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.
Official listing: polymarket.com/event/critical-discord-incident-by
| No |
| 83 |
| asdssss | No | 56.81 |
| holy-mike | No | 27 |
| handsome-mike | No | 26 |
| shalushizhe | No | 23 |
| hululubear | No | 22 |
| VibeyQuant | No | 22 |
New to prediction markets? How to read a market page
