ChangeIntel IT change radar
Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord
Resolved GitHub · degraded service

Incident with Actions and Checks API

Posted 9 Nov 18:12 UTC, last seen today 13:21 UTC.

GitHub status pageOn the status board
Unknown Duration: the provider stated no start
8Updates posted
6Other incidents at the same time

What it affected

As the provider names it

WebhooksActionsPages

What the provider posted

Newest first
  1. 9 Nov 18:59 UTCResolvedOn 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. 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. 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.
  2. 9 Nov 18:59 UTCResolvedThis 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.
  3. 9 Nov 18:43 UTCMonitoringThe degradation affecting Actions, Pages and Webhooks has been mitigated. We are monitoring to ensure stability.
  4. 9 Nov 18:30 UTCUpdatePages is experiencing degraded performance. We are continuing to investigate.
  5. 9 Nov 18:24 UTCUpdateWe're investigating elevated errors affecting GitHub Actions and the Checks API. We'll share another update as we learn more.
  6. 9 Nov 18:23 UTCUpdateWebhooks is experiencing degraded performance. We are continuing to investigate.
  7. 9 Nov 18:14 UTCUpdateActions is experiencing degraded availability. We are continuing to investigate.
  8. 9 Nov 18:12 UTCInvestigatingWe are investigating reports of degraded availability for Actions
  9. 9 Nov 18:29 UTC ChangeIntel noticed a new title; it was "Incident with Actions"

Around it

From the sources ChangeIntel reads; a match in time is not a cause

Earlier incidents in the 14 days before

Keep track

What changed

  1. Services: Actions → Webhooks, Actions, Pages · Status: Monitoring → Resolved · Incident state: Ongoing → Ended
  2. Status: Investigating → Monitoring
  3. Title changed
Page history

Changes are dated when recorded; day views use the last saved version from that UTC day, and citations stay fixed.

Cite this version
Field-level log (12)

Up to 100 recent field edits are shown; older edits may be outside retention.

  1. 13 Nov 2026 · 04:19:40 UTC SummaryThis 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. → 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. 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. 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.
  2. 9 Nov 2026 · 19:00:25 UTC ServicesActions → Webhooks, Actions, Pages
  3. 9 Nov 2026 · 19:00:25 UTC StageMonitoring → Resolved
  4. 9 Nov 2026 · 19:00:25 UTC Observed stateOngoing → Ended
  5. 9 Nov 2026 · 19:00:25 UTC SummaryThe degradation affecting Actions, Pages and Webhooks has been mitigated. We are monitoring to ensure stability. → 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.
  6. 9 Nov 2026 · 18:45:04 UTC StageInvestigating → Monitoring
  7. 9 Nov 2026 · 18:45:04 UTC SummaryPages is experiencing degraded performance. We are continuing to investigate. → The degradation affecting Actions, Pages and Webhooks has been mitigated. We are monitoring to ensure stability.
  8. 9 Nov 2026 · 18:34:26 UTC SummaryWe're investigating elevated errors affecting GitHub Actions and the Checks API. We'll share another update as we learn more. → Pages is experiencing degraded performance. We are continuing to investigate.
  9. 9 Nov 2026 · 18:29:15 UTC SummaryWebhooks is experiencing degraded performance. We are continuing to investigate. → We're investigating elevated errors affecting GitHub Actions and the Checks API. We'll share another update as we learn more.
  10. 9 Nov 2026 · 18:29:15 UTC TitleIncident with Actions → Incident with Actions and Checks API
  11. 9 Nov 2026 · 18:24:04 UTC SummaryActions is experiencing degraded availability. We are continuing to investigate. → Webhooks is experiencing degraded performance. We are continuing to investigate.
  12. 9 Nov 2026 · 18:18:58 UTC SummaryWe are investigating reports of degraded availability for Actions → Actions is experiencing degraded availability. We are continuing to investigate.
ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 13 Nov 13:11 UTC · 274 of 275 readable · 273 fully read · documentation 469/469 current

No accounts or analytics; your preferences stay in your browser. Information, not advice. ChangeIntel is an independent tool and is not affiliated with or endorsed by Microsoft, Apple, Google, Broadcom (VMware), Jamf, Oracle, Mozilla, or any other vendor it covers. Product names are trademarks of their owners. Built by Evotec.