Hi,
I am building an app for an event that relies on gemini-3-pro-image-preview and I keep getting error code 429.gemini-2.5-flash-image seems to be working fine so far instead for some reason.
I have recently migrated the project from a Google AI Studio API key to Vertex AI. Is there something I’m missing in the Cloud console perhaps?
Did you solve it? Because im getting this eror also. But i dont know how solve it
Hi. I think it must have been an issue on their end rather than my setup. I say that because eventually it started working again automatically by itself.
All I can say is that regardless I ended up switching back to an AI studio API key because Vertex AI seems much slower and also error prone compared to it. Like seriously a massive difference. I also don’t think I ever got that error with the AI studio.
It’s just the Vertex AI API that seems to be unsuccessful relatively often and returning that error
Same thing. They started returning a lot of 429’s - way more than in the past, even though i stopped making concurrent requests etc.
Hi all, Apologies that you are seeing so many 429s for the Gemini 3 Pro Image models. The errors are transient and indicate severe spikes in traffic, we are looking to address these issues asap
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?
Same here massive spike in 429s for gemini-3-pro-image-preview
Likewise, huge spikes in 429s happened suddenly, starting ~1/22, both on gemini-3-pro-image-preview and gemini-2.5-flash-image. It’s essentially unusable for us as it currently stands and our product team is trying to figure out replacement vendors.
Have there been any changes in load balancing logic or account quotas?
I have to admit I’m pretty frustrated that availability is this poor in a commercial offering, and it needs to be documented better if this is the true expectations for dynamic shared quota.