All systems operational

Between 08:37 and 09:41 UTC on August 31, 2026, GitHub Copilot experienced degradation affecting several GPT models, including gpt-5.2, gpt-5.3-codex, gpt-5.4, gpt-5.4-mini, gpt-5.4-nano, and the gpt-5.6 family (Luna, Sol, and Terra). Users encountered elevated error rates and interrupted streaming responses. Other models were not affected. The degradation was caused by an issue with an upstream model provider. GitHub engineers detected the issue through automated monitoring, displayed in-product warnings for the affected models, and coordinated with the provider. Service returned to normal after the provider implemented a mitigation.

Started 31 авг. 2026 г., 09:15 UTC · Resolved 31 авг. 2026 г., 09:58 UTC

On August 27th, 2026, between approximately 09:20 and 12:14 UTC, the Copilot service experienced a degradation of the Kimi K3 model due to an issue with our upstream provider. Users encountered elevated error rates when using Kimi K3. No other models were impacted. The issue was resolved by a mitigation put in place by our provider. GitHub is working with our provider to further improve the resiliency of the service to prevent similar incidents in the future.

Started 27 авг. 2026 г., 10:04 UTC · Resolved 27 авг. 2026 г., 12:12 UTC

On August 26, 2026, from 21:55 UTC to 23:58 UTC, 2.6% of workflow runs triggered by pull request events were delayed, with the impact rising as high as 25% at its peak. Some users also experienced delays in pull request merge-commit generation, mergeability information, and merge-button availability. Actions and Pull Requests fully recovered by 23:58 UTC; the incident was resolved at 00:26 UTC after normal operation was confirmed. Background jobs that process pull request updates and generate merge commits were impacted by timeouts reaching a single partition of git data. This resulted in a backlog in pull request merge-commit processing, delaying pull request-triggered GitHub Actions workflows and some mergeability information. We reduced workload, shifted traffic away from affected infrastructure, and restored the affected service component to a healthy state. Together, these actions helped drain the backlog and restore normal operations. We are working to improve resource saturation detection and to eliminate customer impact in this scenario by isolating impact, placing better bounds on retries, and strengthening backpressure to make our systems more resilient under load.

Started 26 авг. 2026 г., 22:56 UTC · Resolved 27 авг. 2026 г., 00:26 UTC

On August 26, 2026, between 20:40 UTC and 00:51 UTC on August 27, GitHub Billing experienced degraded performance affecting billing budget pages and GitHub Copilot CLI sessions. Affected customers encountered failed budget page loads or failures when starting or continuing CLI sessions. We confirmed this impact for a small number of customers (<1%). This was caused by a concentrated workload that created processing delays in our data storage layer. Automated retries increased the load and prolonged the degradation. We mitigated the incident by rebalancing traffic within our infrastructure. We are improving workload isolation, retry behavior, and detection of concentrated load to reduce the likelihood of recurrence and shorten our time to detect and mitigate similar incidents.

Started 26 авг. 2026 г., 20:40 UTC · Resolved 27 авг. 2026 г., 00:51 UTC

The scheduled maintenance has been completed.

Started 21 апр. 2025 г., 16:30 UTC · Resolved 22 апр. 2025 г., 16:30 UTC

The scheduled maintenance has been completed.

Started 2 апр. 2025 г., 17:00 UTC · Resolved 3 апр. 2025 г., 17:00 UTC

The scheduled maintenance has been completed.

Started 18 мар. 2025 г., 21:00 UTC · Resolved 19 мар. 2025 г., 05:00 UTC

The scheduled maintenance has been completed.

Started 28 февр. 2025 г., 17:00 UTC · Resolved 1 мар. 2025 г., 02:00 UTC