Resolved -
Customers running jobs that pulled dependencies from Maven Central experienced elevated 429 (rate limit) errors. We have worked with Sonatype to allow list CircleCI's dedicated IP ranges. Customers using our IP ranges feature should no longer see Maven Central rate limits affect their jobs while we continue work to fully address the issue for all customers.
Customers whose jobs failed during this window may rerun affected jobs. We thank you for your patience while our team worked on implementing a fix.
May 14, 19:38 UTC
Monitoring -
We're monitoring to verify that rate limited jobs are recovering.
May 14, 18:08 UTC
Investigating -
Jobs pulling dependencies from maven central are experiencing increased 429 errors due to maven central rate limits.
We are investigating the issue and working to identify mitigations for customer jobs.
May 14, 16:49 UTC
Completed -
The scheduled maintenance has been completed.
May 7, 01:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 7, 00:00 UTC
Scheduled -
On May 7th between 00:00 UTC and 01:00 UTC, we will be performing scheduled maintenance that may briefly affect OIDC token minting. Customers with jobs that rely on OIDC tokens may experience token failures during a short period within this window.
May 6, 01:56 UTC
Resolved -
This incident has been resolved.
May 6, 21:26 UTC
Update -
We are continuing to monitor for any further issues.
May 6, 17:54 UTC
Monitoring -
GitHub is reporting a major incident for degraded pull request availability. This does not impact running CircleCI builds for newly created pull requests or push events.
May 6, 17:54 UTC
Resolved -
This incident is resolved. Thank you for your patience, and we apologize for any inconvenience.
May 6, 20:13 UTC
Monitoring -
The rollback was successful. Pipelines are flowing normally again. Monitoring for a bit.
May 6, 20:03 UTC
Update -
We are continuing to investigate this issue.
May 6, 19:43 UTC
Investigating -
We are having an issue with some pipelines being lost. We are rolling back the affected service, and will share more information when we have it.
May 6, 19:42 UTC