GitHub reported this minor-impact incident on its official status page on Oct 22, 2026, 14:18 UTC. It was resolved after 1h 1m.
Right now GitHub is operational. Live GitHub status →
On October 22, 2026, from 13:05 to 15:20 UTC, our event streaming platform was degraded resulting in elevated job processing latency spikes of 19-35 seconds and elevated job processing times of 4m – this resulted in delayed Actions workflow and step results (up to 13m), notifications (20m) and repository push events (12m). Recovery for repositories began at 14:32, with Actions recovery beginning at 14:59. The issue reoccurred at 16:26 again impacting Actions runs, repo push events, and notifications. Recovery began at 17:16 and completed at 2:07. <br /><br />The incident was caused by a significant increase in load coupled with client connection storms during a deployment overloading our Kafka event streaming brokers. <br /><br />To prevent future recurrence, we have expanded the affected cluster, shifted traffic to less loaded clusters, and implemented tunable client reconnect backoff.
GitHub Actions workflow and step result processing has recovered. Repository update processing has also returned to normal.
The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
We’re seeing recovery, and repository update processing has returned to normal. Delays affecting GitHub Actions workflow and step results are continuing to clear as we scale processing capacity; the remaining backlog is expected to take about 20 minutes to drain.
Repository update processing has recovered. We’re continuing to work on delays affecting GitHub Actions workflow and step results. We’ll share another update as we make progress.
We’re investigating delays in processing GitHub Actions workflow and step results, along with some repository updates.
We are investigating reports of degraded performance for Actions
Overlapping incidents aren't necessarily related.
GitHub reported 67 incidents in the last 90 days, 24 of them major or critical. A typical incident lasted 1h 15m. See GitHub's uptime and incident history