Chromium repositories 429

[Mike Aizatsky]

Happy Monday everyone,

We suddenly see a lot of 429s from chromium git repositories such as:

fatal: unable to access 'https://chromium.googlesource.com/chromium/src/third_party/abseil-cpp.git/': The requested URL returned error: 429

Are there any infrastructure problems? Any ideas if things will improve?

Thanks a lot for help.

[Eldar Pulatov]

Hello everybody, we can confirm this on our side as well.

Starting today, gclient / git ls-remote against multiple Chromium dependency repositories began failing with HTTP 429, so the issue likely affects Chromium third_party mirrors rather than a single repository.

[0:00:46] fatal: unable to access 'https://chromium.googlesource.com/chromium/src/third_party/freetype2.git/': The requested URL returned error: 429
[0:00:49] 

Plain host reachability still looks fine, which suggests this is specific to Git access for some Chromium dependency repos. At first I suspected rate limiting or some Googlesource Git access / captcha-related issue, but I reproduced the same behavior from several different IPs and the problem remains.

Could someone please check this issue?

This e-mail may contain CONFIDENTIAL AND PROPRIETARY INFORMATION and/or PRIVILEGED AND CONFIDENTIAL COMMUNICATION intended solely for the recipient and, therefore, may not be retransmitted to any party outside of the recipient’s organization without the prior written consent of the sender. If you have received this e-mail in error please notify the sender immediately by telephone or reply e-mail and destroy the original message without making a copy.

[Kevin Graney]

I also started seeing these failures around 11:00AM UTC on April 6 from gclient sync.  They have continued to fail as of 2 hours ago.

On Mon, Apr 6, 2026 at 6:25 PM 'Eldar Pulatov' via Chromium-dev <chromi...@chromium.org> wrote:

Hello everybody, we can confirm this on our side as well.

Starting today, gclient / git ls-remote against multiple Chromium dependency repositories began failing with HTTP 429, so the issue likely affects Chromium third_party mirrors rather than a single repository:

[0:00:46] fatal: unable to access 'https://chromium.googlesource.com/chromium/src/third_party/freetype2.git/': The requested URL returned error: 429
[0:00:49] 

Plain host reachability still looks fine, which suggests this is specific to Git access for some Chromium dependency repos. At first I suspected rate limiting or some Googlesource Git access / captcha-related issue, but I reproduced the same behavior from several different IPs and the problem remains. Could someone please re-check this issue?

On Monday, April 6, 2026 at 8:23:00 PM UTC+3 Mike Aizatsky wrote:

This e-mail may contain CONFIDENTIAL AND PROPRIETARY INFORMATION and/or PRIVILEGED AND CONFIDENTIAL COMMUNICATION intended solely for the recipient and, therefore, may not be retransmitted to any party outside of the recipient’s organization without the prior written consent of the sender. If you have received this e-mail in error please notify the sender immediately by telephone or reply e-mail and destroy the original message without making a copy.

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev...@chromium.org.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/bd2ed5a8-38d3-4a63-8cb1-dce48eea2618n%40chromium.org.

[Pratyush Mohanty]

Hello Mike,

HTTP 429 from chromium.googlesource.com indicates the service is refusing requests due to request-rate limiting or protective throttling. This can affect multiple Chromium dependency repositories at once and may persist for some time when a threshold is exceeded (often due to high parallelism or many builders sharing the same egress IP/NAT).

Immediate mitigations that typically reduce or eliminate 429s:

• Reduce concurrency for sync/fetch operations (especially in CI):
  

  gclient sync -j1

• Limit Git HTTP parallel requests on the client side:
  

  git config --global http.maxRequests 1

• Back off and retry rather than immediately re-running in tight loops (introduce a delay between retries, and avoid running many retries in parallel across hosts).
• If you have multiple machines behind the same public IP, consider staggering schedules (e.g., start times) or reducing simultaneous builders to avoid tripping shared-IP limits.

We will check whether there is an ongoing infrastructure-side issue affecting Gitiles/googlesource throttling and follow up. If this is an infra regression, improvement will require a service-side change; otherwise, the above mitigations should stabilize syncs.

Regards,
Pratyush Mohanty

Email sent via Mail Agent

[Eldar Pulatov]

Hello Pratyush,

I created a bug in Infra/SDK to track the problem: https://issues.chromium.org/issues/500042303

Thank you for the answer and suggested workarounds. However, in my case concurrency does not appear to be the main factor, because I can reproduce the issue from several different IPs even with a simple git ls-remote command, without running parallel gclient syncs.

Regards,

Eldar