UnclassifiedExpires Aug 31, 2026
Creator

Another critical Cloudflare incident by July 31, 2026?

Probability

14¢

1h

+0.0pp

24h

+3.5pp

24h Vol

$2.0K

Liquidity

$356.14

Research loop

Inspect detail

Read the move, holders, recent trades, source, and resolution risk before saving anything.

Canonical status

confidence: medium

Source status (Polymarket)

active

Derived status (Orrery)

ILLIQUID

Reason

Liquidity is below $1,000 — price discovery is unreliable.

The derived status is computed from the source flags plus the live YES price, so a market trading near a rail can read as PRICE-PINNED while upstream is still active. That isn't the same as resolved.

Methodology explanation

Review-only opportunity

No paper intent is emitted from the public opportunity row. Paper action appears only after the paper governor evaluates the row.

read_only_explanationpaper-onlysend false

Why this market is in review

signal

Resolution-source risk

15% source confidence on this opportunity row.

Paper-only action

paper-only

Review-only opportunity

read_only_explanation; no live order, no network send, no raw secrets.

Risk / veto readback

review

Resolution review required

The public opportunity row has not passed the paper governor; source wording and settlement state remain review blockers.

Source evidence

source

4 mapped surfaces

283/283 sources runtime-backed; all registered sources are runtime-backed; live authority remains false.

Signals

  • Resolution-source riskwatch

    15% source confidence on this opportunity row.

Veto / blockers

  • Resolution review requiredwatch

    The public opportunity row has not passed the paper governor; source wording and settlement state remain review blockers.

  • Confidence below paper gatewatch

    Paper policy needs at least 72% confidence before any paper intent can be proposed.

Costs / sizing

Research score
Composite opportunity score before paper-governor costs and vetoes.
3
Capacity
Estimated research capacity, not an approved size.
$500
Liquidity
Market liquidity visible on the opportunity row.
$356
Explanation packet2026-06-16.1
DecisionSignalsVetoes and capsCostsDriftShadow policyLearning statusAuthority
What can be learned
Source-to-runtime coverage283/283 runtime-backed0 unmapped

all registered sources are runtime-backed; live authority remains false; this card cites mapped surfaces only.

P32-Source-to-Runtime-Coverage-Matrix-v1semantic_risk_kernelmethodology_runtime_boundarypromotion_gate+3
live falsesecrets falsetraining falsenot advice

Resolution & Risk

LOW risk
End date
Aug 31, 2026
UMA status
n/a
Resolution source
Primary
consensus of credible reporting
Type
News consensus
Confidence
extracted · medium
Market type
Binary
  • Wide spread (9.0¢) — liquidity risk on entry/exit.

Probability (last 7 days)

-4.5pp 7d
1007550250
14¢
Jul 22, 2026, 05:00 UTCJul 29, 2026, 04:02 UTC
updated 04:04:00 UTC·src:Polymarket CLOB·snap:snap_2026-07-29T04-04Z

Why did it move?

Structured · 3 factors
  • 01
    Price move

    Up 4pp over 24h

    Now 14¢; flat in the last hour.

  • 02
    Active signal

    Resolution-risk observation firing

    Spread is wide enough that intraday moves overstate any tradeable edge.

  • 03
    Spread cost

    Wide spread — 9.0¢

    Bid-ask spread is wide enough that intraday moves overstate any tradeable advantage. Most of the headline pp move would be eaten by spread on a market order.

What to track next

  • Verify the resolution source on this page — exchange feed, official release, news consensus — before treating any move as new information.

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.

Verification Brief

A guided checklist for what must be proven before this market is treated as reliable context.

liquidity sensitive
Trust transition

Liquidity is thin enough that movement can be noisy. Verify source context before reading the move as information.

Create trust-state alert

Verification goal

Map resolution-relevant sources to the exact criteria needed to avoid misreading price as settlement.

What needs proof

Primary source

required

Confirm the primary news consensus source and whether it directly answers the market's resolution question.

Current evidence: consensus of credible reporting

Contract wording

required

Extract the exact condition that makes YES resolve true and note any exclusions, time zone, deadline, or fallback rule.

Telegram verification task

Orrery verification task Another critical Cloudflare incident by July 31, 2026? State: Illiquid — liquidity sensitive Need sources for: 1. Primary source: Confirm the primary news consensus source and whether it directly answers the market's resolution question. 2. Contract wording: Extract the exact condition that makes YES resolve true and note any exclusions, time zone, deadline, or fallback rule. 3. Liquidity context: Check whether the move is supported by enough liquidity and volume to treat it as meaningful context. Drop only durable links that map to one criterion. Research only. Not trade advice.

X verification thread

Orrery verification brief Another critical Cloudflare incident by July 31, 2026? State: liquidity sensitive Verify: Primary source + Contract wording Price is not settlement. Research only. Not trade advice.

Market link goes in reply

Guided source review

A controlled loop for durable sources. Every source must answer one criterion from this Verification Brief.

Sources

0

Criteria covered

0

Reviewed

0

Awaiting review

0

Submit a source mapped to a criterion

Confirm the primary news consensus source and whether it directly answers the market's resolution question.

Research only · no price-only screenshots · no profit claims

Recent source checks

Pilot audit summary

Research only · Not trade advice · Every source maps to one criterion

Timeline

critical · price · trade flow

Critical

  • Aug 31, 00:00 UTCScheduled resolution

    Market resolves in 787.9h

    LOW
  • 04:04Signal

    Resolution risk

    Spread is wide enough that intraday moves overstate any tradeable edge.

    LOW

Price movement

+3.5pp over the last 24h, now 14¢.

Biggest hourly move: +49.0pp at 18:00 (to 65¢).

Show top 8 of 39 hourly moves
  • 19:00 · +9.5pp → 25¢
  • 18:00 · +49.0pp → 65¢
  • Jul 28, 04:00 UTC · -5.5pp → 11¢
  • Jul 28, 03:00 UTC · -5.5pp → 11¢
  • Jul 28, 02:00 UTC · -5.5pp → 11¢
  • Jul 28, 00:00 UTC · -5.5pp → 11¢
  • Jul 27, 23:00 UTC · -5.5pp → 11¢
  • Jul 24, 18:00 UTC · -9.0pp → 14¢
updated 04:04:00 UTC·src:Polymarket CLOB·Polymarket Data

Active signals

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.

updated 04:04:00 UTC·src:Polymarket Data

Market 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: low

Category

Other

Source

Default fallback

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 July 31, 2026?"?

As of Wed, 29 Jul 2026 04:04:00 GMT, YES is priced at 14% implied probability on Polymarket. The price changed +3.5pp in the last 24 hours, +0.0pp in the last hour, and -4.5pp in the last 7 days.

When does this market resolve?

This market resolves by Aug 31, 2026 (2026-08-31T00: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?

$2.0K of trading volume in the last 24 hours. Lifetime volume on Polymarket: $8.0K. Open liquidity in the YES/NO orderbooks: $356.14. Spread between best bid and best ask: 9.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

¢
Deliver

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.