Where does the bug appear (feature/product)?
Background Agent (GitHub, Slack, Web, Linear)
Describe the Bug
I believe this is more of an incident, rather than a bug; but there isn’t a place to report incidents.
Also, Cloudflare is having several maintenances right now (https://www.cloudflarestatus.com/) in case that’s the trigger of the issue, but since they say that the traffic will be re-routed, perhaps the “bug” is within your internal infra that can’t connect to CF during their maintenance, or lack of resilience.
Root cause: api3.cursor.sh is unreachable. When I curl the endpoint, I get:
- HTTP/2 404
- “The request could not be routed”
Details:
- api2.cursor.sh works fine (confirmed via network diagnostics)
- api3.cursor.sh connects but Cloudflare can’t route to backend
- Tested from multiple Cloudflare datacenters (LED, ARN) - same issue
- Tried Google DNS (8.8.8.8) - no change
- Not using VPN, firewall is off, HTTP/1.1 fallback enabled
- GitHub properly connected
curl output:
➜ curl -v https://api3.cursor.sh
- Host api3.cursor.sh:443 was resolved.
- IPv6: (none)
- IPv4: 104.18.19.125, 104.18.18.125
- Trying 104.18.19.125:443…
- Connected to api3.cursor.sh (104.18.19.125) port 443
- ALPN: curl offers h2,http/1.1
- (304) (OUT), TLS handshake, Client hello (1):
- CAfile: /etc/ssl/cert.pem
- CApath: none
- (304) (IN), TLS handshake, Server hello (2):
- (304) (IN), TLS handshake, Unknown (8):
- (304) (IN), TLS handshake, Certificate (11):
- (304) (IN), TLS handshake, CERT verify (15):
- (304) (IN), TLS handshake, Finished (20):
- (304) (OUT), TLS handshake, Finished (20):
- SSL connection using TLSv1.3 / AEAD-AES256-GCM-SHA384 / [blank] / UNDEF
- ALPN: server accepted h2
- Server certificate:
- subject: CN=api3.cursor.sh
- start date: Nov 4 02:27:46 2025 GMT
- expire date: Feb 2 03:27:40 2026 GMT
- subjectAltName: host “api3.cursor.sh” matched cert’s “api3.cursor.sh”
- issuer: C=US; O=Google Trust Services; CN=WE1
- SSL certificate verify ok.
- using HTTP/2
- [HTTP/2] [1] OPENED stream for https://api3.cursor.sh/
- [HTTP/2] [1] [:method: GET]
- [HTTP/2] [1] [:scheme: https]
- [HTTP/2] [1] [:authority: api3.cursor.sh]
- [HTTP/2] [1] [:path: /]
- [HTTP/2] [1] [user-agent: curl/8.7.1]
- [HTTP/2] [1] [accept: /]
GET / HTTP/2
Host: api3.cursor.sh
User-Agent: curl/8.7.1
Accept: /
- Request completely sent off
< HTTP/2 404
< date: Tue, 04 Nov 2025 21:09:37 GMT
< content-type: text/plain; charset=utf-8
< content-length: 31
< cf-ray: 999717ec8d05eff0-ARN
< cf-cache-status: DYNAMIC
< server: cloudflare
< - Connection #0 to host api3.cursor.sh left intact
The request could not be routed%
Developer console errors:
[backgroundComposer] Failed to fetch BGA metadata: ConnectError: [not_found] Error
POST https://api3.cursor.sh/… net::ERR_CONNECTION_RESET
This appears to be a Cloudflare routing configuration issue on Cursor’s infrastructure.
Steps to Reproduce
Steps are above.
Expected Behavior
Cursor client should connect to api3.cursor.sh
Operating System
MacOS
Current Cursor Version (Menu → About Cursor → Copy)
Version: 2.0.54
VSCode Version: 1.99.3
Commit: 7a31bffd467aa2d9adfda69076eb924e9062cb20
Date: 2025-11-03T22:40:44.657Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin x64 24.6.0
Does this stop you from using Cursor
No - Cursor works, but with this issue
