Current answer
GitHub experienced a critical incident: Incident with Actions. ServiceAlert observed recovery on Aug 26, 2026.
Looking for an update now? Check the current status, or follow GitHub for future changes.
Incident Lifecycle
Affected Components
Actions
Pages
Incident Timeline
Monitoring
The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
Aug 26, 2026 at 5:54 PM UTC
Investigating
We are continuing to observe recovery and expect actions inbound queues to be back to normal in <30min. Work will continue to flow through the system subject to per-customer concurrency limits.
Aug 26, 2026 at 5:32 PM UTC
Investigating
We are continuing to observe recovery and delayed queues are burning down. Some customers will continue to see increased delays until all throttled work has been completed - we expect this within the next hour.
Aug 26, 2026 at 4:50 PM UTC
Investigating
Pages is operating normally.
Aug 26, 2026 at 4:49 PM UTC
Investigating
We believe we've identified and addressed the issue and are ramping traffic back up slowly to ensure it doesn't recur. Some customers will continue to see delays as we ramp up.
Aug 26, 2026 at 4:14 PM UTC
Investigating
primary failover briefly improved performance but did not fully mitigate, we've throttled inbound traffic and are investigating upstream Vitess issues
Aug 26, 2026 at 3:48 PM UTC
Investigating
We've identified an issue with a database primary and are failing over to a replica immediately
Aug 26, 2026 at 3:23 PM UTC
Investigating
Pages is experiencing degraded performance. We are continuing to investigate.
Aug 26, 2026 at 3:12 PM UTC
Investigating
We are investigating reports of degraded availability for Actions
Aug 26, 2026 at 3:11 PM UTC
Was your business affected by this GitHub outage?
Follow GitHub and route available status alerts to email or a team channel.