What happened: Customers running jobs that pulled dependencies from Maven Central experienced elevated HTTP 429 (rate limit) errors due to newly enforced rate limits from Sonatype/Maven Central.
What we did: We worked with Sonatype to allowlist CircleCI’s dedicated IP ranges. Customers using our IP Ranges feature should no longer see Maven Central rate limits affecting their jobs. We are continuing work to fully address the issue for all customers.
What you should do: If your jobs failed during this window, you can safely rerun them. No configuration changes are required at this time.