Empty Analytics Dashboard

Bug Reports
1

Describe the Bug

Hi all,

Although I’m using Cursor, my dashboard appears completely empty, yet I can see my model usage in the “Usage” section. Due to our company proxy, I’m using HTTP/1.0, which might be the cause. However, network diagnostics haven’t returned any errors so far.

Thanks!

Steps to Reproduce

Screenshots / Screen Recordings

Screenshot 2025-06-13 at 09.18.31.png
Screenshot 2025-06-13 at 09.18.31.png1876×1216 62.5 KB

Operating System

MacOS
Linux

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.1.0
VSCode Version: 1.96.2

Does this stop you from using Cursor

No - Cursor works, but with this issue

2 Likes
2

Same here. I am on the education plan if that makes any difference, but same issue - on windows. Tried on multiple networks, cleared cookies.

3

Hey, maybe it was temporary. I just checked, and everything is showing up for me. Can you confirm that this issue is resolved?

4

Hey! Unfortunately, it’s still empty for me.

5

Maybe you revoked all sessions, try logging out and logging back into your account.

6

No, because I can see all my usage in the “Usage” section, but nothing on the dashboard.

7

Any update on yours? Mine is still empty.

8

Same here! I can’t see a darn thing!

9

Hi! I want to follow up on the issue, as it appears others are experiencing the same problem. Upon reviewing the dashboard retrospectively, I noticed it’s not showing any data after May 1st; everything was fine before that.

10

The endpoint at https://www.cursor.com/api/dashboard/get-user-analytics is not returning any data for me after May 14th.

Requests with startDate after May 14th are missing the dailyMetrics array and only return this:
{"period":{"startDate":"1749967200000","endDate":"1750571999999"},"totalMembersInTeam":0}

The endpoint at https://www.cursor.com/api/dashboard/get-filtered-usage-events is working fine though.

Here’s an screenshot of how it looks when I set the dates from May 1 - June 22 on the chart.

image
image912×586 36.8 KB

11

It’s finally working again! Thanks a lot for fixing!