CircleCI

The Usage API issue has been resolved. All data is now current. Appreciate your patience.

The Usage API issue has been identified and a fix is being implemented. We expect to the issue be resolved within a few hours.

Usage API data is delayed this morning. Team is investigating.

The Usage API incident is resolved on an ongoing basis. There was a 4-hour period yesterday 4/7 for which we did not capture RAM and CPU utilization in our logs. We will not be backfilling the data for that period. Appreciate your patience.

We have identified an issue causing Insights workflow and job data to be delayed when requested through the Usage API. Some data for the last 24 hours may not be fully reflected while we work to process the backlog of events. Insights UI is not impacted by this issue. Thank you for your patience.

**What happened** All modals and dialogs across the CircleCI application became invisible. They were being rendered correctly in the background, but were not visible to users. This affected approval jobs, SSH key management, and other settings pages across the app. **Root cause** The issue was introduced by an upgrade to our internal design system library. The new version added animation support to modal components using a library called Framer Motion. These animations are designed to fade modals in from invisible \(`opacity: 0`\) to visible \(`opacity: 1`\) when opened. However, the animation logic reads open/close state from a specific React context that is only available when modals are opened via a particular component \(`DialogTrigger`\). Our application manages modal state differently, passing open/close state directly via props, so that context was never populated. As a result, every modal in the app was permanently stuck in the "hidden" animation state and never transitioned to visible. **Resolution** We reverted the design system upgrade to restore the previous working version, which resolved the issue immediately. We are now working on a follow-up fix that will upgrade Framer Motion properly, by ensuring all modal components receive the required context. **Impact** The issue affected all modal dialogs across project settings, org settings, user settings, plans & payments, and other areas of the app for the duration of the incident. No data was lost or corrupted. The underlying functionality was intact, just inaccessible via the UI.

This incident has been resolved.

A fix has been implemented and we are monitoring the results. Thank you for your patience.

We are currently investigating an issue in the CircleCI UI impacting approval jobs and SSH key navigation. This is an interface-only issue and builds continue to flow as usual.

The Usage API issue affecting 4/1 data has been resolved. Updated data will be available on 4/3. Thank you for your patience.

The Usage API issue has been identified and the fix is being implemented.

We are currently investigating this issue.

It appears that GitHub's `GET /repos/{owner}/{repo}/commits` API is now stable and responsive.

GitHub's `GET /repos/{owner}/{repo}/commits` API has appeared to recover. We will continue to monitor this.

We are continuing to see very high error rates from GitHub's `GET /repos/{owner}/{repo}/commits` API.

Some pipelines may not trigger due to a high rate of API failures on one of GitHub's API endpoints. This includes some manually-triggered pipelines, some OAuth hooks and some scheduled pipelines.