Incident with Actions
At a glance · GitHub's status
ResolvedLasted 2 h 49 min
- First posted
- on GitHub Status
- Ended
- · marked resolved
- Affects
- GitHub Actions, GitHub Pages
- Edited
- Not since we first saw it
- Source
- GitHub Status · checked just now
In short
GitHub reported a major outage affecting GitHub Actions and GitHub Pages, starting 15:11 UTC on 26 Aug. GitHub marked it resolved at 18:01 UTC after 2 h 49 min.
GitHub says
GitHub's latest update, , in short excerpts.
On August 26, 2026 from 15:02 to 15:45 UTC, Actions jobs failed to start.
Timeline
Times in UTC, GitHub's own where it gives them.
26 Aug
GitHubFirst public postFrom GitHub's own incident history, before our archive started.
+2 h 43 min
GitHubMitigated, now monitoring
+2 h 50 min
GitHubResolved
What GitHub changed
GitHub adds updates to its incidents. We save every version (checked every minute) and list what changed. Quotes are short excerpts. The full text is on GitHub's page.
One version so far. If GitHub edits it, each change shows here with what was removed and added.
First version we captured ·
As first seen: resolved · 2 services
- Status
- resolved
- Services
- GitHub Actions, GitHub Pages
Seen by us · GitHub's timestamp · GitHub's page
Affected services
Official updates
Posted by GitHub Status, newest first. The newest are quoted in their first sentence; the full text of each is on GitHub's page.
Resolved ·
On August 26, 2026 from 15:02 to 15:45 UTC, Actions jobs failed to start.
Monitoring ·
All inbound queues have recovered and Actions is operating as expected.
Monitoring ·
The degradation affecting Actions has been mitigated.
Investigating ·
We are continuing to observe recovery and expect actions inbound queues to be back to normal in <30min.
Investigating ·
We are continuing to observe recovery and delayed queues are burning down.
Investigating ·
Pages is operating normally.
Investigating ·
We believe we've identified and addressed the issue and are ramping traffic back up slowly to ensure it doesn't recur.
Investigating ·
primary failover briefly improved performance but did not fully mitigate, we've throttled inbound traffic and are investigating upstream Vitess issues
Investigating ·
We've identified an issue with a database primary and are failing over to a replica immediately
Investigating ·
Pages is experiencing degraded performance.
Investigating ·
We are investigating reports of degraded availability for Actions
Last updated