Another critical Cloudflare incident by September 30, 2026?
Probability
78¢
1h
+0.0pp
24h
+0.0pp
24h Vol
$83.26
Liquidity
$10.3K
Canonical status
confidence: highSource status (Polymarket)
Derived status (Orrery)
Reason
Active market, expiry beyond the near-expiry window.
Resolution & Risk
LOW risk- End date
- Sep 30, 2026
- UMA status
- n/a
- Resolution source
- Primaryconsensus of credible reportingTypeNews consensusConfidenceextracted · medium
- Market type
- Binary
- No obvious resolution-risk signals in metadata.
Probability (last 7 days)
+0.0pp 7dWhy did it move?
Structured · 1 factor- 01Liquidity
Thin liquidity
Only $10.3k 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.
Resolution & Risk
LOW risk- End date
- Sep 30, 2026
- UMA status
- n/a
- Resolution source
- Primaryconsensus of credible reportingTypeNews consensusConfidenceextracted · medium
- Market type
- Binary
- No obvious resolution-risk signals in metadata.
Timeline
critical · price · trade flowCritical
- Sep 30, 00:00 UTCScheduled resolutionLOW
Market resolves in 3230.2h
Price movement
+0.0pp over the last 24h, now 78¢.
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.
Related Markets
2Market Description
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.
Why this category?
confidence: lowCategory
Source
Reason
No override, sports marker, rule, or upstream hint matched. Market is unclassified — the keyword rules need an entry for this topic.
Categories come from a deterministic engine: manual overrides (highest priority) → sports hard markers → event-tag rules → keyword rules → Gamma category hint → default. The engine is versioned in category-overrides.ts; methodology lives at /methodology.
FAQ — questions readers actually ask
What is the current Polymarket probability for "Another critical Cloudflare incident by September 30, 2026?"?
As of Mon, 18 May 2026 09:47:44 GMT, YES is priced at 78% implied probability on Polymarket. The price changed +0.0pp in the last 24 hours, +0.0pp in the last hour, and +0.0pp in the last 7 days.
When does this market resolve?
This market resolves by Sep 30, 2026 (2026-09-30T00:00:00.000Z). Resolution is determined from the market description on Polymarket.
What source determines the outcome?
Resolution is sourced from the market description on Polymarket. Polymarket's UMA optimistic oracle is the final settlement layer; if the published source is ambiguous, UMA tokenholders adjudicate. Source-extraction confidence is shown in the Resolution & Risk block above.
How much is being traded on this market?
$83.26 of trading volume in the last 24 hours. Lifetime volume on Polymarket: $3.8K. Open liquidity in the YES/NO orderbooks: $10.3K. Spread between best bid and best ask: 1.0¢.
Is this a trade recommendation?
No. Orrery describes — never predicts. Every signal on this market carries explicit Evidence, Backtest, and Action tiers. The Action is always one of: Watch only, Inspect timeline, Create alert, Verify source, or Ignore — never Buy or Sell. The probability above is the market's collective implied probability, not a forecast Orrery is publishing.
How fresh is this data and where does it come from?
This page revalidates from the public Polymarket APIs every 30 seconds. Probability and 24h-change come from Gamma; the chart series comes from the CLOB orderbook history; trade and holder data come from the Data API. The fetched-at timestamp on each block tells you exactly how old the underlying upstream pull was.
Alerts
In-app banners fire as soon as a rule is satisfied. Email digests are wired to a server-side cron and continue while your tabs are closed. Telegram and Discord are planned — every existing rule will keep working as channels light up.