Comment
March 6, 21h here UTC time. Still not solved.
At the moment I’m getting maybe one response out of twenty attempts at best. I currently have six projects under development, all using paid APIs. I’ve tried pretty much everything I could think of: changing APIs, generating new API keys, opening the app in an incognito window, trying Safari instead of Chrome, clearing cache and cookies, refreshing, remixing the projects, toggling API switches… basically shaking the whole thing up in every possible way. Nothing seems to make a difference.
A couple of days after the problems appeared, it became pretty obvious that the issue is not on the user side but a platform breakage caused by the recent UI/product update. Well, there are both bad and good things about what’s happening.
As for the bad:
Breaking things during what looks like a major overhaul of an application is always a possibility. That’s part of software development. But when the company doing it is Google, you would normally expect a bit more anticipation around that risk. Something like staged deployment, fallback mechanisms, or at least a clear warning to users before pushing such a large change. From the outside it really doesn’t look like that level of caution was applied here.
Once the problem became obvious, the next thing users needed most was simply information. When a platform breaks, the first thing people want to know is what is happening and whether someone is actively working on it. A small communication effort could have gone a long way: acknowledging the issue, explaining the scope of the problem, giving some indication of recovery time. Instead, there seems to be very little official information about what exactly went wrong or what users should expect. That lack of communication probably contributes more to the frustration than the bug itself.
There is also a point where we, the users, have to be honest with ourselves. From the start, AI Studio has been presented as an experimental prototype builder rather than a fully mature production platform. People who attached production deadlines or customer commitments to it were essentially taking a gamble. When you work with experimental tools, part of the deal is that things may break in unpredictable ways. In that sense, the only thing we can reasonably complain about is being charged for services that are temporarily unusable, but beyond that the risks were somewhat implicit from the beginning.
Now the good:
One thing worth mentioning is that the recent update, despite all the problems it introduced, does seem to push the platform toward what looks like a significant upgrade. The new interface and system feel more oriented toward serious development. There are hints of better project organization, more structured workflows, and a general sense that the platform is trying to grow beyond a simple prototype playground. The intent looks promising — nobody goes through this kind of trouble for a product that is not intended to last or evolve further. If that direction continues and the stability issues are resolved, it could become a genuinely powerful environment for AI-assisted development.
In a way, the frustration people are expressing right now is also a sign that the platform has real potential. People are upset because they actually want this tool to work. If reliability and communication improve, AI Studio Builder could turn into something very significant.
Now, and this is aimed at the people at Google: AI Studio is a great product that’s becoming popular, but if it isn’t backed by active support very soon, users are going to lose trust in Google products. I’m personally very disappointed at how users were essentially thrown under the bus, with little regard for the amount of time spent learning — yes, learning — and adopting this tool.
At this point I honestly don’t know what to do. Should I turn to Antigravity? Firebase Studio? What guarantee do I have that after investing time and effort I won’t face the same outage again, with no warning?
I used to say that betting on big tech companies such as Google was safe because of how much is at stake for them in terms of reputation and credibility. But now I’m not so sure anymore. At this rate I almost expect my Gmail account to hang unexpectedly at any moment.
My best bet for now is probably to make projects as migration-friendly as possible and maintain regular backups.
If anyone from the AI Studio team happens to read this, a simple clarification would already help a lot: is the current issue related to a quota system change, a builder-side rate limit, or a platform migration problem linked to the recent update? Even a short status message or confirmation that the team is actively investigating would go a long way toward restoring confidence.
In the meantime, if other users have found temporary workarounds or have more information about the scope of the outage, it would be very useful to share.