ismyagentdownAll agentsAlerts
All agents  /  GitHub  /  History  /  Oct 22, 2026

GitHub outage on Oct 22, 2026: incident with Actions

Resolved after 1 h 1 min.

14:18 UTC to 15:18 UTC your time. GitHub: “Incident with Actions.” 0 reports here during the incident.

GitHubUpRight now GitHub is up. See live status

Reports during the incident

Every 15 minutes, 13:15 UTC to 16:30 UTC. Grey: normal. Red line: official incident.
13:15 UTC14:18 UTC15:18 UTC16:30 UTC

What people reported

0 reports during the incident

No reports in this window.

GitHub's updates

Quoted from www.githubstatus.com

  1. 14:18 UTC

    Investigating

    We are investigating reports of degraded performance for Actions

  2. 14:19 UTC

    Investigating

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

  3. 14:35 UTC

    Investigating

    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.

  4. 15:06 UTC

    Investigating

    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.

  5. 15:17 UTC

    Monitoring

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

  6. 15:18 UTC

    Monitoring

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

  7. 15:18 UTC

    Resolved

    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.

Other GitHub incidents

Nov 81 h 57 minIncrease in timeouts for some unauthenticated usersDetails
Nov 545 minDegraded performance for multiple GitHub servicesDetails
Nov 552 minIncident with ActionsDetails
All GitHub incidents

Other agents

Claude CodeUpCodexUpCursor IDEUpGitHub CopilotUpGemini CLIUpClaude APIUpOpenAI APIUp

Know the moment it's back.

Coral shows it in your Mac's notch, and tells you which agent needs you. Free.

Get Coral for Mac

Official status from Anthropic, OpenAI, GitHub, Google and Cursor, checked every minute. Reports come from people on this site. We keep no IP address and set no cookies.

AlertsRSSPrivacyMade by Coral