No usage events found for the selected filters

Bug Reports
1

Describe the Bug

I’ve been monitoring usage closely, refreshing the page https://www.cursor.com/dashboard?tab=usage frequently. I had a ton of usage there. Then, within that past hour or two, it just disappeared. It shows “No usage events found for the selected filters.” no matter what date range you select.

It also shows “Usage-Based Spending this Month” as $0. It was not $0 before, and is not time for renewel.

I hope this is very nice pricing change. But, as usual, no communication. Nothing in my email explaining it.

Of course, the concern is that I’ll trigger usage based and not know it. I refresh this page a lot so I can understand when and how I trigger that. If this is a bug in showing the usage, but underneath the hood we’re still being billed for Usage Based when you hit those throttle limits, then we’re blind as can be. It was hard to make good decisions before, but impossible now if we cannot even see our usage and when and how we’re being billed for requests not being in the Pro plan.

Steps to Reproduce

Refresh the page “Cursor - The AI Code Editor”.

Expected Behavior

A very long list of usage displayed, showing for each request the cost (nothing if counted as part of Pro plan, $x.xx if Usage Base was triggered due to new pricing thresholds).

Screenshots / Screen Recordings

Screenshot from 2025-06-27 20-31-25.png
Screenshot from 2025-06-27 20-31-25.png1186×308 11.9 KB

Operating System

Linux

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.1.6
VSCode Version: 1.96.2
Commit: 5b19bac7a947f54e4caa3eb7e4c5fbf832389850
Date: 2025-06-25T02:13:33.781Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Linux x64 6.14.5-100.fc40.x86_64

Does this stop you from using Cursor

No - Cursor works, but with this issue

2

i started getting the same error on that page few minutes ago

3

Hey, it looks like this was temporary. I just checked and everything is working for me now. Can you confirm or deny that it’s working for you?

4

Yep, it came back. Guessing they were doing a backend update. You didn’t see errors in the browser network tab or console. Felt like a power outage when you’re using that page to understand the new pricing model (due to lack of clear transparency).