Cloud builds are failing with 429 Too Many Requests error while downloading artifacts from central sonatype registry.

What to do

• Check whether you use Harness Continuous Integration Enterprise(CIE) - Windows Cloud Builds, Continuous Integration Enterprise(CIE) - Windows Cloud Builds, Continuous Integration Enterprise(CIE) - Linux Cloud Builds, Continuous Integration Enterprise(CIE) - Windows Cloud Builds and 4 more in us, us-central1, us-east5, us-west1. 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 3h 31m it lasted.

  Anything that failed between 2026-06-17 13:42 UTC and 2026-06-17 17:13 UTC may need a replay.

• Subscribe to Harness's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=harness works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Harness 6

1. investigatingJun 17, 2026, 1:42 PM UTC

   We are investigating an issue affecting artifact downloads from Maven Central following recent rate-limiting changes implemented by Sonatype. Sonatype has recently implemented rate limits and builds downloading artifacts from central sonatype  https://central.sonatype.org/faq/429-contact-support/. Customers downloading artifacts would be impacted.  We are actively engaging with Sonatype to mitigate the issue here.

   provider

2. identifiedJun 17, 2026, 2:03 PM UTC

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

   provider

3. monitoringJun 17, 2026, 2:21 PM UTC

   A fix has been implemented and we are monitoring the results.

   provider

4. monitoringJun 17, 2026, 3:21 PM UTC

   Maven Central is rate-limiting requests originating from our us-central1 NAT egress IP. Other regions (us-west1, us-east5) are not affected. The Maven/Sonatype team has been engaged and is actively working on lifting the rate limit for our IP range.

   provider

5. monitoringJun 17, 2026, 4:12 PM UTC

   We are continuing to monitor for any further issues.

   provider

6. resolvedJun 17, 2026, 5:13 PM UTC

   This incident has been resolved.

   provider

Corrections

None so far.

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