Build1 publisher2 min readPublished
CircleCI's open preview runs GitHub Actions YAML on its own control plane
Third-party runners speed up Actions jobs while GitHub still dispatches them. CircleCI's preview takes orchestration too, for standard Linux environments, and claims 40 percent faster builds from sampling.
The Engineer · Build desk
What happened
- CircleCI opened a preview that runs existing GitHub Actions YAML directly on its own platform, selected as a config option when a project is set up.
- The company says sampling shows 40 percent faster builds and sub-30-second queue times even under the heaviest loads, with the Actions YAML teams already wrote.
- CircleCI counts 57 separate GitHub Actions outages between May 2025 and April 2026, which it calls the most frequently affected service on the platform.
- According to the post, a GitHub outage on August 17, 2026 ran close to eight hours and hit Actions alongside other core GitHub services.
- Runner services such as Blacksmith, Namespace and RunsOn keep existing workflows, but GitHub Actions still handles workflow events, queueing and job dispatch.
Compiled by The EngineerSomething wrong?How this is made
Why it matters
- decision Choosing a CI vendor now includes choosing which system receives the repository event and dispatches jobs, because that choice decides whether a GitHub incident stops deploys.
- constraint Mixed pipelines cannot move whole during the preview, so a team with Windows or macOS jobs runs two control planes and keeps its Actions dependency for part of the graph.
- exposure Teams that keep GitHub as both collaboration and delivery host lose code review and shipping in the same incident. CircleCI is selling against that concentration risk.
- cost Adoption work becomes auditing each workflow against CircleCI's supported-features list, with anything unsupported filed as a feature request in Canny.
A push lands, and something has to expand the YAML into queued jobs. Under the runner-swap model that something is GitHub: Actions receives the repository event, queues the work and dispatches the job, and the third-party service supplies only the machine that runs it [9]. Blacksmith sells managed runners for existing Actions workflows, Namespace sells alternative compute for Actions jobs, and RunsOn provisions ephemeral runners inside your own AWS account [8]. CircleCI's post states the consequence in one line: "When Actions is unavailable, the runner never receives the job" [10].
Self-hosted runners sit in the same position. You own provisioning, scaling, maintenance and security, and your exposure to an Actions outage is unchanged [11]. CircleCI's argument is that only moving orchestration as well as execution takes Actions out of the critical path, and it says a smaller set of platforms can run Actions workflows on their own infrastructure [12].
Those outage figures are CircleCI's own count. The window matters. The 57 span twelve months, from May 2025 through April 2026, an average of about 4.75 a month [15]. The sharpest data point in the post is dated later: on August 6, 2026, CircleCI says, 71 percent of workflow runs hit infrastructure failures at peak, with significant delays on many of the rest [6]. Both of the August 2026 incidents it describes fall after the period the 57 were counted in [16]. The post also says GitHub "has continued to struggle under load, at one point falling to zero nines of availability" [5].
A sampled 40 percent transfers only if your builds are bound by whatever bound the sample [3]. The post does not describe the workloads sampled or the compute on either side. The queue-time claim is the one you can test cheaply: your current wait is already sitting in your run history.
The file format is the portable part. I think CircleCI has that right: the YAML travels, and the dispatcher was the thing you were tied to. Whether switching is a config choice depends on the supported-features list. The preview covers standard Linux environments, and you select your GitHub Actions config during project setup [2]. Workflows that need Windows or macOS runners cannot move yet [17].
CircleCI also writes that newer platforms running GHA syntax independently are "still maturing and often lack the depth, scale, and delivery capabilities required for high-volume software delivery" [13]. Its own preview has to meet that standard now. The post points teams to the FAQ's supported-features list and asks for anything missing in Canny [14].
What to watch
- Whether the preview adds Windows and macOS environments, and which Actions features the FAQ list still excludes.
- Whether GitHub's own status history supports CircleCI's count of 57 Actions outages for May 2025 to April 2026.
- What running Actions YAML on CircleCI costs once the preview closes; the post only says sign-up is free.