Part of GitHub

GitHub Actions Outage History

GitHub Actions is up right now

GitHub Actions had 33 outages in the last 2 years totaling 14h 58m of downtime, averaging 1.4 incidents per month.

There were 33 GitHub Actions outages since March 3, 2026 totaling 14h 58m of downtime. Each is summarised below. Incident details, duration, and resolution information.

Source: githubstatus.com

Critical April 23, 2026

Incident with multiple GitHub services

Detected by Pingoru
Apr 23, 2026, 04:12 PM UTC
Resolved
Apr 23, 2026, 05:30 PM UTC
Duration
1h 18m
Affected: WebhooksActionsCopilot
Timeline · 8 updates
  1. investigating Apr 23, 2026, 04:12 PM UTC

    We are investigating reports of degraded availability for Copilot and Webhooks

  2. investigating Apr 23, 2026, 04:19 PM UTC

    We are investigating multiple unavailable services.

  3. investigating Apr 23, 2026, 04:34 PM UTC

    Actions is experiencing degraded performance. We are continuing to investigate.

  4. investigating Apr 23, 2026, 04:52 PM UTC

    We have identified the root problem and are working on mitigation.

  5. investigating Apr 23, 2026, 05:03 PM UTC

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

  6. investigating Apr 23, 2026, 05:04 PM UTC

    Many services are mitigated and are validating the remaining services.

  7. investigating Apr 23, 2026, 05:10 PM UTC

    Webhooks is operating normally.

  8. resolved Apr 23, 2026, 05:30 PM UTC

    This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.

Read the full incident report →

Minor April 23, 2026

Investigating errors on GitHub

Detected by Pingoru
Apr 23, 2026, 02:40 PM UTC
Resolved
Apr 23, 2026, 03:18 PM UTC
Duration
38m
Affected: ActionsPackagesCodespacesCopilot
Timeline · 8 updates
  1. investigating Apr 23, 2026, 02:40 PM UTC

    We are investigating reports of degraded performance for Actions

  2. investigating Apr 23, 2026, 02:41 PM UTC

    Packages is experiencing degraded performance. We are continuing to investigate.

  3. investigating Apr 23, 2026, 02:42 PM UTC

    Codespaces is experiencing degraded performance. We are continuing to investigate.

  4. investigating Apr 23, 2026, 02:44 PM UTC

    Copilot is experiencing degraded performance. We are continuing to investigate.

  5. investigating Apr 23, 2026, 02:51 PM UTC

    Users are experiencing errors loading various web pages on github.com. Actions and Copilot Cloud Agent runs will be delayed.

  6. investigating Apr 23, 2026, 03:02 PM UTC

    A mitigation was applied and services have recovered. Actions is working through queued work before fully recovering.

  7. monitoring Apr 23, 2026, 03:02 PM UTC

    The degradation affecting Actions, Codespaces, Copilot and Packages has been mitigated. We are monitoring to ensure stability.

  8. resolved Apr 23, 2026, 03:18 PM UTC

    This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.

Read the full incident report →

Minor March 30, 2026

Elevated delays in Actions workflow runs and Pull Request status updates

Detected by Pingoru
Mar 30, 2026, 01:02 PM UTC
Resolved
Mar 30, 2026, 01:25 PM UTC
Duration
23m
Affected: Pull RequestsActions
Timeline · 4 updates
  1. investigating Mar 30, 2026, 01:02 PM UTC

    We are investigating reports of degraded performance for Actions and Pull Requests

  2. monitoring Mar 30, 2026, 01:20 PM UTC

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

  3. monitoring Mar 30, 2026, 01:25 PM UTC

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

  4. resolved Mar 30, 2026, 01:25 PM UTC

    On March 30, 2026, between 10:11 UTC and 13:25 UTC, GitHub Actions experienced degraded performance. During this time, approximately 2.65% of workflow jobs triggered by pull request events experienced start delays exceeding 5 minutes. The issue was caused by replication lag on an internal database cluster used by Actions, which triggered write throttling in our database protection layer and slowed job queue processing. The replication lag originated from planned maintenance to scale the internal database. Newly added database hosts triggered guardrails in the throttling layer, restricting write throughput. The incident was mitigated by excluding the new hosts from replication delay calculations. To prevent recurrence, we have updated our maintenance procedures to ensure new hosts are excluded from throttling assessments during scaling operations. Additionally, we are investing in automation to streamline this type of maintenance activity.

Read the full incident report →