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
Bad Gateway 502 on OpenCode Go — also affected July 3 2026 #35163
Also experiencing the same Bad Gateway 502 error with OpenCode Go since around 20:50 CST (12:50 UTC) on July 3, 2026. All models affected via the OpenCode Go / Zen API endpoint.
Error: HTTP 502 Bad Gateway — Cloudflare: "The origin web server returned an invalid or incomplete response to Cloudflare."
Impact: Completely blocked, retried 3 times each request, exhausted retries
Workaround: Switched to direct DeepSeek API as fallback, which worked fine
Confirmed this is an upstream OpenCode Go origin server issue, not a client-side problem. Multiple other users reporting the same (#35148, #35156, #35160). Also seeing related "Insufficient Balance" errors (#35149, #35159) which may indicate the root cause is upstream DeepSeek account/payment issues on the OpenCode Go backend.
OpenCode version
N/A (using API endpoint directly)
Operating System
Linux
Additional context
This is the first time we have encountered this issue — no previous 502 occurrences in our monitoring.
A few of us in the community have gathered evidence showing the root cause is Cloudflare’s proxy read timeout (120s) killing upstream requests when the model backend is under load. The 502/503 errors return raw Cloudflare HTML instead of proper JSON, which client SDKs can’t parse.
Would appreciate any update on timeline for a fix, or if there’s a configuration change we can make on our end to work around this in the meantime.
Closing this one. These 502 Bad Gateway errors were from a service outage on July 3 that has since been resolved. The latest report here is about OpenRouter, which is a separate path.
If you see 502s on OpenCode Go or Zen now, please open a new issue with the time, model and error.
Activity
hogtinbao commentedon Jul 3, 2026
也遇到了一样的问题
rfaeseke commentedon Jul 3, 2026
same problem
hogtinbao commentedon Jul 3, 2026
hogtinbao commentedon Jul 3, 2026
现在恢复正常了
logeek404 commentedon Jul 3, 2026
还是没解决吧 有没有补偿啊
。。。
Crqptx commentedon Jul 3, 2026
Issue might be resolved - give it a try. Deepseek V4 Flash Free & Big Pickle are working for me again.
See #35142
darrenloasby commentedon Jul 3, 2026
I'm still experiencing issues been out for atleast 90m on my end
Turgaud88 commentedon Jul 3, 2026
Несколько минут назад были подобные проблемы, сейчас все окей, Deepseek V4 Flash работает
hogtinbao commentedon Jul 3, 2026
现在使用deep seek V4 Flash可以正常运行
rfaeseke commentedon Jul 3, 2026
seems to be functioning normally again.
indubitablyodin commentedon Jul 5, 2026
This issue just showed up for me.
big-cookie commentedon Jul 5, 2026
Same problem for me as well
duruonanni commentedon Jul 16, 2026
Hey @thdxr @adamdotdevin @Brendonovich — this issue is still affecting users (last report July 5). Also related: #36889, #32215, #33726.
A few of us in the community have gathered evidence showing the root cause is Cloudflare’s proxy read timeout (120s) killing upstream requests when the model backend is under load. The 502/503 errors return raw Cloudflare HTML instead of proper JSON, which client SDKs can’t parse.
Would appreciate any update on timeline for a fix, or if there’s a configuration change we can make on our end to work around this in the meantime.
elliejayliquid commentedon Aug 19, 2026
This is happening through OpenRouter for me with DeepSeek v4 Pro 0813 on OpenCode desktop.
neriousy commentedon Oct 1, 2026
Closing this one. These 502 Bad Gateway errors were from a service outage on July 3 that has since been resolved. The latest report here is about OpenRouter, which is a separate path.
If you see 502s on OpenCode Go or Zen now, please open a new issue with the time, model and error.