Analytics
“Will GitHub's longest critical incident in August 2026 be less than 1 hour?” is a prediction market on Polymarket with two tradeable outcomes, Yes and No. It belongs to the event “Longest GitHub critical incident in August?”. The Yes price is the crowd's implied probability that the question resolves Yes; every trade on the public order book moves it.
The venue reports this market as closed. Its scheduled close is Sep 1, 2026. No resolved outcome is inferred from a closed or suspended state.
Vultax observes this market from Polymarket's public order book and data API and keeps its own record: 12 hourly price points from Aug 21, 2026 to Sep 1, 2026 (Yes between 0.1% and 8.0%); 13 loaded holder wallets, the largest ten holding 99.0% of the loaded shares; 66 recent public fills from 22 wallets. Each figure carries its observation time; nothing here is a return forecast.
Public Polymarket market/event context is available; Vultax source-pack coverage is tracked separately.
This resolved market has no live orderbook depth; the public close quote is shown for context.
Nine stops, one per figure on this page. Each stop says what the number is, why it matters, and what it reads right now for this market.
Each outcome trades as a share that pays $1 if it wins and nothing if it loses. Prices are quoted in cents, and Yes plus No add up to about one dollar.
This market will resolve according to the duration of the longest qualifying incident that begins between August 1, 2026, 12:00 AM ET and August 31, 2026, 11:59 PM ET. If no qualifying incident begins during this period, this market will resolve to the lowest bracket (“<1 hour”). An incident will qualify if the official GitHub Status Page (githubstatus.com) or the official GitHub Status API (githubstatus.com/api) classifies the incident's impact as "critical," unless its affected components, once the incident is marked "Resolved," consist solely of Copilot and/or Copilot AI Model Providers. Incidents listing no affected components will qualify. GitHub classifies incident impact as None, Minor, Major, or Critical; only Critical will qualify. Component status labels (e.g. "Degraded Performance," "Partial Outage," or "Major Outage") will have no bearing on this market absent a qualifying critical incident. Revisions published after an incident is marked “Resolved” will not be considered. An incident's duration is the time between its official start timestamp and the time the incident is marked “Resolved,” as published by the GitHub Status Page or the GitHub Status API. An incident will be attributed to the month in which it begins, based on its official start timestamp converted to Eastern Time (ET); an incident that begins during the period and is resolved after the period ends will count in full. If the determined value falls exactly on the boundary between two brackets, this market will resolve to the higher bracket. If an incident that began during the period remains unresolved at the end of the period, this market will remain open and resolve at the earlier of: (i) when the incident is officially resolved, or (ii) the end of the seventh calendar day (ET) after the end of the period, at which point the market will resolve based on the official information available at that time, with any unresolved incident's duration measured from its official start timestamp to that time. Incidents whose affected components, once the incident is marked "Resolved," consist solely of Copilot and/or Copilot AI Model Providers will not qualify. Scheduled maintenance will not qualify. The primary resolution source for this market will be official GitHub system-status information published at https://www.githubstatus.com/, including the official GitHub Status API (https://www.githubstatus.com/api); however, a consensus of credible reporting may also be used.
Official listing: polymarket.com/event/will-githubs-longest-critical-incident-in-august-2026-be-less-than-1-hour
The Yes price read as a chance. A share at 21.5¢ means the crowd gives Yes about a 21.5% chance right now. It moves with every trade, so it is a live forecast, not a verdict.
Dollar value of shares that changed hands in the last 24 hours. High volume means the price is being tested by real money; low volume means a few trades can move it.
Dollars resting in the order book, waiting to be traded against. Deep liquidity lets a large order fill near the quoted price; thin liquidity means the price jumps when someone trades size.
The gap between the best bid and the best ask. A tight spread makes entry and exit cheap; a wide spread is a cost paid on every round trip.
The wallets holding the most shares on each side, and how much of the loaded sample the largest ten control. Concentration shows whether a market is a crowd or a handful of large positions.
The public fills, newest first: which wallet bought or sold which outcome, at what price, and when. It is the market's own diary, and every wallet on it links to a trader profile.
Hourly closes of the Yes price. The range shows how sure or split the crowd has been; the move shows which way it has been changing its mind.
Trading stops at the close time. The outcome is then settled by the resolution source named in the rules. A closed market is not resolved until the venue reports it, so the two states are shown separately.
| Trader | Outcome | Shares |
|---|---|---|
| Indigo Signal 2966 | No | 591.62 |
| ACara | Yes | 223.61 |
| Swift Meteor 30F2 | Yes | 125 |
| 74744886D1081ab236510E04c5b617b914A3Cef7. | Yes | 100 |
| pootytherewardfarmer | Yes | 55 |
| Mojito9 | Yes | 40.52 |
| flexer78 | Yes | 35.13 |
| Deafening-Possible | Yes | 14.7 |
| TENETENET | Yes | 10 |
| bjprolo | Yes | 5 |