Incident with Actions

What to do

• Check whether you use GitHub Actions. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 1h 1m it lasted.

  Anything that failed between 2026-10-22 14:18 UTC and 2026-10-22 15:18 UTC may need a replay.

• Subscribe to GitHub's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=github works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from GitHub 7

1. investigatingOct 22, 2026, 2:18 PM UTC

   We are investigating reports of degraded performance for Actions

   provider

2. investigatingOct 22, 2026, 2:19 PM UTC

   We’re investigating delays in processing GitHub Actions workflow and step results, along with some repository updates.

   provider

3. investigatingOct 22, 2026, 2:35 PM UTC

   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.

   provider

4. investigatingOct 22, 2026, 3:06 PM UTC

   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.

   provider

5. monitoringOct 22, 2026, 3:17 PM UTC

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

   provider

6. monitoringOct 22, 2026, 3:18 PM UTC

   GitHub Actions workflow and step result processing has recovered. Repository update processing has also returned to normal.

   provider

7. resolvedOct 22, 2026, 3:18 PM UTC

   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. The incident was caused by a significant increase in load coupled with client connection storms during a deployment overloading our Kafka event streaming brokers. To prevent future recurrence, we have expanded the affected cluster, shifted traffic to less loaded clusters, and implemented tunable client reconnect backoff.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.