Blacksmith Outage History

GitHub Actions experienced degraded availability for 2.6 hours, preventing jobs from being picked up due to severe degradation in GitHub's API. The incident affected GitHub Actions and API requests, causing a backlog of jobs that needed to be processed. Recovery began when GitHub's APIs came back online, with some elevated wait times continuing as the remaining backlog was cleared.

Blacksmith experienced upstream failures with GitHub's API for 2.7 hours, affecting job adoption and GitHub interactions in running jobs. The issue was caused by a GitHub outage that impacted their APIs and Actions services. GitHub implemented a fix and service began recovering, though git operations remained degraded during the monitoring phase.

Blacksmith experienced delays in job adoption and degraded GitHub service interactions, primarily affecting Checkout actions, due to an upstream GitHub outage. The incident impacted GitHub Actions and Blacksmith Managed Runners for 12.6 hours. The service showed signs of recovery and was resolved through monitoring as the upstream GitHub issues were addressed.

Blacksmith experienced degraded performance with GitHub Actions job adoption due to a related GitHub incident. The service disruption affected GitHub Actions, API requests, and webhooks for 44 minutes. The team monitored the situation and the issue was resolved following the resolution of the upstream GitHub incident.