Elevated 429 errors pulling from maven central

What to do

• Check whether you use CircleCI Docker Jobs, Machine Jobs, macOS Jobs. 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 2h 50m it lasted.

  Anything that failed between 2026-05-14 16:49 UTC and 2026-05-14 19:38 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. investigatingMay 14, 2026, 4:49 PM UTC

   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.

   provider

2. monitoringMay 14, 2026, 6:08 PM UTC

   We're monitoring to verify that rate limited jobs are recovering.

   provider

3. resolvedMay 14, 2026, 7:38 PM UTC

   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.

   provider

Corrections

None so far.

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