Blacksmith Managed Runners - Operational
Blacksmith Managed Runners
Previous page
Next page
Incremental Docker Builders - Operational
Incremental Docker Builders
API - Operational
API
Website - Operational
Website
Github → Actions - Operational
Github → Actions
Github → API Requests - Operational
Github → API Requests
Github → Webhooks - Operational
Github → Webhooks
This incident has been resolved, GitHub API interactions appear to be back to normal.
We are currently investigating this incident. We have been alerted about some steps in GitHub Action workflows such as checking out the repository and logging in to GHCR taking much longer than usual.
Our dashboard analytics are stale due to the previous incident. We've identified the issue and are working on a fix.
This incident has been resolved.
We've deployed a fix and are monitoring the incident.
We've run into an issue with our upstream database provider. We're working on mitigating this incident.
This incident has been resolved, queue times are back to normal in the US region.
We are currently noticing higher than normal queue times for orgs running in our US region, we are looking into whether this is an upstream GitHub issue
We are seeing signs of recovery in GitHub assigning jobs to our VMs, we will continue to monitor queue times.
We are getting notified of a potential GitHub outage that is causing jobs to not get assigned to our runners, we are monitoring the situation.
The upstream network degradation has been resolved and Docker builds are functioning as normal.
We received information from an upstream provider about degradation in their network stack. We are continuing to monitor recovery of our services.
We are currently investigating reports of degraded performance of our Docker builders in the US region. This may affect jobs using useblackmith/build-push-action@v1
useblackmith/build-push-action@v1
This incident has been resolved, cache operations have returned to normal.
We've identified a fix and are working to deploy it.
We are currently investigating a higher than normal rate of failures when hitting our Blacksmith cace.
GitHub is taking longer than usual to assign jobs to our runners which may manifest as longer queue times. We are looking into this incident.
GitHub has marked the incident as resolved.
GitHub has opened an incident declaring degradation in their GitHub Actions service - https://www.githubstatus.com/incidents/lg4s05t6ttxb. We are monitoring the impact of this on Blacksmith runners.
This incident has been resolved, queue times have returned back to normal.
We are currently investigating delays in GitHub Actions jobs being picked up by our runners in the EU.
GitHub has declared an incident affecting Actions and Packages: https://www.githubstatus.com/incidents/2lxm4wb8wy3r. We're investigating the impact of this incident on our services.
We're seeing signs of recovery after deploying a few fixes, we are continuing to monitor our cache health.
We're seeing signs of recovery and are monitoring the issue.
We're seeing a higher-than-usual rate of failures for cache restores from the Blacksmith cache. We are currently investigating this incident.
We are being alerted about some orgs seeing higher than usual queue times. GitHub is not assigning jobs to our runners in a timely fashion, we are looking into this.
This incident has been resolved, US queue times are back to normal.
We are noticing jobs taking longer than usual to get picked up in our US fleet.
Feb 2025 to Apr 2025
Next