Is there an GitHub outage?
GitHub status: Systems Active
Last checked: 3 minutes ago
Get notified about any outages, downtime or incidents for GitHub and 1800+ other cloud vendors. Monitor 10 companies, for free.
Last checked: 3 minutes ago
Get notified about any outages, downtime or incidents for GitHub and 1800+ other cloud vendors. Monitor 10 companies, for free.
Outage and incident data over the last 30 days for GitHub.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage. It's completely free and takes less than 2 minutes!
Sign Up NowOutlogger tracks the status of these components for Xero:
| Component | Status |
|---|---|
| Actions | Active |
| API Requests | Active |
| Codespaces | Active |
| Copilot | Active |
| Git Operations | Active |
| Issues | Active |
| Packages | Active |
| Pages | Active |
| Pull Requests | Active |
| Visit www.githubstatus.com for more information | Active |
| Webhooks | Active |
View the latest incidents for GitHub and check for official updates:
Description: This incident has been resolved.
Status: Resolved
Impact: Major | Started At: Nov. 19, 2024, 11:36 a.m.
Description: On October 30, 2024, between 5:45 and 9:42 UTC, the Actions service was degraded, causing run delays. On average, Actions workflow run, job, and step updates were delayed as much as one hour. The delays were caused by updates in a dependent service that led to failures in Redis connectivity. Delays recovered once the Redis cluster connectivity was restored at 8:16 UTC. The incident was fully mitigated once the job queue had processed by 9:24 UTC. This incident followed an earlier short period of impact on hosted runners due to a similar issue, which was mitigated by failing over to a healthy cluster.<br /><br />From this, we are working to improve our observability across Redis clusters to reduce our time to detection and mitigation of issues like this one in the future where multiple clusters and services were impacted. We will also be working to reduce the time to mitigate and improve general resilience to this dependency.
Status: Resolved
Impact: Minor | Started At: Oct. 30, 2024, 7:25 a.m.
Description: On Oct 24 2024 at 06:55 UTC, a syntactically correct, but invalid discussion template YAML config file was committed in the community/community repository. This caused all users of that repository who tried to access a discussion template or attempted to create a discussion to receive a 500 error response.<br /><br />We mitigated the incident by manually reverting the invalid template changes.<br /><br />We are adding support to detect and prevent invalid discussion template YAML from causing user-facing errors in the future.
Status: Resolved
Impact: Minor | Started At: Oct. 24, 2024, 6:12 a.m.
Description: On October 11, 2024, starting at 05:59 UTC, DNS infrastructure in one of our sites started to fail to resolve lookups following a database migration. Attempts to recover the database led to cascading failures that impacted the DNS systems for that site. The team worked to restore the infrastructure and there was no customer impact until 17:31 UTC. <br /><br />During the incident, impact to the following services could be observed:<br /><br />- Copilot: Degradation in IDE code completions for 4% of active users during the incident from 17:31 UTC to 21:45 UTC.<br />- Actions: Workflow runs delay (25% of runs delayed by over 5 minutes) and errors (1%) between 20:28 UTC and 21:30 UTC. Errors while creating Artifact Attestations.<br />- Customer migrations: From 18:16 UTC to 23:12 UTC running migrations stopped and new ones were not able to start.<br />- Support: support.github.com was unavailable from 19:28 UTC to 22:14 UTC. <br />- Code search: 100% of queries failed between 2024-10-11 20:16 UTC and 2024-10-12 00:46 UTC.<br /><br />Starting at 18:05 UTC, engineering attempted to repoint the degraded site DNS to a different site to restore DNS functionality. At 18:26 UTC the test system had validated this approach and a progressive rollout to the affected hosts proceeded over the next hour. While this mitigation was effective at restoring connectivity within the site, it caused issues with connectivity from healthy sites back to the degraded site, and the team proceeded to plan out a different remediation effort.<br /><br />At 20:52 UTC, the team finalized a remediation plan and began the next phase of mitigation by deploying temporary DNS resolution capabilities to the degraded site. At 21:46 UTC, DNS resolution in the degraded site began to recover and was fully healthy at 22:16 UTC. Lingering issues with code search were resolved at 01:11 UTC on October 12.<br /><br />The team continued to restore the original functionality within the site after public service functionality was restored. GitHub is working to harden our resiliency and automation processes around this infrastructure to make diagnosing and resolving issues like this faster in the future.
Status: Resolved
Impact: Major | Started At: Oct. 11, 2024, 5:53 p.m.
Description: This incident has been resolved.
Status: Resolved
Impact: Minor | Started At: Oct. 8, 2024, 5:02 p.m.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage or down time. Join for free - no credit card required.
