Incident with Actions
At a glance · GitHub's status
ResolvedLasted 59 min
- First posted
- on GitHub Status
- Ended
- · marked resolved
- Affects
- GitHub Actions
- Edited
- Not since we first saw it
- Source
- GitHub Status · checked 28 min ago
In short
GitHub reported degraded service affecting GitHub Actions, starting 18:28 UTC on 19 Apr 2023. GitHub marked it resolved at 19:27 UTC after 59 min.
GitHub says
GitHub's latest update, , in short excerpts.
This incident has been resolved.
Timeline
Times in UTC, GitHub's own where it gives them.
19 Apr 2023
GitHubFirst public postFrom GitHub's own incident history, before our archive started.
+59 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 · 1 service
- Status
- resolved
- Services
- GitHub Actions
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 ·
This incident has been resolved.
Investigating ·
We've applied a mitigation and workflows targeting hosted Linux/Windows Larger Runners are running again.
Investigating ·
Actions is experiencing capacity constraints with hosted Linux/Windows Larger Runners, leading to high wait times.
Investigating ·
We are investigating reports of degraded performance for Actions.
Last updated