Delays and intermittent failures running Smarter Testing
Smarter Testing had delays and intermittent failures that affected Docker, Machine, macOS, and Windows jobs. CircleCI reports that the incident is resolved and that the outage lasted 2 hours and 48 minutes.
State
Resolved
Started
Lasted
2 h 48 min
Worst impact
Degraded
Timeline
11 updatesInvestigating
32 min 19%
Identified
2 h 6 min 75%
Monitoring
10 min 6%
Updates
Times in UTCAs posted by CircleCI
Smarter Testing functionality is restored. We appreciate your patience as we worked through this.
The maintenance was successful. Smarter Testing functionality has been restored. We are monitoring to ensure performance remains stable.
At 18:45 UTC, we will perform emergency maintenance, which is expected to take a few minutes. During this window, test jobs for customers using Smarter Testing may be delayed or fail. Thank you for your patience while our engineers work to resolve this. We will provide another update by 19:05 UTC.
The maintenance was successful. Smarter Testing functionality has been restored. We are monitoring to ensure performance remains stable.
At 18:45 UTC, we will perform emergency maintenance, which is expected to take a few minutes. During this window, test jobs for customers using Smarter Testing may be delayed or fail. Thank you for your patience while our engineers work to resolve this. We will provide another update by 19:05 UTC.
Since 17:55 UTC, test jobs for customers using Smarter Testing have been running again. Dynamic Test Splitting is still not running optimally. Dynamic Parallelism is also not running optimally, so jobs that use it should be expected to fall back to using all nodes. Thank you for your patience while our engineers work to resolve this. We will provide another update by 18:50 UTC
Since 17:55 UTC, test jobs for customers using Smarter Testing have been running again. Dynamic Test Splitting is still not running optimally. Dynamic Parallelism is also not running optimally, so jobs that use it should be expected to fall back to using all nodes. Thank you for your patience while our engineers work to resolve this. We will provide another update by 18:30 UTC.
Since 17:38 UTC, some test jobs for customers using Smarter Testing have been failing. Thank you for your patience while our engineers work to resolve this.
Since 17:09 UTC, we have been seeing delays in updating test impact analysis data. Test selection may be less precise, which may cause more tests than necessary to run. Thank you for your patience while our engineers work to resolve this.
Starting at 16:38 UTC, test jobs for customers using Smarter Testing should be back running. Dynamic Test Splitting may still not be working optimally for some customers.
Some Smarter Testing customers may not be able to run tests. We are also seeing delays updating the impact analysis data map, which may cause more tests to be selected by Smarter Testing.
Affected components
4CircleCI in the last 90 days
Full historyIncidents in 90 days
39
Days with an incident
28
Median duration
1 h 13 min
This incident
2.3× the median
Other CircleCI incidents
All incidentsCircleCI·Minor Service Outage
CircleCI reports degraded service on api.anthropic.com. CircleCI reports that the incident is resolved and that it lasted 3 minutes.
CircleCI·Minor Service Outage
The Anthropic api.anthropic.com component had degraded performance. CircleCI reports that the incident is resolved and lasted 24 minutes.
CircleCI·Partially Degraded Service
CircleCI reports a partially degraded service that affects GitHub Pull Requests. CircleCI resolved this incident. It lasted 4 hours and 6 minutes.
CircleCI·Partially Degraded Service
CircleCI reported degraded service for GitHub Pull Requests. CircleCI resolved the issue. The outage lasted 3 minutes.
CircleCI·Minor Service Outage
CircleCI reports degraded service on Anthropic api.anthropic.com. CircleCI resolved the incident after 75 minutes.
Follow CircleCI
Your coding agent knows when CircleCI is down, and tells you when a failure is theirs, not yours. You can also get CircleCI incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "circleci" and tell me if CircleCI has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.live/feed.xml?providers=circleci/feed subscribe https://outages.live/feed.xml?providers=circleciFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane