I am a Google AI Studio user. When using the Gemini 3.1 Pro Preview model, I encountered severe rate limits (You’ve reached your rate limit. Please try again later.), so I subscribed to Google AI Pro.
However, despite subscribing to Google AI Pro, there is no difference in how I use Google AI Studio. The Gemini 3.1 Pro Preview model usage remains the same, and I cannot sync the Nano Banana Pro model.
What could be the problem? Please help me, thank you.
Note: Google officially states that subscribing to Google AI Pro is valid for use in Google AI Studio, as shown in the screenshot.
Hello @FelixJi ,
This forum is primarily dedicated to discussions regarding the Gemini API and Google AI Studio. For issues related to Google AI subscriptions, we recommend visiting Google One Help, as they will be better equipped to assist you.
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.
