Skip to main content
CircleCI

Usage API data delayed for 5/28

Degraded Lasted 3h 19m · started · CircleCI's page

Level
confirmed
Worst impact
Degraded
Components
CircleCI API
Down Index
21of 100

What to do

  • Check whether you use CircleCI CircleCI API. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 3h 19m it lasted.

    Anything that failed between 2026-05-29 14:51 UTC and 2026-05-29 18:10 UTC may need a replay.
  • Subscribe to CircleCI's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=circleci works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from CircleCI 3

  1. investigating

    We are currently investigating this issue.

    provider

  2. investigating

    We've identified a small number of duplicate records in the Usage API data. Data is available, but may be inaccurate. We continue to investigate.

    provider

  3. resolved

    The Usage API incident has been resolved.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-05212f5b62

Is CircleCI still down?

No, this incident was resolved 2026-05-29 18:10 UTC. For CircleCI's live state, see https://down.guide/circleci.

How long did it last?

3h 19m, from 2026-05-29 14:51 UTC to 2026-05-29 18:10 UTC, by the times CircleCI posted.

What was affected?

CircleCI named CircleCI API.

What caused it?

CircleCI hasn't published a root cause. If it does, it shows here.

Where does this come from?

CircleCI's official status page, https://status.circleci.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.