Availability Summary: February 2021
GitHub’s core services ran without any downtime incidents throughout February. However, the month was not without its challenges: a series of smaller, isolated issues affected subsets of GitHub Actions customers. These were contained and did not have broad impact, but they are under active investigation as part of GitHub’s ongoing reliability efforts.
Early March Incident: GitHub Actions Degradation
On March 1 at 09:59 UTC, service monitors detected a high error rate when creating check suites for workflow runs. The problem lasted one hour and 42 minutes and caused some queued jobs to fail or be delayed. Customers using the search and filter functionality to locate workflows may also have seen incomplete search results during this window.
Because this incident is recent, the root-cause analysis is still in progress. GitHub states that a more detailed breakdown will be published in the March Availability Report, due on the first Wednesday of April. That update is expected to cover contributing factors as well as steps being taken to reduce the impact of future incidents and improve Actions performance.
Context and Next Steps
The rapid growth of GitHub Actions makes its availability and performance critical to users. GitHub acknowledges this and has committed to continued transparency around service reliability. In the interim, real-time system status is available on the GitHub status page, and deeper engineering insights are shared on the GitHub Engineering blog.
