Skip to content
Sengi

Is GitHub Actions down? Live status and 2026 outage history

Is GitHub Actions down right now?

GitHub Actions is up. That is what GitHub's status feed said at November 21, 2026, 09:25 UTC; this page refreshes every minute. Sengi reads it from githubstatus.com, GitHub's official status page.

Sengi runs hosted runners for GitHub Actions and publishes this page. It is not affiliated with GitHub.

Recent GitHub Actions incidents

StartedIncidentImpactLength
November 16, 2026, 11:59 UTCIncident with Pull Requestsminor4 h 27 min
November 11, 2026, 20:48 UTCImpact across multiple GitHub products including Actions, Pages, and Copilot products.critical33 min
November 10, 2026, 16:10 UTCIncident with Git Operations and Pull Requestscritical1 h 44 min
November 9, 2026, 18:12 UTCIncident with Actions and Checks APIcritical47 min
November 9, 2026, 10:00 UTCIncident with Webhooks and Actionsmajor1 h 50 min
November 5, 2026, 23:36 UTCDegraded performance for multiple GitHub servicesminor45 min
November 5, 2026, 16:50 UTCIncident with Actionsminor52 min
November 4, 2026, 17:40 UTCIncident with Actionsmajor36 min
November 4, 2026, 16:05 UTCIncident with Actions and Pagesmajor56 min
November 4, 2026, 09:49 UTCIncident with Pull Requests, Git Operations and Issuesmajor2 h

The latest 10 incidents that list Actions, from GitHub's status feed. Older ones are on githubstatus.com.

How often GitHub Actions went down in 2026

We read every incident on GitHub's status page from January 1 to November 19, 2026, and kept the 86 that affected Actions: 74 that list the Actions component and 12 whose updates say Actions jobs were hit.

Where the problem wasIncidentsCritical or majorHours on the status page
GitHub's queueing, triggers, API or platform6835132
GitHub-hosted runners only15751
Not stated315
All Actions incidents8643188

Source: githubstatus.com incident history, read November 19, 2026, classified by Sengi from each incident's own updates. Hours run from GitHub's first post to "resolved", which is not always the length of the outage.

Which outages a different runner avoids

A GitHub Actions job passes through GitHub before it reaches any machine: GitHub triggers the workflow, queues the job and hands it to a runner that matches its runs-on label. When that part of GitHub fails, every runner waits, whoever runs it. That was 68 of the 86 incidents in 2026.

The other kind of outage is in GitHub's own runner fleet. In those 15 incidents, jobs on self-hosted and third-party runners kept going. The longest:

  • February 2, 5 h 53 min. An Azure policy change blocked every GitHub-hosted runner VM. GitHub: “Self-hosted runners on other providers were not impacted.” (incident)
  • July 9, 9 h 18 min. Delayed and failed job starts on GitHub-hosted runners, from a backend service that provisions hosted runners. (incident)
  • October 5, 3 h 38 min. A critical incident on GitHub-hosted runners. GitHub: “Self-hosted runners were not affected.” (incident)

It cuts both ways. On July 19, self-hosted and larger runners could not connect to GitHub for about five hours while standard GitHub-hosted runners worked, and the August 6 outage, the longest of the year, hit both.

What to do when GitHub Actions is down

  • Confirm it is GitHub. If the status above is green, check the job's runs-on label and your plan's concurrent job limit first.
  • Do not re-run in a loop. Queued jobs usually start on their own once GitHub recovers; re-run the ones that failed after the incident is resolved.
  • Check required checks. Pull requests can sit blocked on a check that never reported. Re-run that workflow once Actions is back.
  • Plan for runner outages. If GitHub-hosted runner outages cost you most, a second runner provider for your Linux jobs is a one-line runs-on change.

Where Sengi fits

Sengi runs hosted Linux runners for GitHub Actions, outside GitHub's runner fleet. When GitHub-hosted runners are the problem, jobs on Sengi keep running; when GitHub itself is down, they wait like every other runner. Sengi Basic is $0.001 a minute at 2 vCPU, one-sixth of GitHub's $0.006, with 3,000 included minutes a month and no card to start. Moving a job is one line: runs-on: sengi-basic-2-ubuntu-2404. See Sengi pricing and the guide.

FAQ

Is GitHub Actions down right now?

The status at the top of this page comes from GitHub's own status feed and refreshes every minute. If it shows no incident but your jobs are stuck, check that your runner label exists and your concurrency limit is not full before assuming an outage.

How often does GitHub Actions go down?

GitHub's status page lists 86 incidents that affected Actions between January 1 and November 19, 2026, 43 of them rated critical or major. Their status windows add up to about 188 hours.

Do third-party runners keep working when GitHub Actions is down?

Only when the problem is in GitHub's own hosted runners, which was 15 of the 86 incidents in 2026. When GitHub's queueing, triggers, webhooks or API fail, jobs on every runner wait, including third-party and self-hosted runners.

Why are my GitHub Actions jobs stuck in queued?

Either GitHub is delaying job starts, which shows up here as an incident, or no runner matches the job's runs-on label, or your plan's concurrent job limit is full. See why GitHub Actions jobs get stuck.

Is this GitHub's official status page?

No. Sengi, which runs hosted runners for GitHub Actions, publishes this page. The live status is read from githubstatus.com, GitHub's official status page.

Keep your workflow. Cut your runner rate.

Sengi Basic starts at $0.001 a minute for 2 vCPU. Choose 4 or 8 vCPU for $0.002 or $0.004 a minute. Premium stays optional at $0.003, $0.006 and $0.012.

Start without a card ↗︎

See Basic pricing · Switch with your coding agent