Persistent 429 errors on Gemini 2.0 Flash (~1 month)

I’ve been getting 429 errors on Gemini 2.0 Flash for close to a month. My usage is very low and nowhere near any quota limit. This doesn’t appear to be a rate issue on my end.

I’m aware the model is being deprecated after June 1st and migration is expected, but it’s hard to migrate smoothly when the current model is unreliable. Could someone investigate whether there’s a backend issue affecting certain accounts?

The timing here is the core problem. A deprecation notice is supposed to give developers a window to migrate cleanly — but if the model is broken during that window, the window doesn’t actually exist in practice.

My ask is straightforward: either fix the 429 issue before the cutoff, or extend access by at least 6 months. If neither happens, this deprecation notice is effectively void — developers aren’t getting a migration window, they’re getting a broken model with a deadline attached.