Another critical Cloudflare incident by September 30, 2026?
Price checked at
Probability history
Market-implied probabilities · All recorded historyDrag to move · pinch or ⌘/Ctrl+scroll to zoom
Shaded periods have no successful hourly price check.
Based on this market’s outcome prices, expressed as probabilities.
Resolution 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.
The same question elsewhere
2 venues carry it- Polymarketthis market
Another critical Cloudflare incident by September 30, 2026?
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.
71 holders · 0 comments · read Sep 23, 08:50 AM UTC
- PredictFunOpen →
Another critical Cloudflare incident by September 30, 2026?
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.
read Sep 29, 05:22 PM UTC
Other legs of this event
A leg read alone is misleading; the others are beside it.| Market | Venue | Price | Status |
|---|---|---|---|
| Another critical Cloudflare incident by October 31, 2026? | Polymarket | 71% No | Open |
| Another critical Cloudflare incident by August 31, 2026? | Polymarket | 100% No | Open |
Venue activity
Read from the venue 7 days agoBest bid 19% · best ask 20%
Top holders
- nope305040325645480876798584693908481813858556901201944365443348302504675413060526545
- theta-thunberg29561567971800258739937690207447739307438550216441108401236498566030764732276
- JAMJAMJAM429561567971800258739937690207447739307438550216441108401236498566030764732276
- mathrex40325645480876798584693908481813858556901201944365443348302504675413060526545
- CalculatedRisk0829561567971800258739937690207447739307438550216441108401236498566030764732276
A snapshot of positions, not a track record.
Recent trades
- BUY80%$20.17 days ago
- BUY22%$4.47 days ago
- BUY21%$4.27 days ago
- BUY20%$4.17 days ago
- BUY20%$107 days ago
- BUY20%$3.17 days ago
Discussion on Predxy
What Predxy's readers make of this market. Everyone can read; signed-in readers can write. The venue's own thread, when it has one, is the box below.Sign in to join the discussion.
Nobody has said anything here yet.
As of Sep 29, 10:24 PM UTC