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
Multiple models/providers intermittently fail with Endpoint is unavailable #53841
Multiple models/providers intermittently fail with Endpoint is unavailable
Describe the bug
I am experiencing frequent upstream request failures across multiple models, not just one specific model.
For example, Muse can show:
upstream request failed: Endpoint is unavailable. [retrying in 3s attempt #2]
However, I have also encountered similar failures with other models/providers. This makes the issue seem broader than a single model or provider being unavailable.
Error message
upstream request failed: Endpoint is unavailable. [retrying in 3s attempt #2]
OpenCode may continue retrying the request several times, but the request can still fail.
Expected behavior
If an upstream endpoint is temporarily unavailable, OpenCode should:
retry reliably with appropriate backoff;
recover automatically when the endpoint becomes available;
or provide a more specific error explaining which provider/endpoint failed.
Actual behavior
Multiple different models can suddenly fail with the same or similar Endpoint is unavailable error.
This is especially frustrating because switching to another model does not always solve the problem — another model may encounter the same upstream failure.
Environment
OpenCode: 1.18.31
OS: Windows
Affected: Multiple models/providers
Network: Normal internet connection
Additional information
This does not appear to be limited to Muse. I have observed the problem with multiple models, so it may be related to:
provider/endpoint routing;
upstream availability detection;
shared infrastructure;
retry handling;
or how OpenCode handles temporary upstream failures.
It would be helpful if the error displayed the actual provider and endpoint involved, rather than only reporting Endpoint is unavailable.
You're on OpenCode 1.18.31, which is v1. v1 now only gets fixes for critical bugs, such as data loss, security problems or crashes with no workaround. This error comes from the upstream endpoint, OpenCode already retries it, and the failures are intermittent, so it's unlikely to be fixed in v1. Clearer error messages that name the provider and endpoint would be an improvement rather than a critical fix.
We recommend upgrading to v2 (npm package @opencode/cli, opencode command), where active development happens.
These open issues report the same Endpoint is unavailable error from the upstream gateway and may be worth following:
If you think this is critical, or it also happens on v2, please reply here with your v2 version (opencode --version), the provider and model you used, and what you did when it happened.
I understand that v1 is now only receiving critical fixes. My main concern is that this does not appear to be a Muse-specific issue, since I have encountered the same Endpoint is unavailable failure across multiple models/providers.
The existing issues you linked also seem to confirm that this is affecting different models and endpoints.
I'll test this on v2 and, if I can reproduce it there, I'll provide:
Thanks for following up, @youhongtan, and for testing on v2!
You're right that it isn't limited to Muse. The linked reports show the same Endpoint is unavailable error on several models.
This issue is tracked as a v1 report, so it will close automatically at 2026-10-09 02:41 UTC unless there's new information before then. If you reproduce it on v2 before that, reply here with the details you listed and we'll take it from there. If you find it later, please open a new issue with those details and mention #53841. You can also add your v2 findings to whichever of the linked issues matches your model and provider most closely.
I'll test v2 across multiple models/providers and check whether I can reproduce the Endpoint is unavailable error there. If it happens, I'll reply with the exact OpenCode version, provider, model, and full error output before the issue closes.
If I reproduce it after this issue closes, I'll open a new issue and reference #53841.
Sounds good, thanks @youhongtan! We'll look at your v2 results whenever you have them, either here before it closes or in a new issue that references #53841.
Closing this as not planned. It was reported on OpenCode v1 (1.18.31), which only gets critical fixes, and we haven't seen it on v2 yet. Thanks for the report and the follow-ups, @youhongtan!
If you get the Endpoint is unavailable error on v2, please open a new issue that references #53841. Include your opencode --version output, the provider and model, what you were doing, and the full error and retry output.
Activity
opencode-agent commentedon Oct 8, 2026
Thanks for the detailed report, @youhongtan!
You're on OpenCode 1.18.31, which is v1. v1 now only gets fixes for critical bugs, such as data loss, security problems or crashes with no workaround. This error comes from the upstream endpoint, OpenCode already retries it, and the failures are intermittent, so it's unlikely to be fixed in v1. Clearer error messages that name the provider and endpoint would be an improvement rather than a critical fix.
We recommend upgrading to v2 (npm package
@opencode/cli,opencodecommand), where active development happens.These open issues report the same
Endpoint is unavailableerror from the upstream gateway and may be worth following:If you think this is critical, or it also happens on v2, please reply here with your v2 version (
opencode --version), the provider and model you used, and what you did when it happened.youhongtan commentedon Oct 8, 2026
Thanks for the clarification.
I understand that v1 is now only receiving critical fixes. My main concern is that this does not appear to be a Muse-specific issue, since I have encountered the same
Endpoint is unavailablefailure across multiple models/providers.The existing issues you linked also seem to confirm that this is affecting different models and endpoints.
I'll test this on v2 and, if I can reproduce it there, I'll provide:
opencode --versionThanks for pointing me in the right direction.
opencode-agent commentedon Oct 8, 2026
Thanks for following up, @youhongtan, and for testing on v2!
You're right that it isn't limited to Muse. The linked reports show the same
Endpoint is unavailableerror on several models.This issue is tracked as a v1 report, so it will close automatically at 2026-10-09 02:41 UTC unless there's new information before then. If you reproduce it on v2 before that, reply here with the details you listed and we'll take it from there. If you find it later, please open a new issue with those details and mention #53841. You can also add your v2 findings to whichever of the linked issues matches your model and provider most closely.
youhongtan commentedon Oct 8, 2026
Got it, thanks for clarifying!
I'll test v2 across multiple models/providers and check whether I can reproduce the
Endpoint is unavailableerror there. If it happens, I'll reply with the exact OpenCode version, provider, model, and full error output before the issue closes.If I reproduce it after this issue closes, I'll open a new issue and reference #53841.
opencode-agent commentedon Oct 8, 2026
Sounds good, thanks @youhongtan! We'll look at your v2 results whenever you have them, either here before it closes or in a new issue that references #53841.
class7327-code commentedon Oct 8, 2026
У вас получилось решить проблему? У меня аналогичная проблема с различными бесплатными моделями
opencode-agent commentedon Oct 9, 2026
Closing this as not planned. It was reported on OpenCode v1 (1.18.31), which only gets critical fixes, and we haven't seen it on v2 yet. Thanks for the report and the follow-ups, @youhongtan!
If you get the
Endpoint is unavailableerror on v2, please open a new issue that references #53841. Include youropencode --versionoutput, the provider and model, what you were doing, and the full error and retry output.