GitHub Status

GitHub’s status page tracks incident history across its major service components: Git operations, the REST and GraphQL APIs, Actions, Pages, and Packages. When a push silently fails or a workflow run stalls mid-queue, the official record of why appears here. Incident write-ups are clear and timestamped; most include a root-cause explanation once the post-mortem is complete.

The page does not cover known limitations or planned fixes. That surface lives on the GitHub blog under “Changelog” — a separate feed worth bookmarking alongside the status atom feed for teams that care about behaviour changes rather than outages alone. For most engineering teams, githubstatus.com is the first diagnostic stop: if Actions is degraded, the incident lands here before it surfaces in any other official channel.