What the official timeline says
GitHub marked its November 9 Actions and Checks API incident resolved at 18:59 UTC. Earlier, at 18:43 UTC, it said degradation affecting Actions, Pages and Webhooks had been mitigated and moved to monitoring.
GitHub began investigating degraded Actions availability at 18:12 UTC on November 9. It added degraded Webhooks performance at 18:23 UTC, elevated errors affecting Actions and the Checks API at 18:24 UTC, and degraded Pages performance at 18:30 UTC.
Which work may need checking
The incident page lists Webhooks, Actions and Pages as affected services. Teams using automated checks, event-triggered workflows or Pages publishing should check their actual run and deployment results before assuming work completed.
The provider has not described this as a complete outage of every GitHub feature. A failed or delayed check is not evidence that a code change itself is faulty, and the notice does not establish that existing repositories or all published sites are unavailable.
Resolved, with root-cause analysis pending
The official resolution notice thanks users for their patience and says a detailed root-cause analysis will follow when available. Teams can check delayed workflow, webhook and deployment results in their actual projects; a resolved service notice does not confirm that each queued task completed.
