Status | Blacksmith - Notice history

Blacksmith Managed Runners - Operational

100% - uptime
Apr 2025 · 99.81%May · 100.0%Jun · 99.94%
Apr 2025
May 2025
Jun 2025

Incremental Docker Builders - Operational

100% - uptime
Apr 2025 · 99.81%May · 100.0%Jun · 99.88%
Apr 2025
May 2025
Jun 2025

API - Operational

100% - uptime
Apr 2025 · 99.81%May · 100.0%Jun · 100.0%
Apr 2025
May 2025
Jun 2025

Website - Operational

100% - uptime
Apr 2025 · 100.0%May · 100.0%Jun · 100.0%
Apr 2025
May 2025
Jun 2025

Github → Actions - Operational

Github → API Requests - Operational

Github → Webhooks - Operational

Notice history

Jun 2025

Potential GitHub outage preventing jobs from being assigned to our runners
  • Resolved
    Resolved

    GitHub have marked their incident as closed, our runners are back to behaving as expected.

  • Update
    Update

    GitHub has declared a widespread incident that is affecting Actions as well, we will continue to monitor their status page for updates - https://www.githubstatus.com/incidents/y7lb2rg4btd7

  • Investigating
    Investigating

    We are seeing an uptick in upstream errors from the GitHub control plane, preventing runners from being assigned jobs. We are monitoring the situation.

GitHub is reporting degraded performance for Actions
  • Resolved
    Resolved

    This incident has been resolved by GitHub.

  • Investigating
    Investigating

    GitHub has opened an incident for degraded performance of their Actions service https://www.githubstatus.com/incidents/ry1gsyjqj4qh

May 2025

Receiving reports of cache failures in Blacksmith runners
  • Resolved
    Resolved

    GitHub has resolved the incident, we will continue to monitor interactions with our cache.

  • Identified
    Identified

    GitHub have declared an incident related to the upstream cache service - https://www.githubstatus.com/incidents/9hzy25gws8vh

  • Update
    Update

    An upstream issue has been filed against the actions/cache repository indicating other users are also noticing errors of the form The runner was not able to contact the cache service - https://github.com/actions/cache/issues/1611

    We are continuing to investigate the root cause.

  • Investigating
    Investigating

    We are currently investigating this incident, we are receiving reports of failures to contact the Blacksmith cache.

Reports of GitHub Actions never ending even though the steps have all completed
  • Resolved
    Resolved

    We are no longer receiving reports of this behaviour, we will continue to monitor the situation.

  • Investigating
    Investigating

    We are receiving reports from several customer where they see their GitHub Actions completing all the steps, but then spinning in the final Complete job stage. This is causing jobs to hit their timeouts and eventually fail. There have been numerous reports of this in the past:
    https://github.com/actions/runner/issues/3462
    https://github.com/actions/runner/issues/2409


    GitHub has not yet opened an incident but we expect there to be one soon.

Apr 2025

Apr 2025 to Jun 2025

Next