In December, GitHub did not experience any incidents that resulted in degraded performance across GitHub services. This report provides follow-up root-cause detail on the November 25 incident affecting GitHub Packages and Pages.
Follow-up: November 25 Incident (16:34 UTC, detected at 14:39 UTC, lasting 1 hour and 56 minutes)
Customers using GitHub Packages and GitHub Pages experienced unavailability. The Packages service became unavailable for container, npm, and NuGet registries, though RubyGems and Maven remained functional. GitHub Pages was unable to pull packages, causing CI build failures. Repository landing pages experienced timeouts while retrieving package information.
Root Cause: GitHub Packages uses a third-party database to store data for the service, and the provider was experiencing an outage, which impacted GitHub Packages performance.
Resolution: The provider resolved their regional outage before the GitHub team could execute a failover. With the provider’s mitigation complete, GitHub Packages, GitHub Pages, and repository landing pages recovered.
Follow-up Actions: The team plans to enhance resilience for GitHub Pages and repository landing pages against GitHub Packages outages, and to investigate automated failover options for regional incidents.