CircleCI incident: Delays in Workflow and Job data in the Usage API

Affected components

• CircleCI API

1. resolvedApr 8, 2026, 20:33 UTC

   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.

2. identifiedApr 8, 2026, 13:20 UTC

   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 APIStatus.watch saw

Our 5-minute checks didn't record a change in CircleCI's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• Confluent Cloud: Elevated error rates in AWS me-south-1 and me-central-1 regionsMajor · Apr 1, 2026, 19:52 UTC
• Render: Disruption affecting the provisioning of new instances in Singapore and partially in OregonMajor · Apr 8, 2026, 09:57 UTC
• ReadMe: Discussion posts throwing 500 errorsMajor · Apr 8, 2026, 18:11 UTC
• Intercom: Email Forwarding is experiencing difficultiesMajor · Apr 8, 2026, 18:22 UTC

How often does CircleCI have incidents?

CircleCI reported 22 incidents in the last 90 days, 1 of them major or critical. A typical incident lasted 1h 38m. See CircleCI's uptime and incident history