Hey everyone. Like many of you, I’ve been incredibly frustrated by the recent usage limits challenges and the complete lack of response from Anthropic. I spent some time compiling a timeline and incident report based on verified social media posts, monitoring services, press coverage, and my own firsthand experience. Of course I had help from a ‘friend’ in gathering the social media details. I’m posting this here because Anthropic’s customer support infrastructure has demonstrably failed to provide any human response, and we need a centralized record of exactly what is happening to paying users. Like it or not our livelihoods and reputations are now reliant on these tools to help us be competitive and successful. I. TIMELINE OF EVENTS The Primary Incident — March 23, 2026 ~8:30 AM EDT: Multiple Claude Code users experienced session limits within 10–15 minutes of beginning work using Claude Opus in Claude Code and potentially other models. (For reference: the Max plan is marketed as delivering “up to 20x more usage per session than Pro.”) ~12:20 PM ET: Downdetector recorded a visible spike in outage reports. By 12:29 PM ET, over 2,140 unique user reports had been filed, with the majority citing problems with Claude Chat specifically. Throughout the day: Usage meters continued advancing on Max and Team accounts even after users had stopped all active work. A prominent user on X/Twitter documented his usage indicator jumping from a baseline reading to 91% within three minutes of ceasing all activity—while running zero prompts. He described the experience as a “rug pull.” Community Reaction: Multiple Reddit threads rapidly filled with similar reports: session limits reached in 10–15 minutes on Opus, full weekly limits exhausted in a single afternoon on Max ($100–$200/month) plans, and complete lockouts lasting hours with no reset information. The Status Page Discrepancy: Despite 2,140+ Downdetector reports and multiple trending threads, Anthropic’s official status page continued to display “All Systems Operational.” Current Status: As of March 24, there has been no public acknowledgment, root cause statement, or apology issued by Anthropic for the March 23 usage failures. Background — A Recurring Pattern (March 2–23) This didn’t happen in isolation. The status page and third-party monitors show a troubling pattern this month: March 2: Major global outage spanning North America, Europe, Asia, and Africa. March 14: Additional widespread outage reports. A Reddit thread accumulated over 2,000 upvotes confirming users could not access the service, while Anthropic’s automated monitors continued to show “operational.” March 16–19: Multiple separate incidents logged over four consecutive days, including elevated error rates for Sonnet, authentication failures, and response “hangs.” March 13: Anthropic launched a “double usage off-peak hours” promo. The peak/off-peak boundary (8 AM–2 PM ET) coincided almost exactly with the hours when power users and developers are most active and most likely to hit limits. II. SCOPE OF IMPACT This is not a small cohort of edge-case users. This affected paying customers across all tiers (Pro, Team, and Max). Downdetector: 2,140+ unique reports on March 23 alone. GitHub Issues: Issue #16157 (“Instantly hitting usage limits with Max subscription”) accumulated 500+ upvotes. Trustpilot: Hundreds of recent reviews describing usage limit failures, zero human support, and requests for chargebacks. III. WORKFLOW AND PRODUCTIVITY IMPACT The consequences for professional users are material: Developers using Claude Code as a primary assistant lost access mid-session, mid-PR, and mid-refactor. Agentic workflows depending on Claude Code for multi-file operations were abruptly terminated. Businesses relying on Team plan access for collaborative workflows lost billable hours and missed deadlines. My Own Experience (Team Subscriber): On March 23 at approximately 8:30 AM EDT, my Claude Code session using Opus was session-limited after roughly 15 minutes of active work. I was right in the middle of debugging complex engineering simulation code and Python scripts needed for a production project. This was followed by a lockout that persisted for hours, blocking my entire professional workflow for a large portion of the day. I contacted support via the in-product chat assistant (“finbot”) and was promised human assistance multiple times. No human contact was made. Finbot sessions repeatedly ended, froze, or dropped the conversation. Support emails I received incorrectly attributed the disruption to user-side behavior rather than a platform issue. I am a paid Team subscriber and have received zero substantive human response. IV. CUSTOMER SUPPORT FAILURES The service outage itself is arguably less damaging than the support failure that accompanied it. No accessible human support path: Anthropic routes all users through an AI chatbot. Even when the bot recognizes a problem requires human review, it provides no effective escalation path. Finbot failures: During peak distress on March 23, the support chatbot itself experienced freezes and dropped users without resolution. False promises: Both the chat interface and support emails promised human follow-up that never materialized. Status page misrepresentation: Displaying “All Systems Operational” while thousands of users are locked out actively harms trust. V. WHAT WE EXPECT FROM ANTHROPIC As paying customers, we have reasonable expectations: Acknowledge the Incident: Publicly admit the March 23 event occurred and affected paying subscribers. Silence is experienced as gaslighting. Root Cause Explanation: Was this a rate-limiter bug? Opus 4.6 token consumption? An unannounced policy change? We are a technical community; we can understand a technical explanation. Timeline and Fix Status: What was done to fix it, and what safeguards are in place now? Reparations: Paid subscribers who lost access—particularly on Max and Team plans—reasonably expect a service credit proportional to the downtime. Accessible Human Support: An AI chatbot that cannot escalate or access account data is a barrier, not a support system. Team and Max subscribers need real human support. Accurate Status Page: The persistent gap between what the status page reports and what users experience must end. Advance Notice for Changes: When token consumption rates or limits change, paying subscribers deserve advance notice, not an unexplained meter drain. Anthropic is building some of the most capable AI products in the world, and Claude Code has earned genuine loyalty. But service issues that go unacknowledged, paired with a support system that traps paying customers in a loop of broken bot promises, is not sustainable. submitted by /u/AllWhiteRubiksCube
Originally posted by u/AllWhiteRubiksCube on r/ClaudeCode