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!
Jul 21, 11:04 UTC
Update - We are investigating reports of intermittent SSH authentication failures affecting connections that use deploy keys. Customers may experience failed SSH connections when interacting with repositories via deploy keys. Our engineering team is actively investigating the root cause and working toward resolution.
Jul 21, 10...
Jul 20, 18:37 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.
Jul 20, 18:25 UTC
Update - We are seeing signs of sustained recovery from the upstream provider for GPT 5.3 Codex re...
Jul 20, 01:46 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.
Jul 20, 01:45 UTC
Update - Git LFS API success rates have returned to normal. We will continue to monitor the servic...
Jul 20, 01:37 UTC
Update - Pages is operating normally.
Jul 20, 01:11 UTC
Update - We continue to work on mitigative efforts to restore Actions workflow runners, and have observed that the extended downtime has started to cause knock-on effects to other services.
A separate incident was opened before we understood the...
Jul 17, 00:14 UTC
Resolved - From 22:21 UTC - 23:50 UTC on July 16, 2026, the REST API experienced significant degradation. During this period, about 39% of REST API requests failed with HTTP 500 level responses, with the errors peaking at 44.3%.
We identified the issue as an infrastructure change that wrongly marked the majority of API backends ...