Gemini-2.5-flash-image: Frequent 429 RESOURCE_EXHAUSTED during sequential image generation - seeking clarity on rate limits

[tylertreat]

I agree it seems odd. I found these other recent threads which appear to be related:

Urgent help with 429 gemini-3-pro-image-preview

I started seeing a massive spike in 429s for gemini-2.5-flash-image as well, much more than typical. It started happening a few days ago and now I get these errors consistently. Did something change?

Sudden Spike in 429 Errors with Gemini 2.5 via Vertex AI Global Endpoint

I started seeing a spike in 429s as well with gemini-2.5-flash-image. It sure seems like something changed on Google’s side. The API has become nearly unusable due to the volume of 429s. Does not seem like normal DSQ behavior as I see the same error rate consistently every day for the last few days now.