On 24/08/2026 13:31, Mark Wielaard wrote:
> Hi Jonathan,
>
> On Mon, 2026-08-24 at 12:48 +0100, Jonathan Grant via Gcc wrote:
>> Anyone else getting 429 error on the gcc git web page?
>>
>> I've been seeing this for a few days on:
>>
>> https://gcc.gnu.org/git/?p=gcc.git;a=summary
>>
>> 429 Too Many Requests
>> nginx
>>
>> It did load today, so I clicked the top link diff and got the 429 error on:
>> https://gcc.gnu.org/git?p=gcc.git;a=commitdiff;h=c8e065ed391115f763af09004f593a3db1fa5514
>
> Sadly yes. The AI scraperbots are again in full force using residential
> proxies. An nginx limiter was put in front of gcc.gnu.org https to
> fight them off. But innocent bystanders get hit by the mitigation too.
> One way to get around the limiter is login to bugzilla or use ssh
> (assuming you have an account on the system). That should mark your ip
> address to bypass the limiter.
I can't login to bugzilla due to the same 429. Maybe it will let me in later
and whitelist me.
Thank you again for the suggestions and alternatives
Jonathan
>
> The other is to use a non-https protocol like git:// for cloning or use
> the forge mirror git clone https://forge.sourceware.org/gcc/gcc or the
> sourcehut one git clone https://git.sr.ht/~sourceware/gcc
>
> Sorry for the inconvenience.
>
> Cheers,
>
> Mark
