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
Upstream request failed: Endpoint is unavailable. #42757
Potential fix/workaround: I was running opencode in keyless mode (no login). All other free models worked, but deepseek-v4-flash-free kept failing with 'Upstream request failed: Endpoint is unavailable.' I created a fresh API key from the OpenCode Zen dashboard, connected with that key instead of keyless mode, and everything works now. Suspect keyless/anonymous Zen requests get deprioritized or routed differently on the free DeepSeek lane.
Reacted by ShogunHirei, alexanderdbondar and Alexander Arana
Closing: "Upstream request failed: Endpoint is unavailable" was a temporary gateway outage around Aug 15-17 that has since been resolved. If you still see it on the latest version, please open a new issue with the model and time of the failure. Some cases were caused by the console privacy region setting (Settings → Privacy), so check that too.
Activity
github-actions commentedon Aug 15, 2026
This issue might be a duplicate of existing issues. Please check:
shashankgfx commentedon Aug 15, 2026
Potential fix/workaround: I was running opencode in keyless mode (no login). All other free models worked, but deepseek-v4-flash-free kept failing with 'Upstream request failed: Endpoint is unavailable.' I created a fresh API key from the OpenCode Zen dashboard, connected with that key instead of keyless mode, and everything works now. Suspect keyless/anonymous Zen requests get deprioritized or routed differently on the free DeepSeek lane.
neriousy commentedon Oct 1, 2026
Closing: "Upstream request failed: Endpoint is unavailable" was a temporary gateway outage around Aug 15-17 that has since been resolved. If you still see it on the latest version, please open a new issue with the model and time of the failure. Some cases were caused by the console privacy region setting (Settings → Privacy), so check that too.