Skip to content

DeepSeek V4 Flash (New) route hangs - no response from zen gateway #40479

Closed

Description

@sergiomaciel

Description

The deepseek-v4-flash model (marketed as "DeepSeek V4 Flash (New)") on the opencode zen gateway fails to respond.

Endpoint

POST https://opencode.ai/zen/go/v1/chat/completions
Authorization: Bearer $OPENCODE_API_KEY

Symptoms

  • Without streaming: 0 bytes received, times out after 90s
  • With streaming: Only SSE : keep-alive pings, no actual content arrives
  • With/without max_tokens: same result
  • Billing: user is paying and has balance available

Reproduction

curl -sS -m 60 "https://opencode.ai/zen/go/v1/chat/completions" \
  -H "Authorization: Bearer $OPENCODE_API_KEY" \
  -H 'Content-Type: application/json' \
  -d '{"model":"deepseek-v4-flash","messages":[{"role":"user","content":"hello"}]}'
# Result: timeout, 0 bytes

Comparison

Other models via the same endpoint/key work fine:

  • qwen3.8-max → 2s
  • glm-5.2 → 1.6s
  • deepseek-v4-pro → 13s

Environment

  • opencode v1.18.13
  • Linux (Ubuntu 20.04)
  • git v2.50.1

Expected

deepseek-v4-flash should respond like other models.

Activity

  1. github-actions commented on Aug 4, 2026

    @github-actions
    Contributor

    This issue might be a duplicate of existing issues. Please check:

    If your issue is the same underlying server-side routing problem with the flash lane on the zen/go backend, please add a reaction or comment to one of those existing issues rather than opening a new one.

  2. KarpovVolodymyr commented on Aug 31, 2026

    @KarpovVolodymyr

    Any plans to fix it soon?
    Having the same issue

  3. Vlyn commented on Oct 7, 2026

    @Vlyn

    I'm using /zen/go/v1/chat/completions with opencode-go/deepseek-v4.1-flash as the
    classifier model for a coding agent (pi, Windows 11). Requests are tiny, one-token answers.

    Symptom: the request never returns a single byte. No HTTP status, no error, no stream
    data, my client's own 20s deadline aborts it. It's seemingly random, working fine one second,
    then no response the next.

    What makes me think it's routing/edge rather than request shape: byte-identical bodies
    succeeded in 1.0–2.5s on both sides of the failure (1.6s just before, 2.5s just after),
    and one other call in the same run took 18.7s, just under my deadline. So it's a latency
    tail with a cutoff, not a dead lane, unlike #40465, where flash fails every time.

  4. neriousy commented on Oct 21, 2026

    @neriousy
    Member

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions