Resolved -
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.
Apr 8, 20:33 UTC
Identified -
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.
Apr 8, 13:20 UTC
Resolved -
This incident has been resolved.
Apr 6, 21:12 UTC
Monitoring -
A fix has been implemented and we are monitoring the results. Thank you for your patience.
Apr 6, 20:43 UTC
Investigating -
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.
Apr 6, 20:33 UTC
Resolved -
The Usage API issue affecting 4/1 data has been resolved. Updated data will be available on 4/3. Thank you for your patience.
Apr 3, 02:18 UTC
Identified -
The Usage API issue has been identified and the fix is being implemented.
Apr 2, 21:23 UTC
Investigating -
We are currently investigating this issue.
Apr 2, 19:19 UTC
Resolved -
It appears that GitHub's `GET /repos/{owner}/{repo}/commits` API is now stable and responsive.
Apr 1, 12:23 UTC
Monitoring -
GitHub's `GET /repos/{owner}/{repo}/commits` API has appeared to recover. We will continue to monitor this.
Apr 1, 12:12 UTC
Identified -
We are continuing to see very high error rates from GitHub's `GET /repos/{owner}/{repo}/commits` API.
Apr 1, 11:58 UTC
Investigating -
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.
Apr 1, 11:55 UTC