Cursor Tab does not work after the blackout on Google Cloud/Amazon etc

Bug Reports
1

Describe the Bug

I’ve been using Cursor for about a year probably. There was no such problems.

Couple of days ago, as you do know, there were some problems on all of cloud providers. Everybody had problems with GC, Cloudflare, AWS and so on.

Now it’s been resolved, I’m not sure when exacly.

But Cursor Tab still does not work. At all.
No errors, no warnings, I don’t know how to debug it. IT just does not show anything.

I tried to reload/upgrade/turn-off-on - nothing worked.

Sometimes it might start working when I turn on VPN in the USA, but it’s slow and it still works randomly.

Main location is Russia. Cursor website works fine. Agents work fine. Only the problem is with Tab.

Tab is enabled, obviously.

What should I do? Account is the same as here.

Steps to Reproduce

Just usual usage of Cursor. Type something and Tab should have shown you some suggestions, but it doesn’t.

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.1.2
VSCode Version: 1.96.2
Commit: 87ea1604be1f602f173c5fb67582e647fcef6c40
Date: 2025-06-13T00:30:10.108Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.4.0

Does this stop you from using Cursor

Yes - Cursor is unusable

2

I run network diagnostic in the app (no VPN). Everything is fine.

DNS:

[2025-06-16T08:39:08.818Z] Host: api2.cursor.sh
[2025-06-16T08:39:08.818Z] Servers: 192.168.31.1
[2025-06-16T08:39:08.818Z] Resolved to 54.204.102.146 in 22ms
[2025-06-16T08:39:08.820Z] Resolved to 52.0.1.37 in 1ms
[2025-06-16T08:39:08.821Z] Resolved to 52.0.1.37 in 1ms
[2025-06-16T08:39:08.823Z] Resolved to 52.0.1.37 in 2ms
[2025-06-16T08:39:08.825Z] Host: api2.cursor.sh
[2025-06-16T08:39:08.825Z] Servers: system
[2025-06-16T08:39:08.825Z] Resolved to 54.204.102.146, 52.0.1.37, 18.214.59.207, 52.3.18.101, 3.90.133.157, 34.232.184.45, 3.229.32.167, 3.234.165.166 in 2ms
[2025-06-16T08:39:08.825Z] Resolved to 54.204.102.146, 52.0.1.37, 18.214.59.207, 52.3.18.101, 3.90.133.157, 34.232.184.45, 3.229.32.167, 3.234.165.166 in 0ms
[2025-06-16T08:39:08.826Z] Resolved to 54.204.102.146, 52.0.1.37, 18.214.59.207, 52.3.18.101, 3.90.133.157, 34.232.184.45, 3.229.32.167, 3.234.165.166 in 1ms
[2025-06-16T08:39:08.826Z] Resolved to 54.204.102.146, 52.0.1.37, 18.214.59.207, 52.3.18.101, 3.90.133.157, 34.232.184.45, 3.229.32.167, 3.234.165.166 in 0ms
[2025-06-16T08:39:08.826Z] Result: true

HTTP2:

[2025-06-16T08:39:08.795Z] Start
[2025-06-16T08:39:09.198Z] Host: api2.cursor.sh
[2025-06-16T08:39:09.198Z] Protocol: h2
[2025-06-16T08:39:09.198Z] Result: true in 403ms

SSL:

[2025-06-16T08:39:08.795Z] Start
[2025-06-16T08:39:09.364Z] URL: https://api2.cursor.sh/
[2025-06-16T08:39:09.364Z] Status: 200
[2025-06-16T08:39:09.364Z] IP: 52.0.1.37
[2025-06-16T08:39:09.364Z] Issuer: C=US; O=Amazon; CN=Amazon RSA 2048 M03
[2025-06-16T08:39:09.364Z] Name: api2.cursor.sh
[2025-06-16T08:39:09.364Z] AltName: DNS:api2.cursor.sh, DNS:prod.authentication.cursor.sh, DNS:*.api2.cursor.sh
[2025-06-16T08:39:09.364Z] DNS Time: 9ms
[2025-06-16T08:39:09.364Z] Connect Time: 173ms
[2025-06-16T08:39:09.364Z] TLS Time: 217ms
[2025-06-16T08:39:09.364Z] Result: true in 569ms

API:

[2025-06-16T08:39:08.796Z] Start
[2025-06-16T08:39:09.363Z] Result: true

etc…