Please turn JavaScript on

GitHub Status - Incident History

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!

Publisher:  Unclaimed!
Message frequency:  0.81 / day

Message History

Jun 4, 20:32 UTC
Resolved - Everything is operating normally.

Jun 4, 20:20 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.


Read full story

Jun 4, 18:03 UTC
Update - We have identified that Copilot Code Review.  Users may see "Copilot ran into an error" on Pull Requests that requested Copilot Code Review.

A mitigation is in progress.

Jun 4, 18:02 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.


Read full story

Jun 3, 21:10 UTC
Update - We are preparing a mitigation for the delayed Dependabot scheduled version updates.

Next update in 2 hours.

Jun 3, 20:18 UTC
Update - Customers may see delays of up to two days in Dependabot version updates.

Dependabot Security updates are not delayed.

The team is investigatin...


Read full story

Jun 3, 06: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.

Jun 3, 06:45 UTC
Monitoring - The degradation has been mitigated. We are monitoring to ensure stability.

J...


Read full story

Jun 1, 17:28 UTC
Update - We are continuing to investigate delayed billing updates, on GitHub.com.   We have applied multiple mitigations and are seeing some signs of improvement, and are continuing to work to improve the processing rate.  We will continue to keep users updated on progress towards mitigation.

GitHub Enterprise Clou...


Read full story