Subscribe to GitHub Status - Incident History’s news feed.
Click on “Follow” and decide if you want to get news from GitHub Status - Incident History via RSS, as email newsletter, via mobile or on your personal news page.
Subscription to GitHub Status - Incident History comes without risk as you can unsubscribe instantly at any time.
You can also filter the feed to your needs via topics and keywords so that you only receive the news from GitHub Status - Incident History which you are really interested in. Click on the blue “Filter” button below to get started.
Website title: GitHub Status
Is this your feed? Claim it!
Jun 11, 22:19 UTC
Resolved - This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
Jun 11, 20:00 UTC
Monitoring - The degradation affecting Webhooks has been mitigated. We are monitoring to ensure st...
Jun 10, 16:39 UTC
Resolved - This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
Jun 10, 16:37 UTC
Monitoring - The degradation has been mitigated. We are monitoring to ensure stability.
J...
Jun 8, 15:00 UTC
Resolved - On June 8, 2026, between 14:49 and 14:54 UTC, a subset of requests to GitHub.com, the REST API, GraphQL API, and Webhooks UI/API experienced elevated error rates due to a transient infrastructure capacity issue that self-resolved within approximately 5 minutes.
Users experienced HTTP 500 errors and timeouts when access...
May 25, 09:02 UTC
Resolved - On May 25, 2026, between 09:02 UTC and 09:11 UTC, Git push operations over HTTPS and SSH experienced elevated failures. During this window, an average of 31% and a peak of 43% of push requests failed.
The incident was caused by a recently enabled code path that issued an unexpectedly expensive database query against a ...
Jun 8, 09:08 UTC
Update - We are experiencing degraded availability for the Claude Opus 4.7 model in Copilot products and IDE surfaces. This is due to an issue with an upstream model provider. While we work with them to resolve the issue, we recommend choosing another model or selecting 'Auto' to continue using Copilot.
Jun 8, 09:05 UTC