‹ Back to incident history

Incident with Actions and Checks API

ResolvedCritical outageGitHub
Tuesday, November 10, 2026 02:12 – Tuesday, November 10, 2026 02:59 (46 min)
Affected components
Webhooks
Actions
Pages
Updates
ResolvedTuesday, November 10, 2026 02:59

On November 9, 2026, between 18:07 and 18:59 UTC, GitHub Actions experienced degraded performance. During this time, some customers saw workflow runs fail to start, update or report status correctly. An average of 28% of workflow runs were affected, peaking at 65% during the worst period of the incident. Once Actions services recovered, some jobs were left in a state that limited available concurrency until the runs were released. <br /><br />The incident occurred during a planned migration of a core Actions database from GitHub’s datacenter to a new cloud region. After the migration completed, we shifted Actions service traffic to the new region. The volume of requests exceeded the capacity and rate limits configured there, so a portion of requests were rejected and workflow updates failed. Dependent services, including Webhooks, Pages and Copilot code review, saw secondary impact. <br /><br />We mitigated impact by shifting some of the traffic back to the original region, allowing service traffic to remain within the configured limits. We then increased capacity and rate limits in the new region before gradually shifting traffic back. While this was a one-time migration event for this cluster that is now complete, we are improving how we validate capacity and limits before shifting traffic during remaining migrations, including shifting traffic in smaller steps. To address the stuck runs left after the incident, we are improving our ability to detect and mitigate these runs for future cases as well as readying an API to enable customers to address this themselves.

MonitoringTuesday, November 10, 2026 02:43

The degradation affecting Actions, Pages and Webhooks has been mitigated. We are monitoring to ensure stability.

InvestigatingTuesday, November 10, 2026 02:30

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

InvestigatingTuesday, November 10, 2026 02:24

We're investigating elevated errors affecting GitHub Actions and the Checks API. We'll share another update as we learn more.

InvestigatingTuesday, November 10, 2026 02:23

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

InvestigatingTuesday, November 10, 2026 02:14

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

InvestigatingTuesday, November 10, 2026 02:12

We are investigating reports of degraded availability 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