Was Google AI Studio really able to return to normal operation?
I can’t believe it.
That’s really a nightmare now!
Nope, not operational at all. Don’t believe that status bar for a second; it’s a total joke. Ever since they started migrating from Google Drive to the new system, everything has been completely messed up. You can’t even get anything done on AI Studio anymore. And they should’ve never moved it in the first place—it’s a total disaster that’s ruined the whole workflow.
Thanks for getting back to me.
As you say, it’s unreliable.
In my case, I asked a simple question to the Code Assistant of an application in the Build menu in Google AI Studio, and the app became unusable. The application was working fine just before I asked the question. Then, after I casually wrote one word, it became unusable.
Although it was for personal purposes, it was an application that did a really great job, so I’m really sad that it no longer works.
Yes you right! paid for Tier 1 every time i send a new line of code i get the quote exceed issue! cant do anything. Sometimes with the FREE tair it works but not great very slow respond. its now for more then 7 days in row this issue hope that AI studio will fix it soon.
I I’ve heard of people trying to use incognito mode or adding an API key in the settings, but I’m pretty sure those are just temporary band-aids. It might work for a few seconds, but then it goes right back to those quota errors. They’ve ruined a perfectly good tool; ever since the update moving away from the cloud, it’s just gone downhill
It doesn’t work to add a new API key or incognito mode. I’ve been trying for days, still getting quota exceeded errors. Does not matter if its my first chat of the day with the ai app bot or what. I wish there was more information as to status, progress, restoration estimation!
Here too, on paid or free tier getting this error… ![]()
It’s not working. I get an internal error in the chat window of ai studio. Where is Google in this? How are they communicating? They don’t take this seriously – so we can’t take it as a serious route to build and deploy either.
I spent over 12 hours today talking and testing with Code Assistant. It turns out that in my case, Google’s infrastructure (proxy/routing) was broken in a specific app container. This caused the app to time out when launched. However, apps created before the problem occurred worked fine. I hope Google’s admins are aware of this.
I suspect—and this is just a guess—that Gemini’s recent troubles were caused by a collaboration between humans and AI, resulting in errors in the network definition here and there, or in poor performance settings.
The reason I think this is because, while analyzing the problem I was having with Code Assistant, I noticed that Code Assistant itself could change the network definition.
Changing the network configuration of a massive system is impossible for humans alone. Therefore, a certain percentage of the network configuration changes were handled by the AI.
If a human had verified these changes, they could have been corrected. However, perhaps this verification was insufficient because it took too much time.
This is just my imagination. I don’t need to know whether this is true, but I hope the system will be restored quickly.