[BUG] Persistent HTTP 500 ESF Error - All requests failing since weekend outage (Europe-West, France)

[Florent]

Hi,

I’ve been experiencing a persistent HTTP 500 Internal Server Error in Antigravity since the weekend outage (March 28-29, 2026). Despite the incident being marked as resolved on the status page, I am still completely blocked.

**TraceIDs collected today (March 31, 2026):**

- 0xf4bc05 (10:58 AM Paris time)

- 0x355c7a (01:00 PM Paris time)

- 0xedb7cc (02:31 PM Paris time)

**What I tried:**

1. Revoked Google OAuth and re-authenticated

2. Deleted local auth cache (~/.gemini/ credentials)

3. Restarted the app multiple times

4. Tested with multiple Google accounts — all blocked the same way

**Error details:**

- Endpoint: cloudaicompanion.googleapis.com

- Error: HTTP 500 Internal Server Error (ESF layer)

- Location: Europe-West / France

- All accounts affected — appears to be a project/subscription-level issue

**Environment:**

- OS: Windows 10 Pro

- Antigravity version: latest

- Region: France (Europe-West)

The issue started during the weekend outage (March 28-29) and has persisted ever since, even though the status page shows the incident as resolved. I cannot use Antigravity at all.

Could a Google engineer check the TraceIDs above to identify what is happening server-side?

Thank you.

[Thatipamula_Namratha]

Hello @Florent ,

Welcome to AI Forum!

Thanks for addressing this issue and for providing those specific TraceIDs. We’re sorry for the inconvenience caused by this persistent error.

I have shared your report and the TraceIDs with our internal engineering team to investigate why your connection is still failing following the weekend outage in the Europe-West region.

We appreciate your patience as we look into this. Please let us know if you notice any changes in the error message.

[Florent]

Thanks a lot ! Unfortunatly still no changes to this day. Thanks for the rapid reply.

Trajectory ID: 3236ab03-97df-49b9-
Error: HTTP 500 Internal Server Error
Sherlog:
TraceID: 0xcbe230fd
Headers: {“Alt-Svc”:[“h3=“:443”; ma=2592000,h3-29=“:443”; ma=2592000”],“Content-Length”:[“109”],“Content-Type”:[“text/event-stream”],“Date”:[“Thu, 02 Apr 2026 08:05:32 GMT”],“Server”:[“ESF”],“Server-Timing”:[“gfet4t7; dur=359”],“Vary”:[“Origin”,“X-Origin”,“Referer”],“X-Cloudaicompanion-Trace-Id”:[“cbe230fd43bcc5f1”],“X-Content-Type-Options”:[“nosniff”],“X-Frame-Options”:[“SAMEORIGIN”],“X-Xss-Protection”:[“0”]}

{
“error”: {
“code”: 500,
“message”: “Internal error encountered.”,
“status”: “INTERNAL”
}
}

[JonS]

I can confirm the same experience. I’m on MacBook Pro M1 with the latest Antigravity installed.

I also tried most of the steps well described below by @Florent.

See screenshot and error message below.

Trajectory ID: b462675b-b9ff-4c85
Error: HTTP 500 Internal Server Error
Sherlog:
TraceID: 0x2c286fe9b
Headers: {“Alt-Svc”:[“h3=":443"; ma=2592000,h3-29=":443"; ma=2592000”],“Content-Length”:[“109”],“Content-Type”:[“text/event-stream”],“Date”:[“Fri, 03 Apr 2026 07:25:52 GMT”],“Server”:[“ESF”],“Server-Timing”:[“gfet4t7; dur=340”],“Vary”:[“Origin”,“X-Origin”,“Referer”],“X-Cloudaicompanion-Trace-Id”:[“2c286fe9bf4297ef”],“X-Content-Type-Options”:[“nosniff”],“X-Frame-Options”:[“SAMEORIGIN”],“X-Xss-Protection”:[“0”]}

{
“error”: {
“code”: 500,
“message”: “Internal error encountered.”,
“status”: “INTERNAL”
}
}