Description
Cloudflare incidents marked as Critical (red) will settle Yes if a Critical incident is officially resolved by the specified date. The timeframe runs through February 28, March 31, April 30, May 31, and June 30, 2026. Resolution relies on official Cloudflare status pages or credible reporting consensus if needed. Incidents still ongoing or upgraded after resolution time do not affect the Yes outcome unless they are resolved within the market window, and revisions count only if published within the window.
Event stats
Market highlights
Related events
Markets
Outcome | Odds | Spread | 24h Change | 24h Volume | Total Volume | Liquidity | |
|---|---|---|---|---|---|---|---|
| February 28 | No | — | — | — | — | — | |
| March 31 | No | — | — | — | — | — | |
| April 30 | Yes | — | — | — | — | — | |
| May 31 | Yes | — | — | — | — | — | |
| June 30 | Yes | — | — | — | — | — |
Rules
This market will resolve to “Yes” if Cloudflare experiences any incident classified as Critical (red) as of the time it is marked as “Resolved” by the listed date (ET). Otherwise, this market will resolve to “No”. Classifications of an incident while it is ongoing will have no bearing on the resolution of this market. Only classifications of events that are resolved will be considered. Qualifying incidents include outages and other issues classified as critical when they are resolved, during this market's above specified timeframe. An incident resolved outside this market’s timeframe will only qualify if ongoing at this market’s resolution time, in which case the market will remain open until that incident is marked as “Resolved,” and resolution will be based on the first impact classification thereafter, regardless of subsequent revisions or corrections. Revisions that upgrade an incident’s impact classification to Critical will qualify if the incident was resolved and the revision is published within this market’s timeframe. The primary resolution source for this market will be official information from Cloudflare (for example, on cloudflarestatus.com or cloudflarestatus.com/history); however, a consensus of credible reporting may also be used.