Operational CircleCI status
circleci.com · Official status page (Statuspage-compatible JSON)
FROM ALL SOURCES
CircleCI looks fine itself, but Amazon Web Services, a provider it may run on (inferred), reports major outage. Watch for knock-on effects.
confidence: low Vendor: operational · users: normal · routing: no data · upstream providers: major.
- Vendor status page Operational · 1 open incident
- User reports 0 in 15 min vs ~0 typical
- Routing / BGP no ASN mapped, so no routing view
- News & network weather no recent mentions
- Providers it may run on (inferred) Amazon Web Services: Major outage
- CISA KEV (context) no recent entries for this vendor
Regions mentioned: Docker Jobs, Machine Jobs, macOS Jobs
| Clock | Started | Running |
|---|---|---|
| Vendor clock when the vendor's open incident started | 19 h 16 min | |
| Crowd clock when user reports began rising above normal | not seen | n/a |
| Network clock when routing anomaly data first flagged it | not seen | n/a |
| ORBIT clock when our checker first recorded the change | not seen | n/a |
Evidence
- Official page: Operational (“All Systems Operational”). evidence confidence: high
- Vendor stage: resolved on “Delays and intermittent failures running Smarter Testing”. evidence confidence: high
- User reports are within normal range (0 in 15 min). evidence confidence: low
- Amazon Web Services reports an issue. CircleCI may depend on it (inferred from public sources). Coincidence, not causation. evidence confidence: low
What we don't know: what is happening inside CircleCI's own systems, how many users are actually affected (reports are self-selected and unverified), and anything from routing / bgp. Routing data shows reachability, not whether the app works.
Coincidence, not causation: signals that overlap in time are shown side by side, not as proof of cause.
Automated analysis by Cloudy_Day NetWeather; not a personal statement. Generated .
Cloudy_Day's take
Stage vs. health
The vendor's stage is “resolved”. Stage tells you where they are in their process; health is what users experience. Right now vendor: operational · users: normal · routing: no data · upstream providers: major. Vendor status and outside signals roughly agree.
Who depends on whom
CircleCI may run on Amazon Web Services, Google Cloud (inferred). We don't map other services that depend on CircleCI. Dependency chains are where single points of failure hide.
Identity & trust lens
Even without an identity system involved, outages push people toward workarounds: password resets, unofficial apps and “status” links in DMs. Each one is a trust decision. Use official channels.
For users
Check the official status page before changing settings or reinstalling. If you must act, use known-good bookmarks. Reporting what's broken on ORBIT helps everyone see the real footprint.
For security teams
Treat this as an availability event unless an official source says otherwise. Check which of your systems sit on CircleCI or its upstream providers, watch for outage-themed phishing aimed at your users, and log what you see with timestamps (all four clocks).
What to watch next
The vendor stage moving to “monitoring”, then “resolved”; the user-report curve falling back under baseline; and whether dependents start reporting issues.
Automated analysis by Cloudy_Day NetWeather; not a personal statement. Independent researcher; not affiliated with CircleCI. No blame or attack claims without an official source. Generated .
INCIDENT REPLAY
Delays and intermittent failures running Smarter Testing
minor resolved · started · resolved
9 updates
- investigating
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.
- identified
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.
- identified
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.
- identified
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.
- identified
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.
- identified
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
- identified
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.
- monitoring
The maintenance was successful. Smarter Testing functionality has been restored. We are monitoring to ensure performance remains stable.
- resolved
Smarter Testing functionality is restored. We appreciate your patience as we worked through this.
Community comments (0)
Comments are opinions of visitors, not statements by Cloudy_Day. Every comment is held for review before it appears. Links are removed, and personal data is redacted. Community guidelines.
No approved comments yet.
How to read this: official status comes from each provider's own public status page. User reports are unverified visitor reports. Things that happen at the same time are coincidence, not causation. Cloudy_Day is independent and not an official status source for any company listed.