Status | Blacksmith - Notice history

Blacksmith Managed Runners - Operational

100% - uptime
Jan 2025 · 100.0%Feb · 100.0%Mar · 100.0%
Jan 2025
Feb 2025
Mar 2025

Incremental Docker Builders - Operational

100% - uptime
Jan 2025 · 100.0%Feb · 100.0%Mar · 100.0%
Jan 2025
Feb 2025
Mar 2025

API - Operational

100% - uptime
Jan 2025 · 100.0%Feb · 100.0%Mar · 100.0%
Jan 2025
Feb 2025
Mar 2025

Website - Operational

100% - uptime
Jan 2025 · 100.0%Feb · 100.0%Mar · 100.0%
Jan 2025
Feb 2025
Mar 2025

Github → Actions - Operational

Github → API Requests - Operational

Github → Webhooks - Operational

Notice history

Mar 2025

Degraded performance of GitHub Actions reported by Github
  • Resolved
    Resolved

    GitHub has marked the incident as resolved.

  • Investigating
    Investigating

    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.

Feb 2025

Incident affecting GitHub Actions
  • Resolved
    Resolved
    This incident has been resolved.
  • Investigating
    Investigating

    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.

Jan 2025

Increased time for GitHub to assign jobs to our runners
  • Resolved
    Resolved

    GitHub has resolved the incident, queue times are returning to normal on Blacksmith runners.

  • Investigating
    Investigating

    GitHub has declared an incident which is causing some degradation in their ability to assign jobs to our runners - https://www.githubstatus.com/incidents/nm83zrdky73y. Customer may notice increased queue times during this period.

Reports of job setup failing due to network degradation
  • Resolved
    Resolved

    This incident has been resolved, runners are consistently working as expected.

  • Monitoring
    Monitoring

    We are seeing signs of recovery, jobs are consistently being able to setup their environments and pull artifacts. We are continuing to monitor the situation until all our monitoring returns to its baseline.

  • Update
    Update

    We are seeing degradation across both our US and EU fleets, which are on different networking stacks. This suggests that there is a degradation on GitHub's end, as can be seen on downdetector - https://downdetector.com/status/github/. We're still investigating on our end.

  • Investigating
    Investigating

    We are seeing reports of some network degradation across our fleet. It is unclear whether this is on GitHub's end or not. We are looking into the issue.

GitHub reporting degradation in Git operations
  • Resolved
    Resolved
    This incident has been resolved.
  • Monitoring
    Monitoring

    GitHub posted an update

    "We've identified a cause of degraded git operations, which may affect other GitHub services that rely upon git. We're working to remediate."

  • Identified
    Identified

    GitHub posted an update "Actions is experiencing degraded performance. We are continuing to investigate."

    https://www.githubstatus.com/incidents/qd96yfgvmcf9

    We're continuing to monitor this.

  • Investigating
    Investigating

    GitHub has opened an incident reporting degradation in Git operations. This may manifest as checkouts failing in GitHub Action workflows - https://www.githubstatus.com/incidents/qd96yfgvmcf9

Jan 2025 to Mar 2025

Next