‹ Back to incident history

Incident with Actions

ResolvedMinor incidentGitHub
Thursday, October 22, 2026 22:18 – Thursday, October 22, 2026 23:18 (1 hr)
Affected components
Actions
Updates
ResolvedThursday, October 22, 2026 23:18

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.

MonitoringThursday, October 22, 2026 23:18

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

MonitoringThursday, October 22, 2026 23:17

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

InvestigatingThursday, October 22, 2026 23:06

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.

InvestigatingThursday, October 22, 2026 22:35

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.

InvestigatingThursday, October 22, 2026 22:19

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

InvestigatingThursday, October 22, 2026 22:18

We are investigating reports of degraded performance for Actions

Incident data from the GitHub official status page:Read the official incident

About this data

Where does the incident data for GitHub come from?

Data comes from the GitHub official status page, syncs every 5 minutes, and covers 90 days. The detail page links to the original report.

How do I read the component status bars?

Each block is one day. Green means no issue was reported, yellow means degraded performance, red means a major outage, and gray means no data. Availability covers the last 90 days.

Why is history missing for some services?

Only services with a public official status page are included.

How is duration calculated?

Duration runs from the official start time to recovery, or to the current time for ongoing incidents. Incidents spanning multiple days appear on each affected day.

See the full service list and live status in the status overview