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
OpenCode Go: deepseek-v4.1-flash returns 402 insufficient_user_quota from OrcaRouter while Go quota is healthy #49936
deepseek-v4.1-flash via OpenCode Go returns HTTP 402 insufficient_user_quota from an OrcaRouter upstream, while the OpenCode Go account quota is healthy and other Go models work with the same API key/session.
This is the same September wave reported in #37231 (see the 2026-09-19 comment from @hyuri) and #49416.
Steps to reproduce
Call OpenCode Go Chat Completions with deepseek-v4.1-flash:
Same wave here — reproducing from a third-party client (omp/oh-my-pi 18.2.6, provider opencode-go, model deepseek-v4.1-flash, macOS) with a healthy Go quota, in the same window as your report (09:06Z–09:24Z, 8 consecutive 402s).
GET /v1/usage → rolling 6% / weekly 2% / monthly 1%, status: ok.
Two data points that might help localize this:
It looks session/route-scoped rather than model-scoped: with freshly generated x-opencode-session values, the same model returned 200 from the same machine and same key minutes apart (09:22Z–09:23Z), including with "reasoning_effort":"max". A long-lived session in the same window kept getting the same 402 on every retry. Requests with no x-opencode-session still get the expected 400 MissingSessionID.
The relayed amount varies per request ($0.02 in other reports, $0.05 here), so it reads as the upstream account's balance, not the caller's Go quota.
Starting a new session may be a usable workaround in the meantime.
Happy to provide request IDs to the maintainers privately if that helps.
I can reproduce the same issue today with deepseek-v4.1-flash via OpenCode Go.
My OpenCode Go quota is still healthy:
5-hour usage: 14.3%
Weekly usage: 42.1%
Monthly usage: 61.2%
GLM-5.3 Flash works normally under the same OpenCode Go subscription/session.
However, deepseek-v4.1-flash remained stuck on Thinking for a long time, and Stop/Abort did not respond immediately. Eventually it returned:
Error from provider (Console Go): Upstream request failed:
[insufficient_user_quota] You're out of credits — this request needs $0.05.
Add credits to keep going:
https://www.orcarouter.ai/console/billing?ref=err_credit_gate#add-credits
request id:
202609190936037680844508268d9d61pkyhO7f
There also seem to be related historical reports such as #27595 / #27598, although my current issue is specifically with deepseek-v4.1-flash returning OrcaRouter insufficient_user_quota while my Go quota is still available.
OpenCode Go usage at recovery: rolling 10%, weekly 53%, monthly 26%.
This looks like a transient upstream routing/quota failure on the OrcaRouter path rather than a permanent fix. Other Go models remained 200 throughout. Please keep this issue open until the upstream health check/failover behavior is fixed and there is a root-cause update.
Thanks for the report, and sorry for the disruption. This was a temporary problem with the hosted service or an upstream model provider, and it has since recovered. You can see live status and past incidents at https://status.opencode.ai. If you still see this now, please open a new issue with the time (with timezone), model, and request ID from the console logs.
Activity
fanchw commentedon Sep 19, 2026
Same wave here — reproducing from a third-party client (omp/oh-my-pi 18.2.6, provider
opencode-go, modeldeepseek-v4.1-flash, macOS) with a healthy Go quota, in the same window as your report (09:06Z–09:24Z, 8 consecutive 402s).GET /v1/usage→rolling 6% / weekly 2% / monthly 1%,status: ok.Two data points that might help localize this:
x-opencode-sessionvalues, the same model returned200from the same machine and same key minutes apart (09:22Z–09:23Z), including with"reasoning_effort":"max". A long-lived session in the same window kept getting the same 402 on every retry. Requests with nox-opencode-sessionstill get the expected400 MissingSessionID.Starting a new session may be a usable workaround in the meantime.
Happy to provide request IDs to the maintainers privately if that helps.
xinian5216 commentedon Sep 19, 2026
I can reproduce the same issue today with
deepseek-v4.1-flashvia OpenCode Go.My OpenCode Go quota is still healthy:
GLM-5.3 Flashworks normally under the same OpenCode Go subscription/session.However,
deepseek-v4.1-flashremained stuck on Thinking for a long time, and Stop/Abort did not respond immediately. Eventually it returned:zfei2080 commentedon Sep 19, 2026
Update 2026-09-19: the same deepseek-v4.1-flash request/key/session started returning 200 again after roughly an hour, with no client-side changes.
Success response ID: 00f43eb9-0605-4934-adc8-b703f9bffc95
OpenCode Go usage at recovery: rolling 10%, weekly 53%, monthly 26%.
This looks like a transient upstream routing/quota failure on the OrcaRouter path rather than a permanent fix. Other Go models remained 200 throughout. Please keep this issue open until the upstream health check/failover behavior is fixed and there is a root-cause update.
AClon314 commentedon Sep 19, 2026
In pi, I use
/compressto start a new session with new context window. That works for meneriousy commentedon Oct 21, 2026
Thanks for the report, and sorry for the disruption. This was a temporary problem with the hosted service or an upstream model provider, and it has since recovered. You can see live status and past incidents at https://status.opencode.ai. If you still see this now, please open a new issue with the time (with timezone), model, and request ID from the console logs.