GitHub Actions down again today

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.

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

Monitoring - The degradation affecting Actions and Pages has been mitigated. We are monitoring to ensure stability.

Update - We have identified the cause of the authentication issues affecting GitHub Actions and are actively working on mitigation

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

Update - We are investigating authentication issues leading to failure in starting Actions runs and downloading actions. At this time the majority of Actions runs is impacted.

Update - Actions is experiencing degraded availability. We are continuing to investigate.

Investigating - We are investigating reports of degraded performance for Actions and Pages

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.

Update - This is fully mitigated, we will continue to monitor to ensure it does not reoccur.

Update - We have identified and are applying additional mitigation and will continue to monitor for complete mitigation.

Update - We see significant signs of mitigation and are monitoring for full mitigation.

Update - We are seeing signs of mitigation and are continuing to monitor for complete mitigation. 

Update - We are continuing to investigate an elevated error rate of authentication failures for app installation tokens.  Next update in one hour.

Update - We are seeing an increased rate of authentication failures for app installation tokens, affecting approximately 1% of tokens.  We are continuing to investigate.

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

Resolved - On May 20, 2026, between 16:00 UTC and 17:45 UTC, GitHub Actions customers experienced run start delays exceeding 5 minutes. Approximately 4.5% of all runs were delayed during the impact window, with scale set jobs disproportionately affected. 30% of scale set jobs were delayed and 4% failed to start entirely.

Update - Customer impact has fully subsided. We are maintaining yellow status while we deploy a permanent fix to prevent recurrence.

Update - We've applied a mitigation to fix the issues with queuing and running Actions jobs. We are seeing improvements in telemetry and are monitoring for full recovery.

Monitoring - The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.

Update - A subset of runners are taking longer than expected to connect, which may delay some jobs from beginning execution. We are actively working to mitigate the issue.

Investigating - We are investigating reports of degraded performance for Actions

Resolved - On May 15, 2026, from approximately 07:43 UTC to 08:48 UTC, GitHub Actions experienced a degradation that caused workflow runs to fail or experience delayed starts for a subset of customers. The incident was triggered by a planned failover of supporting infrastructure used by GitHub Actions. During that operation, an automated service discovery update did not propagate correctly, which caused traffic to be routed incorrectly and increased request timeouts in a core dependency for workflow orchestration.

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

Update - We are monitoring an issue that was affecting GitHub Actions and causing downstream issues in GitHub Coding Agent and GitHub Code Review Agent. The issue has resolved now but we are closely monitoring our systems for full recovery.

Update - The degradation affecting Pages has been mitigated. We are monitoring to ensure stability.

Update - The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.

Update - Pages is experiencing degraded availability. We are continuing to investigate.

Investigating - We are investigating reports of degraded availability for Actions

Resolved - Beginning at 02:49 UTC on May 15 2026 and lasting until 03:04 UTC, GitHub.com was unavailable for a subset of customers. This impact has been mitigated and normal service resumed.

Resolved - On May 13, 2026, between 14:31 and 16:03 UTC, the Code Scanning service experienced processing delays and 12% of check runs took over 15 minutes to complete. The delays were caused by replication lag due to an internal database migration, resulting in insufficient worker capacity for our high rate of job enqueues.

Update - CodeQL impact has been mitigated. We are continuing to monitor for durable recovery.

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

Update - We have applied a mitigation to increase processing capacity. We are continuing to monitor to confirm full recovery. We will provide another update by 15:30 UTC.

Update - We are investigating delays affecting CodeQL, the code analysis engine used by Code Scanning. Some users may experience delayed or incomplete code scanning results. Our engineering team is investigating. We will provide another update by 15:15 UTC.

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

Resolved - On May 12, 2026, between 13:41 and 17:43 UTC, some services experienced delays in processing. For the Code Scanning service, 53% of check runs took over 15 minutes to complete. Additionally, notifications took an average of 22 minutes to be delivered and Slack integration webhooks took an average of 20 minutes to be delivered. The delays were caused by replication lag due to an internal database migration, resulting in insufficient worker capacity for our high rate of job enqueues.

Update - All services have fully recovered.

Update - CodeQL has fully recovered. We're continuing to work on recovery for the remaining impacted services.

Update - Webhooks have fully recovered. Continuing to work on recovery for the other services.

Update - Webhooks is operating normally.

Update - We've established that most delays are related to a queuing service and are working to scale out. Early signals from the scale-out are showing signs of recovery for some services. We'll provide an update when services are fully recovered.

Update - Webhooks is experiencing degraded performance. We are continuing to investigate.

Update - We're continuing to investigate issues with CodeQL actions workflows. We're additionally seeing delays for notifications, webhooks, and the Slack integration.

Update - CodeQL actions are currently experiencing delays, which may result in those actions being stuck in a pending state or having failed due to a timeout.

Investigating - We are investigating reports of degraded performance for CodeQL