GitHub Actions and Pages are experiencing degraded availability

GitHub's automation platform, Actions, and hosting service Pages are currently experiencing significant stability issues, as reported on the service's status site. These problems are part of a series of recent outages that the platform has faced. GitHub initially reported the issue at 1522 UTC on Thursday, noting that Actions were dealing with "degraded performance," followed by an update 20 minutes later stating that availability was also degraded.

Shortly after, GitHub disclosed that workflow runs were failing to initiate or complete, and requests to the Actions REST API were returning errors. Users also encountered unexpected rate limits. The cause of these issues was attributed to an unnamed factor, although it was discovered over two hours ago, and the situation remains unresolved.

Pages were added to the list of affected systems shortly after GitHub announced it was working on mitigating the issue. Apart from these problems, GitHub's Copilot code review, coding agent, hosted runners, and migrations using GitHub Enterprise Importer were also reportedly impacted by the outage, along with potential delays in Webhook deliveries.

This latest outage is the latest in a string of stability issues at GitHub. The platform's status history page reveals the severity of the situation, with numerous incidents logged in recent months. July saw a similar Actions outage, and June had 23 incidents, May had 23 as well, and April had 26 incidents. In just six days of August, the platform has logged six incidents.

Developers have become increasingly frustrated with the platform's instability, with some considering moving their projects to alternative platforms. Ghostty developer Mitchell Hashimoto even went so far as to state that the platform has become unsuitable for hosting "serious work." GitHub apologized for the continued glut of outages in April, but it remains to be seen if their promised structural improvements have made a difference. A response from GitHub regarding this latest issue has not been received at the time of writing.