Skip to content

Free tier IP-level block: "detected abusive traffic" on home network — expiry / review? #56853

Closed as not planned

Description

@wushuang404

Description

Since 2026-10-18 ~15:13 UTC, every free-tier request from my home network fails at the IP level with the "detected abusive traffic" error below. The same account and app work fine when I tether through a mobile hotspot, so the block is scoped to my home IP, not my account.

Context: previously, a local learning plugin (claude-smart) used opencode run through a local CLI bridge to make small automated extraction calls against the free tier. That automation was very likely what triggered the flag, and it was my mistake to point it at the free tier. I have now stopped that automation completely and rerouted it to a third-party API (Zhipu GLM-4.5-Flash). It no longer touches the free tier at all, and I will not point automation at the free tier again.

Error

AI.Error.Authentication: 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

Steps to reproduce

  1. On my home network (China Mobile residential, no VPN/proxy active):
    opencode run --agent plan --model opencode/deepseek-v4.1-flash-free "Reply with exactly: PING"
    
  2. Observe 403 FreeTierError "abusive traffic" (CLI). The desktop app shows the same error on all free models.
  3. Tether through a mobile hotspot with the same account and repeat → free tier works normally.

Timeline (UTC)

  • 2026-10-18 15:13–16:16 — 98 "Failed to drain Session" log entries with the error above (desktop app sessions).
  • 2026-10-18 16:42, 16:46 — same error from a fresh CLI run after switching back to the home network (session IDs ses_eb01b1da8ffetMixmgjFUFIsqH, ses_eb1a62987ffeGG6dLRsmK8iuJr).
  • 2026-10-18 ~16:57 — still reproducible; the block has persisted for ~2 hours so far.

Questions / request

  1. Does this IP-level flag expire automatically? If so, roughly how long does it take?
  2. If it does not expire, could it be reviewed and unblocked? (Similar to OpenCode's free tier can only be used from within OpenCode. Download it at https://opencode.ai and keep building. #55483, where the same question is still unanswered.)
  3. Any guidance on what counts as "abusive" for CLI automation would be appreciated, so I can avoid it in the future.

Log excerpts (sanitized)

level=ERROR message="Failed to drain Session"
cause="AI.Error.Authentication: 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. ..."

Plugins

@tarquinen/opencode-dcp, opencode-parser, opencode-img, opencode2-grok-imagine, opencode-planning-with-files, plus a local learning plugin (claude-smart — its free-tier automation has been disabled and rerouted off the free tier).

OpenCode version

2.0.32 (latest, desktop app bundled CLI)

Operating System

Windows 11 (10.0.26200)

Terminal

Windows Terminal / cmd.exe (plus desktop app sessions)

Activity

  1. opencode-agent commented on Oct 18, 2026

    @opencode-agent
    Contributor

    Thanks for the detailed report, and for explaining the automation and shutting it down. The error comes from the OpenCode free model gateway, not the app: its abuse detection has flagged your home network's IP address. Only the team can say whether that flag expires or review and lift it. We can't change it from GitHub.

    Billing and account support isn't handled in GitHub issues. Please email help@anoma.ly with the details: when the block started (2026-10-18 ~15:13 UTC), the session IDs you listed, that the automation has been stopped and moved off the free tier, and that you'd like the IP reviewed. You can also ask them what kinds of CLI automation are acceptable. If you've already emailed, the team will get to it, especially now that we've seen it here. Please keep your IP address, email address and account details out of this public issue and put them in the email instead.

    Related reports:

    The bot will close this issue in 1 day.

  2. opencode-agent commented on Oct 19, 2026

    @opencode-agent
    Contributor

    We're closing this issue now. The IP-level block comes from the free model gateway and can only be reviewed by the team, so it isn't something we can resolve here on GitHub.

    If your home network is still blocked, or you still have questions about acceptable CLI automation, please email help@anoma.ly with the timeline and session IDs from this issue. Please keep your IP address and account details out of this public thread. Thanks again for explaining what happened and moving the automation off the free tier.

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

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions