You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug] OpenCode Go: return 401 Request blocked by upstream provider — chat/completions blocked while /v1/models works #38257
Starting today (2026-07-22), all models under my OpenCode Go subscription are returning 401 Request blocked by upstream provider when calling the chat/completions endpoint. The /v1/models endpoint works fine.
This appears to be a server-side issue affecting Go subscriptions, not a client configuration problem.
Account Details
Subscription: OpenCode Go
Expiry: 2026-08-13
Console status: All usage limits (5h / weekly / monthly) show sufficient balance
API Key: Valid (tested with newly created key, same result)
Affected Models
All of the following models return the same error:
These issues report the same symptom — chat/completions returning 401 Request blocked by upstream provider while /v1/models works fine — for Go subscription users starting today.
Is it possible that the account has been disabled? I noticed that this issue doesn’t occur in all accounts.账户可能被禁用了吗?我注意到这个问题并非所有账户都会出现。 是不是账号被禁用了?我发现并非所有账号都出现这个问题
看起来不像是账号禁用的问题。opencode 不像 anthropic 和 OpenAI 属于商业 AI 范畴,禁用账号是出于政策原因。我身边也有朋友是订阅了 GO 还正常能用的,现在还不完全知道问题所在
API key authenticates successfully (opencode models lists 60+ Zen models) but all chat completions fail with AuthError: Request blocked by upstream provider. Direct curl confirms same error without OpenCode. Recreated account, new keys — identical result. Direct provider keys (DeepSeek, Anthropic) work fine.
Root cause traced to source in #38218 (comment) — short version: this string is thrown by the workspace.isBlocked check in packages/console/app/src/routes/zen/util/handler.ts (added in c40e3e7, 2026-07-21). No upstream provider is contacted; the request is refused at opencode's edge (~114 ms, same latency as the local invalid-key path), and the same models answer anonymously in the same second. Key rotation, cache clearing, and re-login cannot help. #40944 proposes a distinct error message for this case so it stops presenting as a vendor outage.
Same issue here — paying OpenCode Go subscriber, all Go-tier models blocked since 2026-07-22 while free models work.
Verified reproduction (own account):
GET /zen/go/v1/models → 200 OK (key valid, full model list)
POST /zen/go/v1/chat/completions (model deepseek-v4-flash) → 401{"type":"error","error":{"type":"AuthError","message":"Request blocked by upstream provider."}}
Account state: Go subscription active, all usage limits (hourly/weekly/monthly) sufficient, API key valid — also tried a freshly generated key, same result. /v1/models works while chat/completions is blocked, so the key itself is fine; the block happens server-side on the upstream provider call.
Affected models (all same error): deepseek-v4-pro, deepseek-v4-flash, kimi-k2.6, glm-5.2, minimax-m3, etc.
Paying users are currently unable to use the service they subscribe to. Any update / ETA on a fix, and will there be compensation (prorated refund) for the downtime?
Also observed during an outage window (Aug 9, ~06:00-14:00 UTC?):
even requests WITHOUT any API key returned HTTP 500
{"type":"error","error":{"type":"error","message":"Internal server error"}}
The gateway recovered later and now returns 401 again.
My key, workspace, and subscription all look correct on the console side,
so this appears to be a server-side account/subscription issue, not a
client configuration problem. Please check whether my account/subscription
was flagged on the backend. Could I get my subscription activated or
extended? I've already paid but can't use any Go models.
---Original---
From: ***@***.***>
Date: Sun, Aug 9, 2026 17:41 PM
To: ***@***.***>;
Cc: ***@***.******@***.***>;
Subject: Re: [anomalyco/opencode] [Bug] OpenCode Go: return 401 Request blocked by upstream provider — chat/completions blocked while /v1/models works (Issue #38257)
chanada440824 left a comment (anomalyco/opencode#38257)
Hi, I'm experiencing the same issue and I've gathered additional evidence.
Account: subscribed to OpenCode Go
Workspace: "default" (top-left of console)
Go page shows subscription as ACTIVE
API key is active in the console, and it matches what's stored in auth.json
I verified with curl directly (no client involved):
GET https://opencode.ai/zen/go/v1/models → HTTP 200 (OK)
POST https://opencode.ai/zen/go/v1/chat/completions
with "Authorization: Bearer " → HTTP 401
{"type":"error","error":{"type":"AuthError","message":"Invalid API key."}}
POST https://opencode.ai/zen/v1/chat/completions (free model, same key)
→ HTTP 401 Invalid API key. (free models fail too)
Also observed during an outage window (Aug 9, ~06:00-14:00 UTC?):
even requests WITHOUT any API key returned HTTP 500
{"type":"error","error":{"type":"error","message":"Internal server error"}}
The gateway recovered later and now returns 401 again.
My key, workspace, and subscription all look correct on the console side,
so this appears to be a server-side account/subscription issue, not a
client configuration problem. Please check whether my account/subscription
was flagged on the backend. Could I get my subscription activated or
extended? I've already paid but can't use any Go models.
Windows, OpenCode 1.18.15, subscription via GitHub account
***@***.***
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: ***@***.***>
I’m experiencing the same issue as of Aug 24, 2026.
My OpenCode Go subscription/workspace is active, but multiple Go models all return HTTP 401 with an account-blocked response.
Tested models include Ox Alpha Free, Muse, and MiMo. All three fail with the same account-level response, so this does not appear to be a model-specific failure.
Workspace: wrk_01KNNJ7DYWHXV1VZKNMYFBVHFP
Cloudflare Ray IDs:
a302c84b794ca344-SEA
a302c84f3e0a935e-SEA
a302c851edf4a32e-SEA
I have already contacted help@anoma.ly and requested a manual review.
No API keys or OAuth credentials are included here.
Could the OpenCode team please confirm whether this is an automated account-level enforcement issue and manually review the affected workspace?
---Original---
From: ***@***.***>
Date: Mon, Aug 24, 2026 22:12 PM
To: ***@***.***>;
Cc: ***@***.******@***.***>;
Subject: Re: [anomalyco/opencode] [Bug] OpenCode Go: return 401 Request blocked by upstream provider — chat/completions blocked while /v1/models works (Issue #38257)
zxc8976 left a comment (anomalyco/opencode#38257)
I’m experiencing the same issue as of Aug 24, 2026.
My OpenCode Go subscription/workspace is active, but multiple Go models all return HTTP 401 with an account-blocked response.
Tested models include Ox Alpha Free, Muse, and MiMo. All three fail with the same account-level response, so this does not appear to be a model-specific failure.
Workspace: wrk_01KNNJ7DYWHXV1VZKNMYFBVHFP
Cloudflare Ray IDs:
a302c84b794ca344-SEA
a302c84f3e0a935e-SEA
a302c851edf4a32e-SEA
I have already contacted ***@***.*** and requested a manual review.
No API keys or OAuth credentials are included here.
Could the OpenCode team please confirm whether this is an automated account-level enforcement issue and manually review the affected workspace?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: ***@***.***>
Closing as a duplicate of #38218. Same "Request blocked by upstream provider" 401. This error comes from OpenCode's own gateway (a blocked workspace), not from an upstream provider. Account unblocks and refunds are handled per workspace, so please contact support (help@anoma.ly) with your workspace ID.
Activity
github-actions commentedon Jul 22, 2026
This issue might be a duplicate of existing issues. Please check:
These issues report the same symptom —
chat/completionsreturning401 Request blocked by upstream providerwhile/v1/modelsworks fine — for Go subscription users starting today.gopalkalaleat-sudo commentedon Jul 22, 2026
这没有办法解决么?
Dante926 commentedon Jul 22, 2026
目前看来是 opencode 的模型服务提供有问题了。只能等官方解决了
xiaoyixiaoba commentedon Jul 22, 2026
Is it possible that the account has been disabled? I noticed that this issue doesn’t occur in all accounts.
是不是账号被禁用了?我发现并非所有账号都出现这个问题
Dante926 commentedon Jul 22, 2026
看起来不像是账号禁用的问题。opencode 不像 anthropic 和 OpenAI 属于商业 AI 范畴,禁用账号是出于政策原因。我身边也有朋友是订阅了 GO 还正常能用的,现在还不完全知道问题所在
SZipC commentedon Jul 22, 2026
我看有很多人提这个问题,但是我现在还没有看到解决方法或者是原因,我甚至不知道是不是我账号的原因
tcszh commentedon Jul 22, 2026
I have the same problem in Uganda.
Dante926 commentedon Jul 22, 2026
别怀疑自己,这大面积的 401.一定是服务商有问题了
angellfear commentedon Jul 22, 2026
+1
Tangmjiu commentedon Jul 22, 2026
+1
gopalkalaleat-sudo commentedon Jul 22, 2026
看起来不像是ban账号,我看有人说他支付宝支付的也401了
Tangmjiu commentedon Jul 22, 2026
现在官方也没出来回应,也不知道想干什么,目前网上关于这个报错的信息就那几个文章
gopalkalaleat-sudo commentedon Jul 22, 2026
Tangmjiu commentedon Jul 22, 2026
Deepseek 早上联网搜索也爆了,但是很快就解决了,这帮老外真的是,无语😓
26 remaining items
suse-coder commentedon Jul 30, 2026
same problem still. Please urgently fix.
juanmah98 commentedon Jul 31, 2026
API key authenticates successfully (opencode models lists 60+ Zen models) but all chat completions fail with AuthError: Request blocked by upstream provider. Direct curl confirms same error without OpenCode. Recreated account, new keys — identical result. Direct provider keys (DeepSeek, Anthropic) work fine.
winqihe commentedon Aug 2, 2026
Sanjay-doppalapudi commentedon Aug 6, 2026
Root cause traced to source in #38218 (comment) — short version: this string is thrown by the
workspace.isBlockedcheck inpackages/console/app/src/routes/zen/util/handler.ts(added in c40e3e7, 2026-07-21). No upstream provider is contacted; the request is refused at opencode's edge (~114 ms, same latency as the local invalid-key path), and the same models answer anonymously in the same second. Key rotation, cache clearing, and re-login cannot help. #40944 proposes a distinct error message for this case so it stops presenting as a vendor outage.BeliliFahem commentedon Aug 7, 2026
Same issue here — paying OpenCode Go subscriber, all Go-tier models blocked since 2026-07-22 while free models work.
Verified reproduction (own account):
GET /zen/go/v1/models→200 OK(key valid, full model list)POST /zen/go/v1/chat/completions(modeldeepseek-v4-flash) →401{"type":"error","error":{"type":"AuthError","message":"Request blocked by upstream provider."}}Account state: Go subscription active, all usage limits (hourly/weekly/monthly) sufficient, API key valid — also tried a freshly generated key, same result.
/v1/modelsworks whilechat/completionsis blocked, so the key itself is fine; the block happens server-side on the upstream provider call.Affected models (all same error):
deepseek-v4-pro,deepseek-v4-flash,kimi-k2.6,glm-5.2,minimax-m3, etc.Paying users are currently unable to use the service they subscribe to. Any update / ETA on a fix, and will there be compensation (prorated refund) for the downtime?
chanada440824 commentedon Aug 9, 2026
Hi, I'm experiencing the same issue and I've gathered additional evidence.
Account: subscribed to OpenCode Go
I verified with curl directly (no client involved):
GET https://opencode.ai/zen/go/v1/models → HTTP 200 (OK)
POST https://opencode.ai/zen/go/v1/chat/completions
with "Authorization: Bearer " → HTTP 401
{"type":"error","error":{"type":"AuthError","message":"Invalid API key."}}
POST https://opencode.ai/zen/v1/chat/completions (free model, same key)
→ HTTP 401 Invalid API key. (free models fail too)
Also observed during an outage window (Aug 9, ~06:00-14:00 UTC?):
even requests WITHOUT any API key returned HTTP 500
{"type":"error","error":{"type":"error","message":"Internal server error"}}
The gateway recovered later and now returns 401 again.
My key, workspace, and subscription all look correct on the console side,
so this appears to be a server-side account/subscription issue, not a
client configuration problem. Please check whether my account/subscription
was flagged on the backend. Could I get my subscription activated or
extended? I've already paid but can't use any Go models.
Windows, OpenCode 1.18.15, subscription via GitHub account
chanada0824@outlook.com.
huashuhuashu720 commentedon Aug 9, 2026
winqihe commentedon Aug 12, 2026
你们都是怎么处理的呀,这个月到期了,后面一直用不上
chanada440824 commentedon Aug 19, 2026
huashuhuashu720 commentedon Aug 19, 2026
zxc8976 commentedon Aug 24, 2026
I’m experiencing the same issue as of Aug 24, 2026.
My OpenCode Go subscription/workspace is active, but multiple Go models all return HTTP 401 with an account-blocked response.
Tested models include Ox Alpha Free, Muse, and MiMo. All three fail with the same account-level response, so this does not appear to be a model-specific failure.
Workspace: wrk_01KNNJ7DYWHXV1VZKNMYFBVHFP
Cloudflare Ray IDs:
a302c84b794ca344-SEA
a302c84f3e0a935e-SEA
a302c851edf4a32e-SEA
I have already contacted help@anoma.ly and requested a manual review.
No API keys or OAuth credentials are included here.
Could the OpenCode team please confirm whether this is an automated account-level enforcement issue and manually review the affected workspace?
huashuhuashu720 commentedon Aug 24, 2026
zxc8976 commentedon Aug 24, 2026
我是自己的帳號並且使用自己的信用卡購買 已經用了4個月 只是這幾天ox alpha高頻率使用而我在discord跟rebbit也看到這兩天有其他人發生類似狀況
neriousy commentedon Oct 1, 2026
Closing as a duplicate of #38218. Same "Request blocked by upstream provider" 401. This error comes from OpenCode's own gateway (a blocked workspace), not from an upstream provider. Account unblocks and refunds are handled per workspace, so please contact support (help@anoma.ly) with your workspace ID.