CircleCI reported this minor-impact incident on its official status page on May 14, 2026, 16:49 UTC. It was resolved after 2h 50m.
Right now CircleCI is operational. Live CircleCI status →
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.
We're monitoring to verify that rate limited jobs are recovering.
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.
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.
Overlapping incidents aren't necessarily related.
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