Max plan Extra Usage charges during usage reporting outage — 1M context billing change undocumented

Problem

I am a Max plan subscriber running Claude Code v2.1.33 with opus[1m] (1M context window). Over the past week, I have accumulated \$173.43 in Extra Usage charges that I believe are the result of:

1. An undocumented billing change (referenced in #28927) that silently moved 1M context model usage from Max plan coverage to Extra Usage billing
2. The active usage reporting outage (incident 9s03yn69ky6m on status.claude.com) that prevented me from detecting the charges in real-time

Evidence

• My Max plan "Weekly limits" showed only 13% usage before an unexpected reset — yet Extra Usage had accumulated to $173.43
• My weekly limits reset at the wrong time (evening instead of the displayed "Thu 6:00 AM"), consistent with #25607
• Anthropic's own support widget confirms "Status: Outage in usage reporting — Updated Feb 27, 03:04 UTC"
• The status page states: "Usage reporting has been restored across products, but is not returning data for usage that occurred after 2025-02-25 at around 18:40 UTC"
• I filed a support ticket (Conversation ID: 215473271362461), was escalated to a human agent, and received no response for 6+ hours

Related Issues

• #28927 — Silent billing change in Claude Code moving 1M context to Extra Usage
• #24727 — Max plan overage charges despite plan limits not being reached
• #29000 — Non-deterministic quota accounting / quota spike on Feb 26
• #25607 — Weekly reset timing mismatch

Environment

• Claude Code version: 2.1.33
• Model config: opus[1m] (Opus 4.6, 1M context)
• Plan: Max
• OS: macOS (Darwin, M4)

Request

1. A billing audit of my February 2026 Extra Usage charges
2. A refund of the $173.43 in charges that accrued during a confirmed usage reporting outage and appear related to an undocumented billing change
3. Transparency on what 1M context model usage is covered by the Max plan vs. what triggers Extra Usage billing
4. A response to my open support ticket (Conversation ID: 215473271362461)

Impact

The combination of an undocumented billing change + a usage reporting outage + no real-time charge notifications + a 24-hour billing delay meant I had no way to detect or prevent these charges. The Extra Usage toggle should not silently consume credits during a period when Anthropic's own billing telemetry is confirmed broken.