Go subscription: HTTP 429 outage on 2026-09-06 (multi-hour retry-after) — compensation requested

Summary

Paying OpenCode Go subscriber. On 2026-09-06 the Go endpoint
https://opencode.ai/zen/go/v1/messages returned HTTP 429 for an extended
period, making the paid Go service unusable. This report focuses on that
service outage and the compensation it warrants.

Environment

• OpenCode version: 1.18.29
• OS: CachyOS (Arch-based), Linux kernel 7.2.2-1-cachyos
• Terminal: xfce4-terminal

Steps to Reproduce

1. Use the opencode-go provider (e.g. opencode run --model opencode-go/qwen3.8-flash "ok").
2. Observe the request to https://opencode.ai/zen/go/v1/messages returning HTTP 429.

Expected behavior

A paying subscriber should be able to use the Go service normally; the 429
should only occur after genuinely exceeding the sliding limits.

Actual behavior

• 39 HTTP 429 responses logged on the Go endpoint on 2026-09-06.
• Each returned a retryAfterMs of ~37 626 000 → 48 533 000 ms (~10.5 h → 13.5 h), resetting on each attempt.
• The free Zen models (e.g. Big Pickle) worked instantly during the same period → the fault is specific to the Go endpoint, not my network/auth/config.
• On 09-06, 10 Go sessions were recorded at 0.00 $ (blocked attempts, no usable output).

Impact

The paid Go service was effectively unavailable for the duration of the 429
block on 2026-09-06. This is the basis of the compensation request below.

Request

Given the Go service was down for an extended period on 2026-09-06 (repeated
429s with multi-hour retry-after, while free Zen models worked), please grant
compensation for the lost paid service time (credit/extension on the Go
subscription).

Full log excerpts and the opencode.db aggregate are available on request;
happy to share details privately.