Systematic Service Failures - $440 Refund Request After Month of Critical Bugs (WSL2)
Summary
I am a paying customer with two Claude Code subscriptions ($220 each = $440/month total). The entire month of January 2026 has been rendered unusable due to three critical, unresolved bugs. I am formally requesting a full refund and escalating publicly due to zero human response from Anthropic support.
Three Critical Bugs (All Unresolved)
Bug 1: Plugin-MCP Configuration Mismatch (#18762)
- Discovered: ~January 15, 2026
- Symptom: MCP servers repeatedly lose configuration, tools become unavailable mid-work
- Impact: Constant reconfiguration needed, work interruptions every few minutes
Bug 2: OAuth Authentication Broken in WSL2 (#20756)
- Discovered: January 25, 2026
- Symptom:
/loginfails with empty "OAuth error:" - 100% failure rate - Root Cause: WSL2 localhost ≠ Windows localhost (architectural issue)
- Impact: Complete inability to authenticate
Bug 3: API Connection Errors During Operation (#21417)
- Discovered: January 28, 2026
- Symptom: "API Error: Connection error." every 2-10 minutes during active work
- Pattern: Decreasing intervals (9m → 4m → 3m), correlated with WSL2 IP changes
- Impact: Cannot complete any meaningful work
Evidence (Error Logs)
⎿ API Error: Connection error.
✻ Brewed for 8m 46s
⎿ API Error: Connection error.
✻ Cooked for 3m 40s
⎿ API Error: Connection error.
✻ Worked for 4m 35s
⎿ API Error: Connection error.
✻ Baked for 3m 12s
⎿ Request timed out. Check your internet connection and proxy settings
Retrying in 8 seconds… (attempt 6/10)
⎿ API Error: Connection error.
✻ Churned for 9m 22s
⎿ API Error: Connection error.
✻ Worked for 3m 57s
⎿ API Error: Connection error.
✻ Baked for 3m 23s
⎿ API Error: Connection error.
✻ Sautéed for 4m 50s
⎿ API Error: Connection error.
✻ Cogitated for 14m 28s
⎿ API Error: Connection error.
✻ Brewed for 5m 17s
⎿ API Error: Connection error.
✻ Baked for 17m 7s
⎿ API Error: Connection error.
✻ Brewed for 18m 15s
⎿ API Error: Connection error.
✻ Churned for 15m 17s
⎿ API Error: Connection error.
✻ Brewed for 3m 37s
⎿ API Error: Connection error.
✻ Cogitated for 6m 2s
⎿ API Error: Connection error.
✻ Cogitated for 3m 38s
⎿ API Error: Connection error.
✻ Brewed for 3m 38s
⎿ API Error: Connection error.
✻ Brewed for 3m 36s
⎿ API Error: Connection error.
✻ Brewed for 3m 34s
⎿ API Error: Connection error.
✻ Brewed for 3m 41s
These are just a fraction of the errors from a single day. This pattern repeated every single day in January 2026.
Why I Have Two Accounts
I initially used one account ($220). When API Connection Errors became unbearable, I purchased a second account ($220) hoping the problem was account-specific. It was not. The problem is systemic in Anthropic's API infrastructure.
Financial Impact
| Item | Amount |
|------|--------|
| Account 1 (jyongchul@gmail.com) | $220 |
| Account 2 (jyongchul@naver.com) | $220 |
| Total subscription | $440 |
| Time wasted troubleshooting (55+ hours × $50/hr) | $2,750 |
| Total impact | $3,190 |
Support Experience
| Date | Action | Anthropic Response |
|------|--------|-------------------|
| Jan 25 | GitHub #20756 submitted | Bot auto-reply only |
| Jan 28 | GitHub #21417 submitted | Bot auto-reply, threatened auto-close |
| Jan 29 | Refund email to support@anthropic.com | AI bot ("Fin") response |
| Jan 29 | Rebuttal email demanding human response | AI bot response again |
| Jan 29 | Final ultimatum email | No response |
Five attempts. Zero human responses. Only AI bot auto-replies that suggest solutions requiring the very API access that is broken (Catch-22).
What I'm Requesting
- Full refund of $440 for January 2026 (both accounts)
- Human engineering response to GitHub issues #20756, #21417, #18762
- Acknowledgment that WSL2 users have experienced systematic service failures
What Happens Without Resolution
- Chargeback filing with credit card company ("services not rendered")
- Consumer protection complaints (Korea Consumer Agency + FTC)
- Public disclosure on Reddit, Hacker News, Twitter/X
Environment
- OS: WSL2 (Ubuntu) on Windows, kernel 6.6.87.2-microsoft-standard-WSL2
- Claude Code version: Latest (v2.x)
- RAM: 125GB total, 110GB available
- Network: All tests pass (ICMP ✅, DNS ✅, TLS ✅, HTTPS ✅)
Related Issues
- #18762 - Plugin-MCP Configuration Mismatch
- #20756 - OAuth Authentication Broken in WSL2
- #21417 - API Connection Errors During Operation
---
Reporter: Lee Jyong Chul (이종철)
Company: Whitehat Marketing Co., Ltd. (하얀모자마케팅)
Email: jyongchul@naver.com / jyongchul@gmail.com
Phone: +82-10-9333-2028
19 Comments
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
NOT a Duplicate - Comprehensive Refund Request Issue
This issue is NOT a duplicate of the suggested issues. Here's why:
Comparison
| Suggested Issue | Topic | This Issue (#21601) |
|----------------|-------|---------------------|
| #9950 | Individual connection issue | $440 refund request across 3 distinct bugs over entire month |
| #11810 | Specific error report | Systematic service failure with financial impact documentation |
| #14261 | Single bug report | Comprehensive case combining #18762, #20756, #21417 + refund demand |
Why This Issue is Unique
This is not a bug report. This is a formal refund request and service failure documentation that:
Anthropic Has Already Acknowledged the Problem
From Anthropic Support email (Jan 29, 2026):
This Issue Needs Human Attention
No automated bot can process a refund request. This requires a human from Anthropic's billing or support team to:
Please keep this issue OPEN.
---
Reporter: Lee Jyong Chul (이종철)
Company: Whitehat Marketing Co., Ltd.
Email: jyongchul@naver.com
Update: Both Refund Requests REJECTED (January 29, 2026)
Following Anthropic's own email instructions to use the web refund process, I submitted refund requests for both accounts. Both were automatically rejected.
Results
| Account | Status | Rejection Reason |
|---------|--------|-----------------|
| jyongchul@naver.com ($220) | ❌ REJECTED | "Previously issued refund" |
| jyongchul@gmail.com ($200) | ❌ REJECTED | "Previously issued refund" |
The Contradiction
So Anthropic:
This is a Catch-22 by design: acknowledge the problem, point to a process, but make the process automatically reject.
Previous Refunds Were for DIFFERENT Issues
Any previous refunds were for earlier, separate incidents — NOT for January 2026's month-long systematic failures across 3 critical bugs (#18762, #20756, #21417).
A prior refund for a prior problem does not negate a new refund for a new problem. Each billing period is a separate service contract.
Next Steps
Since Anthropic has:
I will now proceed with:
---
Reporter: Lee Jyong Chul (이종철)
Company: Whitehat Marketing Co., Ltd.
Update: Chargeback Notice Sent (January 29, 2026)
Formal chargeback notice has been sent to support@anthropic.com and billing@anthropic.com.
Summary of All Failed Resolution Attempts
| # | Date | Action | Result |
|---|------|--------|--------|
| 1 | Jan 25 | GitHub #20756 (OAuth broken) | No human response |
| 2 | Jan 28 | GitHub #21417 (API errors) | Bot auto-reply, threatened auto-close |
| 3 | Jan 29 | Email refund request (both accounts) | AI bot response only |
| 4 | Jan 29 | Web refund process (both accounts) | Auto-rejected ("previously issued refund") |
| 5 | Jan 29 | GitHub #21601 (comprehensive case) | Bot auto-reply, threatened auto-close |
| 6 | Jan 29 | Chargeback notice email | Sent to support + billing |
The Contradiction
48-Hour Window
Anthropic has until January 31, 2026 23:59 KST to issue direct refunds ($420 total) before chargebacks are filed.
A direct refund is better for both parties. Chargebacks carry processing fees and merchant rating impact.
Final Status Update — January 29, 2026
Email Response Analysis Complete
| Inbox | Total Anthropic Emails | Human Responses |
|-------|----------------------|-----------------|
| Naver (jyongchul@naver.com) | 22 emails since Jan 28 | 0 |
| Gmail (jyongchul@gmail.com) | 6 emails since Jan 28 | 0 |
| Total | 28 emails | 0 human responses |
Every single response was from "Fin AI Agent" — automated bot replies only.
Bot Response Pattern
Card Information Confirmed
Both accounts use the same Mastercard ending in 2238:
Next Steps
After 28 automated emails and 0 human responses over 10+ days, there is no remaining private channel to resolve this.
---
⚠️ DO NOT auto-close this issue. This is an active consumer dispute with documented evidence of systematic refund avoidance.
Status Update — January 30, 2026 (Evening KST)
Actions Taken Today
Anthropic Response Summary (as of Jan 30 evening)
| Channel | Attempts | Human Responses |
|---------|----------|-----------------|
| Email (support@anthropic.com) | 22+ | 0 |
| Web refund process | 2 (both accounts) | Auto-rejected |
| GitHub issues (4 issues) | 9 total | 0 |
| Total human responses | | 0 |
Latest Anthropic email (Jan 30, 10:34 UTC): Generic auto-reply template — "Thank you for reaching out... A member of our team will be with you as soon as we can."
Current Status
For Anthropic Staff
This can still be resolved directly. Issue a $440 refund ($220 × 2 accounts) and I will withdraw the chargeback and remove public complaints. Your own support acknowledged "multiple service disruptions throughout January 2026."
Contact: jyongchul@naver.com / jyongchul@gmail.com / +82-10-9333-2028
Update: Jan 31, 2026 — Email Server Blocking + Chargeback Filed
1. Anthropic Email Server Now Blocking Customer Emails
Emails to Anthropic support are being rejected with:
Customer cannot reach support through email. Combined with zero human responses across all channels.
2. Samsung Card Chargeback Filed (Jan 30)
3. GitHub Issues Update
opusplanmodel triggers extreme API connection errors (new finding)All channels exhausted. Awaiting chargeback resolution.
Update: Jan 31, 2026 — Complete January 2026 Failure Evidence
Email Server Blocking
Anthropic's Intercom mail server now blacklists customer IPs:
Gmail Daily Sending Limit
After sending 22+ emails requesting a human response, Gmail has also rate-limited my sending. This means Anthropic's non-responsiveness has exhausted my ability to even contact them.
Full January 2026 Error Log (Partial Sample)
From actual Claude Code sessions across multiple projects, computers, and accounts:
API Error: Connection error→ 100+ occurrences across 30+ work sessionsRequest timed out. Check your internet connection→ Retries fail up to 10/10/loginfails with "OAuth error:" (Issue #20756)opusplanmodel → Near-constant connection errors (Issue #21692).claude.jsoncorruption — auto-locked (Issue #18998)Why Two Accounts ($220 × 2 = $440)
I opened a second account (jyongchul@gmail.com) believing the errors were account-specific. The same errors occurred on both accounts, proving this is a systemic Anthropic infrastructure problem, not a user issue.
Anthropic's Own Admission
Current Status
All Related Issues
opusplanAPI connection errors + Docker conflictsI wasted my entire January 2026 dealing with Anthropic's broken service. $440 for a service that was ~90% unusable.
CRITICAL EVIDENCE: 66 Official Anthropic Incident Emails in January 2026
I have compiled all 66 incident notification emails sent by Anthropic's own status system during January 2026, proving systematic service failures across 14 separate days:
Incident Timeline (From Anthropic's Own Emails)
| Date | # Emails | Incident Description |
|------|----------|---------------------|
| Jan 6 | 1 | Errors on requests to Haiku 3.5 |
| Jan 7 | 4 | Elevated error rates on Opus 4.5 |
| Jan 9 | 3 | Increased latency on Sonnet 4.5 |
| Jan 10 | 6 | Degraded performance for API requests (structured output) + Elevated errors on Sonnet 4.5 |
| Jan 11 | 3 | Elevated error rates on Sonnet 4.5 1M context |
| Jan 13 | 11 | Elevated errors for multiple models + Increased errors Opus 4.5 |
| Jan 14 | 13 | Elevated error rates on Opus 4.5 AND Sonnet 4.5 |
| Jan 15 | 1 | Elevated error rates on Opus 4.5 and Sonnet 4.5 (continued) |
| Jan 21 | 5 | Elevated errors on Opus 4.5, Sonnet 4.5, and Sonnet 3.5 |
| Jan 22 | 4 | Elevated errors on Claude Sonnet 4.5 |
| Jan 23 | 11 | Elevated error rates on claude.ai AND API + Invalid
signatureinthinkingblock || Jan 25 | 2 | Increased rate of errors for Opus 4.5 |
| Jan 26 | 1 | Increased rate of errors for Opus 4.5 (continued) |
| Jan 27 | 1 | Elevated errors on Claude Haiku 3.5 |
Total: 66 incident emails across 14 days in a 27-day period (52% of days had incidents)
Models Affected
Refund Request History (From Email Records)
This Is Not a User Issue
All 66 incident emails are preserved as evidence for the Samsung Card chargeback dispute.
UPDATE (2026-02-01): Anthropic's Own Admission of Service Failure — Evidence for Samsung Card Chargeback
Samsung Card Chargeback Filed (Case TCKT1000160744)
I have filed a formal chargeback with Samsung Card (Mastercard) for $400 ($200 × 2 accounts). Samsung Card case number: TCKT1000160744 (filed 2026-02-01).
---
Anthropic's Official Admissions (Direct Quotes)
Anthropic's own support system sent the following admissions via email to jyongchul@naver.com:
Admission #1 (2026-01-29, from Fin AI Agent / support@mail.anthropic.com):
Admission #2 (2026-01-29, from Anthropic Support):
These admissions directly contradict the earlier claim that the only issue was a "27-minute authentication incident on January 22."
---
Evidence Summary
| Evidence | Detail |
|----------|--------|
| Incident alert emails | 66 emails from incident-notifications@anthropic.com in January 2026 |
| Days with incidents | 14 out of 27 days (52%) |
| Anthropic admission | Service disruptions confirmed by Anthropic's own support |
| Refund requests sent | 22+ emails |
| Human responses | 0 (only AI bot auto-replies) |
| Web refund attempts | Both accounts auto-rejected ("Previously issued refund") |
| Email IP blocked | Since 2026-01-31 (SMTP 550 5.7.1 rejection) |
| GitHub issues filed | 9 issues, 0 human responses from Anthropic |
---
Demand
Since Anthropic has admitted the service failures but refuses to process refunds (0 human responses after 22+ requests, email IP blocked), I am pursuing this through:
$200 × 2 accounts = $400 total refund demanded.
The original .eml email files containing Anthropic's admissions are preserved and available for Samsung Card's review upon request.
New Evidence Update (February 1, 2026): Third-Party Cross-Platform Bug Confirmation
Independent Confirmation by @ghcreative869
A third-party user (@ghcreative869) has independently confirmed the same OAuth → Subscription linking bug on native Linux (Ubuntu 25.10), proving this is NOT a platform-specific issue but a systemic Anthropic backend defect.
Key quote from third-party report:
Source: https://github.com/anthropics/claude-code/issues/20756#issuecomment-3830143498
Why This Is Decisive Evidence
| # | Point | Significance |
|---|-------|-------------|
| 1 | Independent reproduction | Third party with no relation to me reproduced the same backend bug |
| 2 | Platform-independent | Occurs on both WSL2 AND native Linux → Anthropic server-side defect confirmed |
| 3 | Paid subscriber impact |
hasExtraUsageEnabled: falseincorrectly applied to valid Max subscribers ($220/mo) || 4 | Multiple reports | Same symptoms in #17966, #6008, #12020 |
Actions Taken Today (Feb 1, 2026)
Running Totals
@anthropics/claude-code-team: You now have independent third-party confirmation that your OAuth→Subscription pipeline is broken for paying subscribers across multiple platforms. This is a billing-impacting backend defect. $440 refund for two Max accounts (jyongchul@naver.com + jyongchul@gmail.com) is the minimum appropriate response.
New Evidence: Anthropic's Own AI Bot Admits Refund Eligibility (Feb 1, 2026)
Just hours after I submitted the third-party cross-platform evidence, Anthropic's Fin AI Agent responded with a significant admission:
Source: Email from Fin AI Agent (support@mail.anthropic.com) → jyongchul@gmail.com, Feb 1, 2026 12:40 KST
Why This Matters
The Pattern
| Date | Channel | Response | Result |
|------|---------|----------|--------|
| Jan 19-31 | Email (22+) | AI bot / none | Refund refused |
| Jan 19 | Web refund | Auto-system | "Previously issued refund" — rejected |
| Jan 31 | Email | Server | IP blacklisted (550 5.7.1) |
| Feb 1 | Email | AI bot | Admits refund eligibility, demands chargeback withdrawal first |
Anthropic admits the technical issues justify a refund but refuses to connect me to a human who can actually process it. This is the definition of bad faith customer service.
Running total: Day 4, 24+ contact attempts, 0 human responses.
Samsung Card Chargeback Progress Update (Feb 2, 2026)
Samsung Card has assigned a dedicated human agent (고다영, d1226.ko@partner.samsung.com) to process the chargeback through Mastercard's dispute resolution.
Samsung Card's Confirmation:
Evidence Submitted to Samsung Card:
Status: Formal Mastercard dispute process initiated. Awaiting Anthropic's response through card network.
Update: API failures continue into February 2026
As of February 2, 2026 ~19:00 KST, API connection errors are occurring again. Claude Code is returning
API Error: Connection error.on every command, with wait times of 3-14 minutes before each failure.January failures have now extended into February. The $440 chargeback is filed with Samsung Card. Still zero human responses from Anthropic support.
Additional API Error Report (2026-02-03)
Another wave of API 500 errors just occurred:
Time: 2026-02-03 ~18:50 KST
Environment: WSL2, Claude Code
Pattern: 6 consecutive 500 errors, unable to continue work
This is ongoing evidence that Anthropic's API infrastructure remains unstable.
The chargeback dispute with Samsung Card is in progress. This additional failure will be reported to the card company as supplementary evidence of continued service failures.
---
Request IDs for Anthropic internal investigation:
Bro, you are angry lol, just chill.
they don't care about their customer, that's why they are treating you, me and others like that.
Stop losing energy, they'll have a backfire.
It's a shame, plain and simple. They bill you for a service they don't provide. That's it for me, bye bye anthropic.
Closing for now — inactive for too long. Please open a new issue if this is still relevant.
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.