Part of GitHub

GitHub Packages Outage History

GitHub Packages is up right now

Pingoru has recorded 7 incidents for GitHub Packages: 7 in the last 12 months and 2 in the last 90 days.

Source: githubstatus.com

7incidents recorded
7last 12 months
2last 90 days
3 hourstypical duration
Incidents per month
012AprMayJunJulAugSepOct1
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct1%
Pingoru began tracking GitHub Packages in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202627 of 720 (1%)
May 202611 of 744 (0%)
June 202610 of 720 (0%)
July 202600 of 744 (0%)
August 202611 of 744 (0%)
September 202600 of 720 (0%)
October 2026111 of 737 (1%)

Incidents, newest first

Minor October 22, 2026 Project updates delayed 11h 2m API Requests, Issues, Pull Requests, Actions and 1 more

Started Oct 22, 2026, 03:28 PM UTC· resolved Oct 23, 2026, 02:30 AM UTC

  1. investigating Oct 22, 2026, 03:28 PM UTC

    We are investigating reports of degraded performance for Actions, Issues and Pull Requests

  2. investigating Oct 22, 2026, 03:33 PM UTC

    Some users may experience intermittent errors loading Issues, Pull Requests and search results on github.com. We're investigating and working to restore normal service.

  3. investigating Oct 22, 2026, 04:08 PM UTC

    Some users continue to experience intermittent errors loading Issues, Pull Requests and search results on github.com. We're investigating and evaluating mitigation options to restore normal service.

  4. investigating Oct 22, 2026, 04:26 PM UTC

    API Requests is experiencing degraded performance. We are continuing to investigate.

  5. investigating Oct 22, 2026, 04:28 PM UTC

    Packages is experiencing degraded performance. We are continuing to investigate.

  6. investigating Oct 22, 2026, 04:35 PM UTC

    API Requests is operating normally.

  7. investigating Oct 22, 2026, 04:41 PM UTC

    Some users continue to experience errors loading Issues, Pull Requests, package listings and search results on github.com. We're working through multiple mitigation efforts and continuing to investigate.

  8. investigating Oct 22, 2026, 05:16 PM UTC

    We're seeing recovery after adding capacity, with errors decreasing. Some users may still experience errors loading Issues, Pull Requests and search results on github.com. We're continuing to work towards full recovery and monitoring for stability.

  9. investigating Oct 22, 2026, 05:41 PM UTC

    Actions, Issues, Packages and Pull Requests are operating normally.

  10. investigating Oct 22, 2026, 05:43 PM UTC

    We're seeing recovery across the affected services. GitHub Projects is still recovering as queued updates are processed, and we're continuing to monitor for stability.

  11. investigating Oct 22, 2026, 06:26 PM UTC

    The other affected services have recovered. We're continuing to investigate GitHub Projects and verify that normal operation has been restored.

  12. investigating Oct 22, 2026, 07:04 PM UTC

    Some updates in GitHub Projects are still delayed. We're continuing mitigation work and monitoring.

  13. investigating Oct 22, 2026, 07:56 PM UTC

    Some GitHub Projects updates related to issue changes and merged pull requests are still delayed. We're investigating the remaining delays and working to restore normal processing.

  14. investigating Oct 22, 2026, 08:46 PM UTC

    Some GitHub Projects updates, including newly added items and changes to issues and pull requests, remain delayed. We've identified interruptions in update processing and are evaluating mitigations to restore normal operation.

  15. investigating Oct 22, 2026, 10:07 PM UTC

    Some GitHub Projects updates, including newly added items and changes to issues and pull requests, are still delayed. We have seen some recovery, and are working to add more capacity to accelerate the recovery.

  16. investigating Oct 22, 2026, 11:48 PM UTC

    GitHub Projects update processing has improved, but newly added items may still take longer than expected to appear. We're continuing to work on the remaining delays and monitor recovery.

  17. monitoring Oct 23, 2026, 12:55 AM UTC

    The degradation has been mitigated. We are monitoring to ensure stability.

  18. resolved Oct 23, 2026, 02:30 AM 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.

Read the full incident report →

Minor August 13, 2026 Incident with Webhooks 50m Git Operations, Webhooks, Issues, Pull Requests and 1 more

Started Aug 13, 2026, 02:45 PM UTC· resolved Aug 13, 2026, 03:36 PM UTC

  1. investigating Aug 13, 2026, 02:45 PM UTC

    We are investigating reports of degraded performance for Webhooks

  2. investigating Aug 13, 2026, 02:46 PM UTC

    Pull Requests is experiencing degraded performance. We are continuing to investigate.

  3. investigating Aug 13, 2026, 02:46 PM UTC

    Issues is experiencing degraded performance. We are continuing to investigate.

  4. investigating Aug 13, 2026, 02:46 PM UTC

    Git Operations is experiencing degraded performance. We are continuing to investigate.

  5. investigating Aug 13, 2026, 02:56 PM UTC

    Packages is experiencing degraded performance. We are continuing to investigate.

  6. investigating Aug 13, 2026, 02:58 PM UTC

    We are currently investigating a brief degradation of service for Git operations (specifically pushes), issues, pull requests, package registry, and webhooks between 14:32 and 14:46 UTC. We have identified the source of the degradation and are investigating mitigation strategies to prevent recurrence.

  7. monitoring Aug 13, 2026, 03:33 PM UTC

    The degradation affecting Git Operations, Issues, Packages, Pull Requests and Webhooks has been mitigated. We are monitoring to ensure stability.

  8. monitoring Aug 13, 2026, 03:33 PM UTC

    We have temporarily disabled a background job which caused the impact. At this time the impact is fully mitigated.

  9. resolved Aug 13, 2026, 03:36 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.

Read the full incident report →

Minor June 6, 2026 Disruption with some GitHub services in the EU region 14m Packages

Started Jun 06, 2026, 04:53 PM UTC· resolved Jun 06, 2026, 05:07 PM UTC

  1. investigating Jun 06, 2026, 04:53 PM UTC

    We are investigating reports of impacted performance for some GitHub services.

  2. investigating Jun 06, 2026, 04:56 PM UTC

    Packages is experiencing degraded performance. We are continuing to investigate.

  3. 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.

Read the full incident report →

Critical May 4, 2026 Incident with Issues and Webhooks 54m Git Operations, Webhooks, Issues, Pull Requests and 4 more

Started May 04, 2026, 03:45 PM UTC· resolved May 04, 2026, 04:40 PM UTC

  1. investigating May 04, 2026, 03:45 PM UTC

    We are investigating reports of degraded performance for Issues and Webhooks

  2. investigating May 04, 2026, 03:48 PM UTC

    We are investigating Increased latency and timeouts across multiple GitHub services.

  3. investigating May 04, 2026, 03:48 PM UTC

    Git Operations is experiencing degraded performance. We are continuing to investigate.

  4. investigating May 04, 2026, 03:50 PM UTC

    Packages is experiencing degraded performance. We are continuing to investigate.

  5. investigating May 04, 2026, 03:51 PM UTC

    Pull Requests is experiencing degraded availability. We are continuing to investigate.

  6. investigating May 04, 2026, 03:51 PM UTC

    Actions is experiencing degraded performance. We are continuing to investigate.

  7. investigating May 04, 2026, 03:56 PM UTC

    Pull Requests is experiencing degraded performance. We are continuing to investigate.

  8. investigating May 04, 2026, 04:05 PM UTC

    Codespaces is experiencing degraded performance. We are continuing to investigate.

  9. investigating May 04, 2026, 04:06 PM UTC

    Pages is experiencing degraded performance. We are continuing to investigate.

  10. investigating May 04, 2026, 04:25 PM UTC

    Git Operations is operating normally.

  11. investigating May 04, 2026, 04:28 PM UTC

    Actions and Packages are operating normally.

  12. investigating May 04, 2026, 04:29 PM UTC

    Latency across services has normalized. We are continuing to investigate the root cause and prevent reoccurrence.

  13. investigating May 04, 2026, 04:29 PM UTC

    Pages is operating normally.

  14. investigating May 04, 2026, 04:32 PM UTC

    Pull Requests is operating normally.

  15. investigating May 04, 2026, 04:34 PM UTC

    The degradation affecting Issues has been mitigated. We are monitoring to ensure stability.

  16. investigating May 04, 2026, 04:35 PM UTC

    The degradation affecting Codespaces has been mitigated. We are monitoring to ensure stability.

  17. investigating May 04, 2026, 04:35 PM UTC

    Webhooks is operating normally.

  18. monitoring May 04, 2026, 04:36 PM UTC

    The degradation has been mitigated. We are monitoring to ensure stability.

  19. resolved May 04, 2026, 04:40 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.

Read the full incident report →

Critical April 27, 2026 GitHub search is degraded 6h 15m Issues, Pull Requests, Actions, Packages

Started Apr 27, 2026, 04:31 PM UTC· resolved Apr 27, 2026, 10:46 PM UTC

  1. investigating Apr 27, 2026, 04:31 PM UTC

    We are investigating reports of degraded performance for Actions

  2. investigating Apr 27, 2026, 04:33 PM UTC

    Customers across GitHub are experiencing failures with searches. Examples include: workflow run failures, projects failing to load, and timed out search requests. This is due to an ongoing infrastructure issue that we have been investigating.

  3. investigating Apr 27, 2026, 04:36 PM UTC

    Issues is experiencing degraded performance. We are continuing to investigate.

  4. investigating Apr 27, 2026, 04:39 PM UTC

    Packages is experiencing degraded performance. We are continuing to investigate.

  5. investigating Apr 27, 2026, 04:53 PM UTC

    Pull Requests is experiencing degraded performance. We are continuing to investigate.

  6. investigating Apr 27, 2026, 05:35 PM UTC

    Users are experiencing intermittent failures to view issues, pull requests, projects and Actions workflow runs. We are still investigating and attempting mitigations. We will provide further updates.

  7. investigating Apr 27, 2026, 06:17 PM UTC

    We're continuing to see connectivity issues reaching elasticsearch. Impact on downstream services will be intermittent as we find the root cause

  8. investigating Apr 27, 2026, 06:19 PM UTC

    Pull Requests is experiencing degraded availability. We are continuing to investigate.

  9. investigating Apr 27, 2026, 07:50 PM UTC

    We have identified the source of the additional load causing stress on our ElasticSearch clusters. We have disabled the source of that load and are seeing signs of recovery

  10. investigating Apr 27, 2026, 08:06 PM UTC

    Pull Requests is experiencing degraded performance. We are continuing to investigate.

  11. investigating Apr 27, 2026, 09:32 PM UTC

    We've applied a mitigation and continuing to monitor

  12. monitoring Apr 27, 2026, 09:33 PM UTC

    The degradation affecting Actions, Issues, Packages and Pull Requests has been mitigated. We are monitoring to ensure stability.

  13. monitoring Apr 27, 2026, 10:35 PM UTC

    The degradation has been mitigated. We are monitoring to ensure stability.

  14. monitoring Apr 27, 2026, 10:44 PM UTC

    The degradation has been mitigated. We are monitoring to ensure stability.

  15. resolved Apr 27, 2026, 10:46 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.

Read the full incident report →

Minor April 23, 2026 Investigating errors on GitHub 38m Actions, Packages, Codespaces, Copilot

Started Apr 23, 2026, 02:40 PM UTC· resolved Apr 23, 2026, 03:18 PM UTC

  1. investigating Apr 23, 2026, 02:40 PM UTC

    We are investigating reports of degraded performance for Actions

  2. investigating Apr 23, 2026, 02:41 PM UTC

    Packages is experiencing degraded performance. We are continuing to investigate.

  3. investigating Apr 23, 2026, 02:42 PM UTC

    Codespaces is experiencing degraded performance. We are continuing to investigate.

  4. investigating Apr 23, 2026, 02:44 PM UTC

    Copilot is experiencing degraded performance. We are continuing to investigate.

  5. 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.

  6. 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.

  7. 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.

  8. 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.

Read the full incident report →

Minor March 13, 2026 Degraded performance for various services 1h 2m Issues, Actions, Packages

Started Mar 13, 2026, 03:12 PM UTC· resolved Mar 13, 2026, 04:15 PM UTC

  1. investigating Mar 13, 2026, 03:12 PM UTC

    We are investigating reports of degraded performance for Actions and Issues

  2. investigating Mar 13, 2026, 03:14 PM UTC

    We are investigating reports of issues with service(s): Actions, Feeds, Issues, Profiles, Registry Metadata, Star, User Dashboard. We will continue to keep users updated on progress towards mitigation.

  3. investigating Mar 13, 2026, 03:20 PM UTC

    Packages is experiencing degraded performance. We are continuing to investigate.

  4. investigating Mar 13, 2026, 03:47 PM UTC

    We are investigating intermittent performance degradation affecting Actions, Feeds, Issues, Package Registry, Profiles, Registry Metadata, Star, and User Dashboard. Users may experience elevated error rates and slower response times when accessing these services. We have identified a potential cause and are implementing mitigations to restore normal service. We'll post another update by 16:15 UTC.

  5. investigating Mar 13, 2026, 04:02 PM UTC

    We have deployed mitigations and are actively monitoring for recovery. We'll post another update by 17:00 UTC.

  6. resolved Mar 13, 2026, 04:15 PM UTC

    On March 13, 2026, between 13:35 UTC and 16:02 UTC, a configuration change to an internal authorization service reduced its processing capacity below what was needed during peak traffic. This caused intermittent timeouts when other GitHub services checked user permissions, resulting in four to five waves of errors over roughly two hours and forty minutes. In total, 0.4% of users were denied access to actions they were authorized to perform. The root cause was a resource right-sizing change deployed to the authorization service the previous day. It reduced CPU allocation below what was required at peak, causing the service's network gateway to throttle under load. Because the change was deployed after peak traffic on March 12, the reduced capacity wasn't surfaced until the next day's peak. The incident was mitigated by manually scaling up the authorization service and reverting the configuration change. To prevent recurrence, we are adding further resource utilization monitors across our entire stack to detect throttling and improving error handling so transient infrastructure timeouts are distinguished from authorization failures, enabling quicker detection of the root issue.

Read the full incident report →