[BUG] max plan 5h usage filled filled 0-100% in just 5 minutes after refresh

Resolved 💬 1 comment Opened May 15, 2026 by prrcarvalho Closed Jun 14, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

Hello Anthropic Support,

I am contacting you because I believe my Claude Code usage limit is being incorrectly enforced on my account.

I am subscribed to the Claude Max plan, specifically the Max 5x plan at approximately €100/month. I was waiting for my 5-hour usage window to reset, and once it refreshed I started a completely new Claude Code chat/session with no previous context.

However, after sending only one initial message in that fresh session, the task ran for approximately 1.5 minutes and then Claude Code blocked me with a rate limit notification saying that the rate limit had been reached.

This does not seem consistent with the expected behavior of the Max 5x plan. The session had just refreshed, there was no long context, no large project history in that chat, and the task was short. Based on this, it looks like a possible account-level usage tracking or rate-limit enforcement bug.

Relevant details:

  • Product: Claude Code
  • Plan: Claude Max 5x
  • Approximate subscription price: €100/month
  • Issue: Rate limit reached almost immediately after the 5-hour usage window refreshed
  • Session context: New chat/session with no previous context
  • Action taken: Sent only one initial message
  • Approximate task duration before block: 1.5 minutes
  • Error/notification: Rate limit reached
  • Expected behavior: I should have had most of my refreshed 5-hour usage window available
  • Actual behavior: I was blocked almost immediately

Could you please investigate whether my account’s Claude Code usage quota is being calculated correctly?

In particular, I would appreciate confirmation on the following:

  1. Whether my Max 5x subscription is being correctly recognized by Claude Code.
  2. Whether my refreshed 5-hour session limit was actually available at the time of the error.
  3. Whether there is any known issue causing Max users to hit rate limits immediately after a reset.
  4. Whether any lost usage/session time can be restored or compensated.
  5. Whether there are any account/session logs that show why a single short task consumed the entire refreshed quota.

I can provide screenshots of the rate-limit message, my plan page, Claude Code /status, Claude Code version, timestamp, operating system, and terminal environment if needed.

I would appreciate escalation to a human Product Support specialist, as this appears to be a billing/plan entitlement or usage-limit enforcement issue rather than a normal usage limit.

Thank you.

What Should Happen?

Hello Anthropic Support,

I am contacting you because I believe my Claude Code usage limit is being incorrectly enforced on my account.

I am subscribed to the Claude Max plan, specifically the Max 5x plan at approximately €100/month. I was waiting for my 5-hour usage window to reset, and once it refreshed I started a completely new Claude Code chat/session with no previous context.

However, after sending only one initial message in that fresh session, the task ran for approximately 1.5 minutes and then Claude Code blocked me with a rate limit notification saying that the rate limit had been reached.

This does not seem consistent with the expected behavior of the Max 5x plan. The session had just refreshed, there was no long context, no large project history in that chat, and the task was short. Based on this, it looks like a possible account-level usage tracking or rate-limit enforcement bug.

Relevant details:

  • Product: Claude Code
  • Plan: Claude Max 5x
  • Approximate subscription price: €100/month
  • Issue: Rate limit reached almost immediately after the 5-hour usage window refreshed
  • Session context: New chat/session with no previous context
  • Action taken: Sent only one initial message
  • Approximate task duration before block: 1.5 minutes
  • Error/notification: Rate limit reached
  • Expected behavior: I should have had most of my refreshed 5-hour usage window available
  • Actual behavior: I was blocked almost immediately

Could you please investigate whether my account’s Claude Code usage quota is being calculated correctly?

In particular, I would appreciate confirmation on the following:

  1. Whether my Max 5x subscription is being correctly recognized by Claude Code.
  2. Whether my refreshed 5-hour session limit was actually available at the time of the error.
  3. Whether there is any known issue causing Max users to hit rate limits immediately after a reset.
  4. Whether any lost usage/session time can be restored or compensated.
  5. Whether there are any account/session logs that show why a single short task consumed the entire refreshed quota.

I can provide screenshots of the rate-limit message, my plan page, Claude Code /status, Claude Code version, timestamp, operating system, and terminal environment if needed.

I would appreciate escalation to a human Product Support specialist, as this appears to be a billing/plan entitlement or usage-limit enforcement issue rather than a normal usage limit.

Thank you.

Error Messages/Logs

Steps to Reproduce

Hello Anthropic Support,

I am contacting you because I believe my Claude Code usage limit is being incorrectly enforced on my account.

I am subscribed to the Claude Max plan, specifically the Max 5x plan at approximately €100/month. I was waiting for my 5-hour usage window to reset, and once it refreshed I started a completely new Claude Code chat/session with no previous context.

However, after sending only one initial message in that fresh session, the task ran for approximately 1.5 minutes and then Claude Code blocked me with a rate limit notification saying that the rate limit had been reached.

This does not seem consistent with the expected behavior of the Max 5x plan. The session had just refreshed, there was no long context, no large project history in that chat, and the task was short. Based on this, it looks like a possible account-level usage tracking or rate-limit enforcement bug.

Relevant details:

  • Product: Claude Code
  • Plan: Claude Max 5x
  • Approximate subscription price: €100/month
  • Issue: Rate limit reached almost immediately after the 5-hour usage window refreshed
  • Session context: New chat/session with no previous context
  • Action taken: Sent only one initial message
  • Approximate task duration before block: 1.5 minutes
  • Error/notification: Rate limit reached
  • Expected behavior: I should have had most of my refreshed 5-hour usage window available
  • Actual behavior: I was blocked almost immediately

Could you please investigate whether my account’s Claude Code usage quota is being calculated correctly?

In particular, I would appreciate confirmation on the following:

  1. Whether my Max 5x subscription is being correctly recognized by Claude Code.
  2. Whether my refreshed 5-hour session limit was actually available at the time of the error.
  3. Whether there is any known issue causing Max users to hit rate limits immediately after a reset.
  4. Whether any lost usage/session time can be restored or compensated.
  5. Whether there are any account/session logs that show why a single short task consumed the entire refreshed quota.

I can provide screenshots of the rate-limit message, my plan page, Claude Code /status, Claude Code version, timestamp, operating system, and terminal environment if needed.

I would appreciate escalation to a human Product Support specialist, as this appears to be a billing/plan entitlement or usage-limit enforcement issue rather than a normal usage limit.

Thank you.

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

Last version

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗