gcc git 429 Too Many Requests nginx

← All discussions

Project / Subsystem

gcc / gcc

Date

2026-08-24

Proposer

Jonathan Grant <jgrantonline@gmail.com>

Source type

public_inbox

Consensus

Proposed

Sentiment

7/10

Technical tradeoffs

• Implementing rate limiting to protect infrastructure versus potentially blocking legitimate users.
• Identifying the source of excessive traffic (e.g., scrapers) versus addressing the symptom (rate limiting).

View thread →

All attributes

project: gcc
subsystem: gcc
patch_id: —
discussion_id: 7fd28b9d-856f-4d62-b2bb-7ca028b4a968@gmail.com
source_type: public_inbox
title: gcc git 429 Too Many Requests nginx
headline: Experiencing 429 Too Many Requests errors on GCC Git web interface
tldr: Users are encountering '429 Too Many Requests' errors when accessing the GCC Git web interface, indicating rate limiting is in effect.
proposer: Jonathan Grant <jgrantonline@gmail.com>
consensus: Proposed
outcome: proposed
sentiment_score: 7
technical_tradeoffs: • Implementing rate limiting to protect infrastructure versus potentially blocking legitimate users.
• Identifying the source of excessive traffic (e.g., scrapers) versus addressing the symptom (rate limiting).
series_id: —
series_role: standalone
series_parts: []
tags: • infrastructure
• rate limiting
• Git
• nginx
• access issues
url: https://inbox.sourceware.org/gcc/7fd28b9d-856f-4d62-b2bb-7ca028b4a968@gmail.com
bugzilla_url: —
date: 2026-08-24T00:00:00.000Z

gcc git 429 Too Many Requests nginx

Jonathan Grant reports experiencing persistent ‘429 Too Many Requests’ errors from nginx when trying to access the GCC Git web pages and specific commit diffs. This issue has been ongoing for several days, suggesting a problem with rate limiting on the server. Other users confirm facing similar blocking issues.