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
opencode.ai unreachable from mainland China: 172.65.90.0/24 edge IPs get TCP-reset #50735
opencode.ai is unreachable from mainland China. The apex domain resolves to 172.65.90.20-23, and TCP connections to any of them on port 443 time out after ~84s. Other Cloudflare edge IPs serve the same site fine (200 in <1s), so the site itself is up.
Observed from a residential network in mainland China (Asia/Shanghai), 2026-09-23:
$ Resolve-DnsName opencode.ai
172.65.90.20 / .21 / .22 / .23 <- all blocked (TCP timeout on 443)
$ curl -I https://opencode.ai
curl: (28) Failed to connect to opencode.ai port 443 after 84187 ms
# forcing a non-blocked Cloudflare IP works:
$ curl --resolve opencode.ai:443:172.66.173.149 -I https://opencode.ai # -> 200 in 0.76s
$ curl --resolve opencode.ai:443:104.20.32.17 -I https://opencode.ai # -> 200 in 0.83s
Controls from the same network at the same time: cloudflare.com, netlify.com, github.com all reachable (200/301 in ~1s), so this is not a blanket Cloudflare/DNS problem - specifically the 172.65.90.0/24 range is being dropped/reset by the local network. Also note www.opencode.ai returns a 301 back to the apex, so the www subdomain does not help.
Steps to reproduce
On a residential network in mainland China: curl -I https://opencode.ai -> "curl: (28) Failed to connect" after ~84s
curl --resolve opencode.ai:443:172.66.173.149 -I https://opencode.ai -> 200 OK in <1s (site is up, only those edge IPs are blocked)
Operating System
Windows 11 (PowerShell 5.1)
Ask
Could the infra/ops team check whether Cloudflare egress for opencode.ai is landing only in the 172.65.90.0/24 range for CN viewers, and whether that range is known to be blocked? If it cannot be fixed at the CDN level, two lightweight mitigations would go a long way:
Serve the site on an additional domain/CDN whose edge IPs are reachable from CN.
Document a hosts-file workaround in the docs for affected regions, e.g.:
Thanks for the detailed write-up, @sugu6, and for testing against other Cloudflare edge IPs. That makes it clear the site is up and only the 172.65.90.0/24 addresses are dropped on your network.
This isn't something the OpenCode app can fix in code, so I've recorded it as a request for the team. You're asking them to check which Cloudflare edge range opencode.ai gets for viewers in mainland China, and to either serve the site on an extra domain or CDN that is reachable from CN, or document a hosts-file workaround for affected regions. Maintainers will consider it.
Until then, the workaround you found (pointing opencode.ai at a reachable Cloudflare IP in your hosts file) is the practical option. Keep in mind that Cloudflare can change which IPs serve the site, so it may stop working at some point.
Activity
github-actions commentedon Sep 22, 2026
This issue might be a duplicate of existing issues. Please check:
opencode.aibeing unreachable from mainland China (China Telecom) — frequent 502/ECONNRESET errors affecting streaming connections from CN residential networks.If your issue is the same root cause, please consider adding information there instead, or linking the two issues.
opencodejr commentedon Oct 28, 2026
Thanks for the detailed write-up, @sugu6, and for testing against other Cloudflare edge IPs. That makes it clear the site is up and only the
172.65.90.0/24addresses are dropped on your network.This isn't something the OpenCode app can fix in code, so I've recorded it as a request for the team. You're asking them to check which Cloudflare edge range opencode.ai gets for viewers in mainland China, and to either serve the site on an extra domain or CDN that is reachable from CN, or document a hosts-file workaround for affected regions. Maintainers will consider it.
Until then, the workaround you found (pointing
opencode.aiat a reachable Cloudflare IP in your hosts file) is the practical option. Keep in mind that Cloudflare can change which IPs serve the site, so it may stop working at some point.Related issues:
Connect Timeout Erroron172.65.90.20-23:443, so this probably affects API access too, not just the website172.65.90.20/22/23:443Connect Timeout Errorto the same172.65.90.xaddresses in OpenCode Desktop on Windows