I am creating this thread to bring this to the attention of the Google development team and to see if anyone else is affected. Today, June 18, I encountered a critical issue with the Google AI Studio web interface.
The Core Issue:
Despite having an active Pro subscription, the system completely blocks generation. Immediately after sending the very first prompt, a message appears stating that the limits are exhausted (error 429 RESOURCE_EXHAUSTED).
Important Details:
Until today (June 18), everything worked absolutely perfectly, and there was no quota overage on my end.
The error occurs on the very first message, meaning the actual usage is zero.
Switching accounts does not solve the problem; the glitch persists everywhere.
Standard methods like clearing the browser cache and logging in again do not help.
The system behaves as if my account suddenly lost its Pro status and received a zero limit for advanced models. It looks like a global billing synchronization bug on the platform’s backend that coincided with today’s technical updates.
To the Google Team:
Please investigate this incident. Because of this error, the workflow is completely paralyzed, and testing prompts is impossible.
Fellow forum members, has anyone else caught this same block today? I would be very grateful if someone could share a working workaround for this problem while we wait for an official patch.
same here!! honestly I cannot afford for AI Studio to be down and there is no way to even contact Google support (they have the worst customer service yet amazing products). I need reassurances that the quota exceeded limit error is just temporary.
Yes, I have 3 Google AI Pro subscriptions and experienced the identical issue you described today. It’s like I’ve lost my 3 best software engineers–and now my Google AI Pro subscriptions (for my purposes) are essentially useless. I love my workflow. Please fix this.
Now, its seems it’s working again here on my end. I’ve tried 2 image generations and it’s back to normal, apparently. I think you guys should give it a try.
Indeed, mine has also returned to its normal state; I posited my query within my six-hundred-thousand-token conversation, and it responded with effortless ease.