0-token requests counted against quota during "Connection lost" retry loop (Asia-Pacific)

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Cursor CLI

Describe the Bug

During a “Connection lost. Retry attempted.” loop (~4 minutes on Feb 25, 2026), approximately 10 gemini-3-flash requests were logged in my Usage page with 0 tokens (“-”) but each counted as 1 request against my Included quota.

This is a previously confirmed bug — @amanrs confirmed it.

Network diagnosis (ss -tnp) showed TCP connections stuck in SYN-SENT to Cursor backend IPs:

SYN-SENT → 3.227.113.226:443 (no SYN-ACK)
SYN-SENT → 34.238.73.128:443 (no SYN-ACK)
SYN-SENT → 52.200.190.124:443 (no SYN-ACK)

ping confirmed 100% packet loss to these IPs. DNS resolution works fine. The issue is routing from Asia-Pacific to specific AWS us-east-1 IPs.

Related threads:

Steps to Reproduce

  1. Use Cursor CLI from Asia-Pacific with unstable routing to AWS us-east-1
  2. Start an Agent session using gemini-3-flash
  3. When network connectivity to some backend IPs is intermittent, Agent enters a “Connection lost. Retry attempted.” loop
  4. Check Usage page — multiple gemini-3-flash requests with 0 tokens (“-”) are logged, each counting as 1 request

Expected Behavior

Failed/0-token requests should not count against the monthly request quota. The billing system should distinguish between successfully processed requests and connection failures.

Screenshots / Screen Recordings

terminal_screenshot.png
terminal_screenshot.png584×551 42.2 KB

Operating System

Linux

Version Information

CLI Version 2026.02.13-41ac335
OS: linux 6.14.0-37-generic

For AI issues: which model did you use?

gemini-3-flash

For AI issues: add Request ID with privacy disabled

Session ID: cbed40eb-768b-4cd1-a22a-9719c9a522a5

Does this stop you from using Cursor

No - Cursor works, but with this issue

3

Hey, thanks for the detailed report. The network diagnostics and the session ID really helped.

This is a known issue. Failed requests or requests with 0 tokens can still count toward your quota when there are connection problems. The team is aware and is actively monitoring it.

For any requests that were counted incorrectly on your account, email [email protected] with your session ID and they can check whether they can adjust your usage.

1 Like
4

I encountered the same problem.