I am currently experiencing repeated 429 “Quota Exceeded” errors when calling the Gemini 2.5 Pro model, even though my account is on Tier 1 (Paid) and my actual usage is well under 1% of the available quota.
Details:
Model: gemini-2.5-pro
Billing Tier: Tier 1
RPM / TPM / RPD limits:
RPM: 150
TPM: 2,000,000
RPD: 10,000
Actual usage shown in the quota dashboard is far below any limit, typically under 1%.
I’m also experiencing this issue with the Gemini API using gemini-2.5-flash.
Everything was working fine yesterday with exactly the same setup, but today I consistently get a 429 “quota exceeded” error whenever my agent calls the API. I’m also on Tier 1 and my usage is nowhere near the documented limits according to the quota dashboard.
So it looks very similar to what others here are reporting:
Tier 1 account
Very low actual usage (+/- 1500 API requetst daily)
Only Gemini 2.5 models (in my case gemini-2.5-flash) are affected
Started suddenly, without any code changes on my side
It really feels like this might be an account- or model-level issue on Google’s side rather than a real quota problem.
If anyone can confirm whether there’s an ongoing incident with Gemini 2.5 (Pro/Flash) or share a workaround, that would be super helpful.
Same issue. And the funny thing is, this has been happening with the exact same task, tokens, prompts etc. I have been testing. So it’s impossible that I reached the quota since it was working a couple of days ago.
Thank you for bringing this to our attention. We truly appreciate you flagging this issue. To help us investigate and file a bug internally, could you please share the complete error log or JSON response?
Here is the complete JSON error response I receive immediately:
codeJSON
{
"error": {
"code": 429,
"message": "Resource has been exhausted (e.g. check quota).",
"status": "RESOURCE_EXHAUSTED"
}
}
CRITICAL CONTEXT:
The issue affects BOTH gemini-2.5-pro and gemini-2.5-flash.
Yesterday, my app was working perfectly using gemini-2.5-pro.
Suddenly, I started getting 429 errors on Pro. I switched my code to use gemini-2.5-flash (thinking it was a specific model quota issue) and optimized the code to be purely sequential (1 request at a time), but I still receive the same immediate 429 error on Flash.
If you read above moderator actually answered that they are aware. Doesn’t mean they actually do something to fix that. I believe this issue affects thousands of people.
Sad that especially Google with its server capacity cannot handle the rush. The problems exist everywhere at the moment, especially sad that paying customers are also affected. Perhaps it was not so smart to make so many major releases in such a short time.
It is happening for me daily on my account and it is losing us money since we are running a saas product over gemini, we need a quick fix, everything was going fine for the past couple of month until the day you released gemini 3 and nano banana