GitHub Packages Outage History
GitHub Packages is up right nowGitHub Packages had 6 outages in the last 2 years totaling 9h 56m of downtime — averaging 0.2 incidents per month.
There were 6 GitHub Packages outages since March 13, 2026 totaling 9h 56m of downtime. Each is summarised below — incident details, duration, and resolution information.
Disruption with some GitHub services in the EU region
Timeline · 3 updates
- investigating Jun 06, 2026, 04:53 PM UTC
We are investigating reports of impacted performance for some GitHub services.
- investigating Jun 06, 2026, 04:56 PM UTC
Packages is experiencing degraded performance. We are continuing to investigate.
- resolved Jun 06, 2026, 05:07 PM UTC
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.
Incident with Issues and Webhooks
Timeline · 19 updates
GitHub search is degraded
Timeline · 15 updates
Investigating errors on GitHub
Timeline · 8 updates
- investigating Apr 23, 2026, 02:40 PM UTC
We are investigating reports of degraded performance for Actions
- investigating Apr 23, 2026, 02:41 PM UTC
Packages is experiencing degraded performance. We are continuing to investigate.
- investigating Apr 23, 2026, 02:42 PM UTC
Codespaces is experiencing degraded performance. We are continuing to investigate.
- investigating Apr 23, 2026, 02:44 PM UTC
Copilot is experiencing degraded performance. We are continuing to investigate.
- investigating Apr 23, 2026, 02:51 PM UTC
Users are experiencing errors loading various web pages on github.com. Actions and Copilot Cloud Agent runs will be delayed.
- investigating Apr 23, 2026, 03:02 PM UTC
A mitigation was applied and services have recovered. Actions is working through queued work before fully recovering.
- monitoring Apr 23, 2026, 03:02 PM UTC
The degradation affecting Actions, Codespaces, Copilot and Packages has been mitigated. We are monitoring to ensure stability.
- resolved Apr 23, 2026, 03:18 PM UTC
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.