Pro Plan Rate Limit Transparency Issues - Need Specific Usage Details

Discussions
43

Update - 3:15 PM EST July 4th: Rate Limit Finally Lifted After ~26 Hours

Thank You to Everyone

First, I want to thank everyone who contributed to this thread and will continue contributing as this issue remains unresolved. The response has been overwhelming and shows this is clearly a widespread issue affecting many Pro subscribers.

Special thanks to @PabloT @dbblackdiamond @Xernive @t0ny1 @Kirai @Alexandre1 and many others including Developer_Spooky, fusiondev, D.V, Nazruden, NahNah, curtdev, decsters01, Gohrd, DesignGears, pleiadess, wtester, b_l, Liam_Baugh, Genshro, murongtianyu, qomosoloto, rahit, malcsi, datrim and everyone else who shared their experiences, screenshots, usage data, and frustrations.

Your detailed experiences, screenshots, and support have been invaluable in documenting these transparency problems and proving this affects the entire Pro subscriber community, not just individual cases.

Addressing Staff Response

@danperks - Thank you for finally responding, though your answer still doesn’t provide the specific numbers we need:

  • “Every few hours” still means nothing - Is it 4 hours? 8 hours? 24 hours? We need exact timing.
  • “Greater than your plan allows” - But what IS the plan allowance? How many Claude 4 Sonnet requests can Pro users make?
  • Auto model suggestion - Many users have explained why this doesn’t work for their workflows.

@T1000 - I’m disappointed by your dismissive response calling this “conspiracy theories.” Multiple users provided concrete evidence of shadow banning, including @Kirai’s documented experience. This isn’t conspiracy - it’s documented fact that you can verify yourself.

The thread being forwarded “to Cursor Team” after 10+ hours and multiple users confirming the same issues shows the system isn’t working as intended.

Thread Hidden Again

Once again, this thread has been hidden from public view as confirmed by @malcsi and @datrim with screenshots. The AI moderation system clearly needs adjustment if it keeps hiding legitimate customer feedback about service issues.

Please fix the AI that automatically hides posts - this is the third time this professional discussion has been suppressed.

Rate Limit Status Update

Good news: When I opened Cursor today at around 1:15 PM EST, I tested Claude 4 Sonnet and it worked without issues. The rate limit appears to have lifted after approximately 26 hours (from 11:19 AM July 3rd to ~1:15 PM July 4th).

Bad news: I’m now scared to use Cursor normally because I don’t want to hit another surprise rate limit. If these limits last an entire day (as my experience suggests), it makes Cursor unreliable for consistent development work.

This confirms that “every few hours” actually means “approximately 24 hours” - which is completely different from what the documentation states.

This Is Not Just a Forum Issue

The same problems are being widely discussed on Twitter/X. This is clearly a systemic issue affecting the entire Cursor community:

Evidence from Social Media:

These are just a few examples - there are dozens more tweets with hundreds of replies expressing the same frustrations.

What This Proves

  1. The issue is widespread - affecting users across all platforms
  2. The documentation is misleading - “every few hours” actually means ~24 hours
  3. Silent plan changes - “Unlimited” was quietly changed to “Extended limits”
  4. No transparency - users can’t track usage or predict limits
  5. Community frustration - users are actively seeking alternatives

Moving Forward

The evidence is overwhelming that this transparency issue affects a significant portion of your user base. Users are:

  • Seeking refunds and considering chargebacks
  • Switching to alternatives like Claude Code
  • Warning others about the pricing changes
  • Questioning the company’s trustworthiness

Requests for Cursor Team

  1. Provide exact reset timing - Replace “every few hours” with specific timeframes
  2. Show actual usage limits - How many Claude 4 Sonnet requests can Pro users make?
  3. Fix the AI moderation - Stop auto-hiding legitimate customer feedback
  4. Unhide this thread whenever the bot incorrectly flags it
  5. Address the community concerns shown in the Twitter evidence above

The community has provided clear, documented evidence of systemic transparency problems. The response needs to match the scale and urgency of the issue.

This thread should remain visible so other users can contribute their experiences and find solutions to these widespread problems.

17 Likes