Incident: arm64 Macro Runners Outage

Since midnight UTC on November 5, 2026, our arm64 macro runners are unavailable. Our infrastructure provider removed the instances they run on without giving us notice to migrate, so benchmark jobs targeting them fail or stay queued. We're moving every team to our x86 macro runners and will keep this entry updated as things change.

Updates

• Nov 5, 00:00 UTC — arm64 macro runner jobs stop starting.
• Nov 5, 10:30 UTC — Outage confirmed. We're contacting impacted teams directly and working on a solution. Next update within 24 hours.

Who is affected

Any workflow using one of these runner labels:

runs-on: codspeed-macro-arm64-graviton-ubuntu-22-04
# or the former label
runs-on: codspeed-macro

Not affected:

• The x86 macro runners on GitHub Actions (codspeed-macro-x64-ryzen-9950x-ubuntu-24-04)
• CircleCI macro runners, which already run on the x86 machines
• CPU simulation and walltime benchmarks on standard CI runners

Failed jobs during the outage are not billed.

What you can do now

Nothing to change on your side yet.

We were already planning to move everyone to our x86 macro runners, so this outage just brings that migration forward. We're giving every organization access to them and increasing the runner pool capacity to handle the additional workloads. Once it's live for you, we'll update this entry and email impacted teams with the new runner label to switch to. The x86 runners are a different machine, so the first run on the new label will start a new baseline.

---

Questions in the meantime: reach out on our Discord or at support@codspeed.io.

We're sorry for the inconvenience, and thanks for your patience while we sort this out.