Repository navigation
Description
Description
Since 2026-10-18 11:00 UTC, every request to OpenCode's own free models from my network is rejected with this 403:
AI.Error: OpenCode's free models aren't available from your current network because we've detected abusive traffic from this IP address. This isn't related to your account. If you're on a VPN or proxy, turn it off and try again, or subscribe to OpenCode Go at https://opencode.ai/go to keep building.
From 11:00 to 14:40 UTC the same request failed with the shorter variant AI.Error: Forbidden, OpenCode Free Model Gateway Detect Abuse Traffic.
Details that narrow it down:
- No VPN, no proxy, no scripts or automation. Only interactive sessions, a few requests per hour, all from my own machine.
- The block follows the network, not the app: the desktop app and the CLI both fail, and closing or restarting the app changes nothing.
- The same egress IP still works for other providers' free models (OpenRouter
:freemodels succeed on every request), andGET https://opencode.ai/zen/v1/modelsreturns 200. So this is the free-model gateway's abuse classifier rejecting the request, not a network-level ban on the IP. - I am not signed in to an OpenCode Console account, so no account, key or balance is involved.
- My public IP belongs to a cloud/hosting ASN rather than a residential ISP. If the classifier auto-flags cloud address space, that would explain a false positive on a single user.
There is a mass of identical reports: #56853, #56874, #56916, #57056, #57074, #57144, all closed with the same advice to contact support by email. I emailed support on 2026-10-19 and have had no reply since, so I am filing this here as the only remaining channel. As requested in those replies, I am not posting my IP address, email or account details here.
Request: please review the flag on my egress IP, or point me to a channel that is actually being monitored.
Plugins
None. One MCP server (rea) is configured, unrelated to the failure.
OpenCode version
2.0.32 (channel latest)
Steps to reproduce
- Run
opencode run --model opencode/mimo-v2.6-flash-free "ping", or start any session on anopencode/*-freemodel. - The request fails immediately with the 403 message quoted above.
- Repeat later: still fails, several times per day since 2026-10-18 11:00 UTC.
- Log evidence in
~/.local/share/opencode/log/opencode.log:2026-10-18T11:00:06.146Z ... AI.Error: Forbidden, OpenCode Free Model Gateway Detect Abuse Traffic2026-10-20T02:40:09.538Z ... AI.Error: OpenCode's free models aren't available from your current network ...2026-10-20T03:28:10.252Z ...and2026-10-20T06:27:26.589Z ...(same error, still happening today)
Screenshot
Not attached; the error is reproducible from the CLI and quoted in full above.
Operating System
Windows 10 Pro, 10.0.19045 (x64)
Terminal
OpenCode desktop app and TUI on Windows; also reproduced with the CLI (opencode run) in PowerShell.
Activity
opencode-agent commentedon Oct 20, 2026
Thanks for the careful report, and sorry you've been locked out of the free models since 2026-10-18, especially since your email hasn't been answered yet. Your checks are right: the 403 comes from the OpenCode free model gateway's abuse detection, which has flagged your egress IP. It isn't a bug in the OpenCode app, and only the team can review or lift the flag. The detail that your IP is in a cloud/hosting network rather than a home ISP's is useful for them.
This kind of account and network support isn't handled in GitHub issues; it goes through help@anoma.ly. You've already emailed, so the team will get to it, especially now that it has come up here. If you reply to your email thread, adding the timestamps from your log and the cloud/hosting network detail may help. Please keep your IP address, email and any account details out of this public issue (thanks for already doing that) and put them only in the email.
Related reports of the same block, all handled through email support:
The bot will close this issue in 1 day.
opencode-agent commentedon Oct 21, 2026
Closing this now, @YangyuAndYangyu. Only the team can review the IP flag on the free model gateway, and that happens by email, not here on GitHub. You've already written to help@anoma.ly, so you don't need to send a new email; the team will get to it. If anything else comes up, reply on that same email thread. Please keep your IP address and account details there and out of this public issue. Thanks again for such a careful report, and sorry for the trouble.