11 月 6 日凌晨三点 Antigravity 集体封号，有人同一天中招吗？

[mzgss114541-gif]

就随便聊聊，别当技术报告看。

今天凌晨三点前后，我池子里三个 Antigravity 凭据死了俩，都是 403 TOS_VIOLATION，前后差四分钟。剩下那个一直在跑，没受影响。

细节都发在 #7296 了（维护者已按"非代码问题"关闭，说留着方便检索），结论一句话：绕过 CPA 直连上游也是同样的 403，所以跟本仓无关，是 Google 在收口。

好奇两点，有同样遭遇的可以聊聊：

1. 你们被封的号，是不是都集中在凌晨 3 点前后？我这边是 03:00:20 还在正常出词，03:00:21 就 403 了。
2. Google 论坛那边有人提到 Jio 渠道的 AI Pro 中招比较多，有人验证过吗？

官方论坛这波的集中帖，几十条申诉都在里面：
https://discuss.ai.google.dev/t/is-anyone-else-getting-hit-by-this-mass-antigravity-gemini-ban-looks-like-a-google-system-bug-false-positive-wave-error-id-0950956c/198498

[mzgss114541-gif]

这个论坛的集中贴很有意思，因为有人指出被封禁的全是jio会员，我有个pixel会员一直在反代，没被波及，似乎谷歌这次是冲着jio来的

[sunriseinkyoto]

[mzgss114541-gif]

Looking at this (就随便聊聊，别当技术报告看。 今天凌晨三点前后，我池子里三个 Antigravity 凭据死了俩，都是 403 TOS_VIOLATION，前后差四分钟。剩下那个一直在跑，没受影响。 细节都发在 #7296 了（维护者已按"非代码问题"关闭，说留着方便检索），结论一句话：绕过 CPA 直连上游也是同样的 403，所以跟…), I’d debug it in this order:

1. Capture the full error/traceback (not only the last line).
2. Confirm versions: OS, runtime (python -V / node -V), and how you start the app.
3. Reproduce in a clean environment (fresh venv or clean node_modules) so old installs aren’t masking it.
4. Change one variable at a time (dependency pin, config path, env var).

If you paste the complete log from router-for-me/CLIProxyAPI and the exact command you run, we can narrow it to a concrete fix. The more specific the failing step, the faster it gets solved.

This is a unified ban from Google, not a problem with the project itself. It was simply determined that it wasn't appropriate to post an issue; let's see if anyone has encountered the same situation in the discussion forum.

[983033995]

我的5个jio的也是被封了

[frankyw]

I had 4 Jio accounts that were all banned