- GitHub.com critical incident by August 31, 2026?>99¢
- GitHub.com critical incident by September 15, 2026?>99¢
- GitHub.com critical incident by September 30, 2026?>99¢
This market will resolve to “Yes” if GitHub.com 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," 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. 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 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.
Recent major outages on GitHub.com, including a 7-hour-47-minute disruption on August 17 affecting Actions, APIs, pull requests, authentication, and Copilot, alongside incidents on August 6 and 26, have heightened trader focus on platform reliability. GitHub's CTO attributed these to scaling failures under peak traffic loads, exacerbated by AI-driven usage spikes and issues like misconfigured autoscaling policies and retry storms in tools such as VS Code. The company has accelerated infrastructure overhauls, including monorepo optimizations and Istio adjustments, while publishing post-mortems. Traders are watching the next availability report and GitHub Universe 2026 for signs of sustained improvements amid ongoing high commit volumes.