CircleCI Status

Resolved: Thank you for your patience. This incident has been resolved.

Identified: The issue has been identified and a fix is being implemented.

Investigating: We are currently investigating an incorrect response from the v1 Job Retry API. While it correctly retries the job, it returns a 503.

Resolved: The issue affecting m2pro resource classes has now been resolved. We thank you for your patience and understanding as our engineering team worked to resolve this issue.

Identified: We are continuing to experience some delays starting macOS jobs on m2pro.medium and m2pro.large resource classes. We suggest customers to move to m4pro.medium or m4pro.large to mitigate queue time.

Identified: We are continuing to experience delays starting macOS jobs on m2pro.medium and m2pro.large resource classes. We suggest customers to move to m4pro.medium or m4pro.large to mitigate queue time.

Identified: We are currently experiencing delays starting macOS jobs on m2pro.medium and m2pro.large resource classes. We suggest customers to move to m4pro.medium or m4pro.large to mitigate queue time.

Identified: We are currently experiencing delays starting macOS jobs on m2pro.large resource class. We thank you for your patience while our engineers work through this issue.

Resolved: Rates of 429 errors are back within normal ranges. This issue has now been resolved.

Monitoring: We have pushed another change which further mitigates the rate limiting. Customers should be able to use the API as normal now. We will continue to monitor the rate of 429s for any changes.

Identified: We have pushed a change that should reduce the frequency of these rate limits. We are continuing to investigate and will continue work to reduce this impact further.

Identified: Following the scheduled maintenance, we are seeing a reduction in rate limits and an increase in 429 errors. Customers are currently able to make API requests less frequently than expected.

Resolved: This incident has been resolved.

Monitoring: The maintenance has completed and we are monitoring the results. Thank you for your patience.

Identified: The APIs for managing personal access tokens (PATs) are still unavailable following a scheduled maintenance. Customers are able to view existing PATs in user settings but not add or delete tokens.