Is Antigravity down?
How to check Antigravity's status properly
There is no status.antigravity page. Antigravity runs on Gemini models, so Gemini/Vertex incidents on Google Cloud's status feed are the closest official signal — that's what the live panel shows.
An Antigravity failure with no Gemini incident listed usually means a client-side issue: the IDE build, your auth, or the model quota on your account.
Is it down, or is it just you?
A 401 or 403 error is almost always your own auth — an expired token or a session that needs re-login, not an outage. A run of 5xx errors, or a 529 "overloaded" response, during an incident that's actually listed on the vendor's status page is on them, not you.
Before you conclude it's a real outage: try a second surface (the web app instead of the CLI, or vice versa), rule out your own network or VPN, and only then treat the vendor's official status page as the final word.
What to do while Antigravity is down
- Rate-limit messages on the free tier are quota, not an outage — Antigravity's free limits are tight and reset over time.
- Antigravity supports Claude models as well as Gemini — during a Gemini incident, switching the model inside Antigravity is the fastest fix.
- Check the in-app changelog/known-issues note: preview-stage IDE bugs can mimic outages after an update.
Frequently asked questions
Does Antigravity have an official status page?
No. Google doesn't publish a dedicated Antigravity status page. The nearest official signal is Google Cloud's incident feed filtered to Gemini/Vertex — which is exactly what the live panel above shows, read directly in your browser.
Why is Antigravity failing if no incident is listed?
With no Gemini incident on Google's feed, the usual culprits are local: free-tier rate limits (they're tight), a stale IDE build after an update, or account auth. Switching the model inside Antigravity is a quick way to isolate the layer.