Will there be fewer than 2 ChatGPT outages in June 2026?
Probability
1¢
1h
-0.2pp
24h
+0.4pp
24h Vol
$155.00
Liquidity
$4.7K
Canonical status
confidence: highSource status (Polymarket)
Derived status (Orrery)
Reason
YES price is near 0¢ but the market has not been officially resolved.
Treat as effectively priced-out, not settled. The market is still live until expiry.
Resolution & Risk
LOW risk- End date
- Jun 30, 2026
- UMA status
- n/a
- Resolution source
- Primaryconsensus of credible reportingTypeNews consensusConfidenceextracted · medium
- Market type
- Multi-outcome (neg-risk)
- Part of a multi-outcome event (neg-risk): only one market can resolve YES.
Probability (last 7 days)
-32.4pp 7dWhy did it move?
Structured · 1 factor- 01Liquidity
Thin liquidity
Only $4.7k 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
- Jun 30, 2026
- UMA status
- n/a
- Resolution source
- Primaryconsensus of credible reportingTypeNews consensusConfidenceextracted · medium
- Market type
- Multi-outcome (neg-risk)
- Part of a multi-outcome event (neg-risk): only one market can resolve YES.
Verification Brief
A guided checklist for what must be proven before this market is treated as reliable context.
The price is pinned near a rail, but price is not settlement. Verify the official status before treating it as final.
Create trust-state alertVerification goal
Map resolution-relevant sources to the exact criteria needed to avoid misreading price as settlement.
What needs proof
Primary source
requiredConfirm the primary news consensus source and whether it directly answers the market's resolution question.
Current evidence: consensus of credible reporting
Contract wording
requiredExtract the exact condition that makes YES resolve true and note any exclusions, time zone, deadline, or fallback rule.
Price is not settlement
requiredVerify whether the market is officially resolved or merely pinned near 0¢/100¢.
Current evidence: 1¢ current price
Orrery verification task Will there be fewer than 2 ChatGPT outages in June 2026? State: Pinned near NO — price pinned not settled 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. Price is not settlement: Verify whether the market is officially resolved or merely pinned near 0¢/100¢. Drop only durable links that map to one criterion. Research only. Not trade advice.
Orrery verification brief Will there be fewer than 2 ChatGPT outages in June 2026? State: price pinned not settled Verify: Primary source + Contract wording Price is not settlement. Research only. Not trade advice.
Market link goes in reply
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
Recent source checks
Pilot audit summary
Research only · Not trade advice · Every source maps to one criterion
Timeline
critical · price · trade flowCritical
- Jun 30, 00:00 UTCScheduled resolutionLOW
Market resolves in 580.8h
Price movement
+0.4pp over the last 24h, now 1¢.
Biggest hourly move: -26.6pp at Jun 4, 03:00 UTC (to 0¢).
Show top 8 of 62 hourly moves
- Jun 4, 11:00 UTC · -26.2pp → 1¢
- Jun 4, 10:00 UTC · -26.5pp → 1¢
- Jun 4, 09:00 UTC · -25.9pp → 1¢
- Jun 4, 03:00 UTC · -26.6pp → 0¢
- Jun 4, 01:00 UTC · -26.1pp → 0¢
- Jun 4, 00:00 UTC · -26.1pp → 0¢
- Jun 3, 21:00 UTC · -26.1pp → 0¢
- Jun 3, 20:00 UTC · -26.1pp → 0¢
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
3Market Description
This market will resolve to the number of calendar days on which OpenAI's ChatGPT experiences any incident classified as 'Partial/Full Outage' as of the time it is marked as “Resolved” during the specified month (ET). Only incidents listing ChatGPT under 'Affected components' will be considered. Incidents labeled as affecting 'APIs,' or 'Sora,' but not ChatGPT, will have no bearing on the resolution of this market. 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 'Partial/Full Outage' when they are resolved, during this market's above-specified timeframe. Revisions that upgrade an incident’s impact classification to 'Partial/Full Outage' will qualify if the incident was resolved and the revision is published within this market’s timeframe. This market will resolve at 12:00 PM ET on the day following the specified timeframe, provided no incident that began during the specified timeframe is ongoing, and all relevant data has been released. If either condition is not met, the market will remain open until the incident is marked as “Resolved” and all relevant data has been released. If all relevant data has not been released by the end of the seventh day after the specified timeframe, this market will resolve based on the data available at that time. The primary resolution source for this market will be official system status information published by OpenAI on status.openai.com; however, a consensus of credible reporting may also be used.
Why this category?
confidence: mediumCategory
Source
Matched term
chatgptReason
Question text contains "chatgpt" — matched the AI keyword rule.
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 "Will there be fewer than 2 ChatGPT outages in June 2026?"?
As of Fri, 05 Jun 2026 19:11:41 GMT, YES is priced at 1% implied probability on Polymarket. The price changed +0.4pp in the last 24 hours, -0.2pp in the last hour, and -32.4pp in the last 7 days.
When does this market resolve?
This market resolves by Jun 30, 2026 (2026-06-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?
$155.00 of trading volume in the last 24 hours. Lifetime volume on Polymarket: $4.7K. Open liquidity in the YES/NO orderbooks: $4.7K. Spread between best bid and best ask: 1.5¢.
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.