Our servers are experiencing high traffic issue

every time it will shows ..i can’t use models .kindly help us.

issue: Our servers are experiencing high traffic right now, please try again in a minute.

take some coffee bro, all users can’t handle this rn , we just wait and wait

solat dulu lah minimal :v

i am using pro subscribe ..then how to use this..google please resolve this i am expiriencing this month starting to facing this kind of issue.

I’m facing the same problem frequently today, and it drains my entire balance.

:expressionless_face:…still not resolve this issue

ultra plan same!
It’s been going on for days now—has no one fixed it yet?

yes feel very bad ..not using this waste of time and spending money also

It is now gobbling up AI credits and continuing with Agent terminated due to error

```
Trajectory ID: d4e22d4b-93c6-41ea-a365-
Error: HTTP 503 Service Unavailable
Sherlog:
TraceID: 0x11a4f3ff7ba
Headers: {“Alt-Svc”:[“h3=“:443”; ma=2592000,h3-29=“:443”; ma=2592000”],“Content-Length”:[“429”],“Content-Type”:[“text/event-stream”],“Date”:[“Fri, 17 Apr 2026 05:54:19 GMT”],“Server”:[“ESF”],“Server-Timing”:[“gfet4t7; dur=2851”],“Vary”:[“Origin”,“X-Origin”,“Referer”],“X-Cloudaicompanion-Trace-Id”:[“11a4f3ff7ba2ff69”],“X-Content-Type-Options”:[“nosniff”],“X-Frame-Options”:[“SAMEORIGIN”],“X-Xss-Protection”:[“0”]}

{
“error”: {
“code”: 503,
“details”: [
{
@type”: “type.googleapis.com/google.rpc.ErrorInfo”,
“domain”: “cloudcode-pa.googleapis.com”,
“metadata”: {
“model”: “claude-opus-4-6-thinking”
},
“reason”: “MODEL_CAPACITY_EXHAUSTED”
}
],
“message”: “No capacity available for model claude-opus-4-6-thinking on the server”,
“status”: “UNAVAILABLE”
}
}
```

This is a server-side issue. The model capacity is exhausted (503 error), so the agent fails after consuming credits.

It’s really disturbing. I can do a proper workflow and it kills my Momentum. Please Google look into it and debug the problem.

Dear Antigravity team,

I believe I’ve found a 100% fix for the “Our servers are experiencing high traffic right now” issue. The solution is fairly straightforward and, judging by your current uptime, perfectly aligned with your existing DevOps practices.

Here’s what you need to do:

Take the Antigravity source code

Feed it into Gemini 3.1 with the prompt “fix skill issue”

And most importantly — kindly ask your developers to temporarily step away from their keyboards so they don’t break whatever the AI accidentally manages to fix :white_check_mark: