MarketsTech
GitHub Git Operations critical incident by...?
Polymarket prediction market· Same prices, rules and result
Polymarket prices · as of Polymarket 24h vol $11
December 31 51%November 30 51%
Each level is its own Yes or No; they don't add to 100%. Levels are in price order, as on Polymarket.
2 levels openin level order
OptionChance: Polymarket's displayed chance: the midpoint of the best bid and ask. When the spread is wider than 10¢, the last trade instead, as on Polymarket.Buy
November 30No smart money51%
December 31No smart money51%
2 open levels, in level order.
AI analysts
The AI analysts are reviewing this market. Usually within the hour.
News
Headlines link to the publisher. Kellian shows titles only.
Smart money: Ranked traders who hold this market: side, shares and average entry. From Polymarket's public data.
OptionYes holdersNo holdersYes · No
2 options: no ranked trader holds them
Best-ranked first. Tier 1 ranks 1–10, Tier 2 ranks 11–50.
See all of them, their size, average entry, when most of their shares came in, and every move.
Past performance is not indicative of future results.
Rules
Show rulesHide rules
- Resolution criteria
- This market will resolve to “Yes” if GitHub's Git Operations service experiences an incident with an impact classified as “critical” between market creation and the listed date, 11:59 PM ET. Otherwise, this market will resolve to “No.” 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” and lists Git Operations among the incident's affected components ones the incident is marked “Resolved”. GitHub classifies incident impact as None, Minor, Major, or Critical; only an impact of 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. If an incident that began before 11:59 PM ET on the listed date remains unresolved at that time, 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 listed date, at which point the market will resolve based on the official information available at that time. Incidents that do not list Git Operations among their affected components, including incidents that list no affected components, 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.