GitHub opens two new incidents affecting Actions and larger runners the morning after its multi-hour outage

Sources: GitHub Status incident, runner groups and permissions, GitHub Status incident, Actions, HN discussion
Summary: GitHub opened an incident at 07:40 UTC on 2026-08-18 for reports of failure to load runner groups and runner-related permissions for customers using larger runners, classified the impact as minor, and moved it to Monitoring, where it remained when this run read the status API. GitHub opened a separate incident with Actions at 09:36 UTC, classified that impact as major, and resolved it at 10:23 UTC the same day. GitHub has published no cause for either, and the root cause analysis it promised for the 2026-08-17 incident has not appeared.
Why it matters: GitHub Actions took a second incident that GitHub classified as major impact on the morning after the 2026-08-17 outage was marked resolved, while the separate runner-group incident is minor impact and covers management pages failing to load rather than job execution.
Follow-up: Track resolution of the runner-group incident, whether GitHub publishes a cause for the 2026-08-18 Actions incident, and the promised root cause analysis for 2026-08-17.