Only happening on Linux dev machine, MacOS not affected or WSL.
In my windows machine on WSL, it's running fine.
great, continue with remaining collections
⎿ API Error (Request timed out.) · Retrying in 1 seconds… (attempt 1/10)
⎿ API Error (Request timed out.) · Retrying in 1 seconds… (attempt 2/10)
⎿ API Error (Request timed out.) · Retrying in 2 seconds… (attempt 3/10)
⎿ API Error (Request timed out.) · Retrying in 5 seconds… (attempt 4/10)
⎿ API Error (Request timed out.) · Retrying in 9 seconds… (attempt 5/10)
⎿ API Error (Request timed out.) · Retrying in 17 seconds… (attempt 6/10)
⎿ API Error (Request timed out.) · Retrying in 36 seconds… (attempt 7/10)
⎿ API Error (Request timed out.) · Retrying in 40 seconds… (attempt 8/10)
⎿ API Error (Request timed out.) · Retrying in 1 seconds… (attempt 1/10)
⎿ API Error (Request timed out.) · Retrying in 1 seconds… (attempt 2/10)
⎿ API Error (Request timed out.) · Retrying in 2 seconds… (attempt 3/10)
⎿ API Error (Request timed out.) · Retrying in 4 seconds… (attempt 4/10)
⎿ API Error (Request timed out.) · Retrying in 40 seconds… (attempt 9/10)
⎿ API Error (Request timed out.) · Retrying in 8 seconds… (attempt 5/10)
⎿ API Error (Request timed out.) · Retrying in 20 seconds… (attempt 6/10)
⎿ API Error (Request timed out.) · Retrying in 34 seconds… (attempt 10/10)
⎿ API Error (Request timed out.) · Retrying in 39 seconds… (attempt 7/10)
⎿ API Error (Request timed out.) · Retrying in 39 seconds… (attempt 8/10)
⎿ API Error (Request timed out.) · Retrying in 37 seconds… (attempt 9/10)
⎿ API Error (Request timed out.) · Retrying in 35 seconds… (attempt 10/10)
Last week's Megathread: https://www.reddit.com/r/ClaudeAI/comments/1kuv6bg/megathread_for_claude_performance_discussion/
Status Report for last week: https://www.reddit.com/r/ClaudeAI/comments/1l0lk3r/status_report_claude_performance_observations/
Why a Performance Discussion Megathread?
This Megathread should make it easier for everyone to see what others are experiencing at any time by collecting all experiences. Most importantly, this will allow the subreddit to provide you a comprehensive weekly AI-generated summary report of all performance issues and experiences, maximally informative to everybody. See the previous week's summary report here https://www.reddit.com/r/ClaudeAI/comments/1l0lk3r/status_report_claude_performance_observations/
It will also free up space on the main feed to make more visible the interesting insights and constructions of those using Claude productively.
What Can I Post on this Megathread?
Use this thread to voice all your experiences (positive and negative) as well as observations regarding the current performance of Claude. This includes any discussion, questions, experiences and speculations of quota, limits, context window size, downtime, price, subscription issues, general gripes, why you are quitting, Anthropic's motives, and comparative performance with other competitors.
So What are the Rules For Contributing Here?
All the same as for the main feed (especially keep the discussion on the technology)
Give evidence of your performance issues and experiences wherever relevant. Include prompts and responses, platform you used, time it occurred. In other words, be helpful to others.
The AI performance analysis will ignore comments that don't appear credible to it or are too vague.
All other subreddit rules apply.
Do I Have to Post All Performance Issues Here and Not in the Main Feed?
Yes. This helps us track performance issues, workarounds and sentiment
As soon as I added the domain to my allowed list, the API errors stopped. To anyone else experiencing this issue, include the variables below to disable. Or, add statsig.anthropic.com to your allowed list.
DISABLE_TELEMETRY
DISABLE_ERROR_REPORTING
DISABLE_BUG_COMMAND
I can work with Claude Code CLI pretty well, but sometimes I get these API timeout errors... Now I'm asking myself if this is me or if Claude is rate limiting their service for performance reasons.
I don't know if you feel the same, but it feels like Claude is doing this intentionally to save server costs... What do you think about that?
Also sometimes it feels like Claude is rejecting kind of simple requests which feels to me like... "No I do not want to answer that... you can do this stupid simple task on your own..." which is sometimes good - Then I think "Ok you're right, I will do this myself, don't need to waste compute power on that stupid task." But mostly it's super annoying because it wastes a lot of time.
So what do YOU think? Is it ME or is it Claude?
Here is what the timeout pattern looks like with typical exponential retry logic:
⎿ API Error (Request timed out.) · Retrying in 1 seconds… (attempt 1/10) ⎿ API Error (Request timed out.) · Retrying in 1 seconds… (attempt 2/10) ⎿ API Error (Request timed out.) · Retrying in 2 seconds… (attempt 3/10) ⎿ API Error (Request timed out.) · Retrying in 5 seconds… (attempt 4/10) ⎿ API Error (Request timed out.) · Retrying in 9 seconds… (attempt 5/10) ⎿ API Error (Request timed out.) · Retrying in 17 seconds… (attempt 6/10) ⎿ API Error (Request timed out.) · Retrying in 35 seconds… (attempt 7/10) ⎿ API Error (Request timed out.) · Retrying in 39 seconds… (attempt 8/10) ⎿ API Error (Request timed out.) · Retrying in 34 seconds… (attempt 9/10) ⎿ API Error (Request timed out.) · Retrying in 39 seconds… (attempt 10/10)
Hey everyone,
Lately I’ve been getting this error almost every day:
Request timed out. Retrying in 0 seconds… (attempt 4/10)
My internet connection is fine; Codex, Cursor, and other tools work perfectly. It only happens with Claude Code.
Restarting VS Code or the network doesn’t fix it. The only thing that seems to work is restarting the PC, but even then the issue eventually comes back.
It happens on Terminal, the VS Code extension, Sonnet 4.5, or haiko models.
Claude’s status page always says “All Systems Operational.”
Is anyone else seeing this issue from time to time? Or is there a known cause/workaround?
Only happening on Linux dev machine, MacOS not affected or WSL.
In my windows machine on WSL, it's running fine.
`great, continue with remaining collections
⎿ API Error (Request timed out.) · Retrying in 1 seconds… (attempt 1/10)
⎿ API Error (Request timed out.) · Retrying in 1 seconds… (attempt 2/10)
⎿ API Error (Request timed out.) · Retrying in 2 seconds… (attempt 3/10)
⎿ API Error (Request timed out.) · Retrying in 5 seconds… (attempt 4/10)
⎿ API Error (Request timed out.) · Retrying in 9 seconds… (attempt 5/10)
⎿ API Error (Request timed out.) · Retrying in 17 seconds… (attempt 6/10)
⎿ API Error (Request timed out.) · Retrying in 36 seconds… (attempt 7/10)
⎿ API Error (Request timed out.) · Retrying in 40 seconds… (attempt 8/10)
⎿ API Error (Request timed out.) · Retrying in 1 seconds… (attempt 1/10)
⎿ API Error (Request timed out.) · Retrying in 1 seconds… (attempt 2/10)
⎿ API Error (Request timed out.) · Retrying in 2 seconds… (attempt 3/10)
⎿ API Error (Request timed out.) · Retrying in 4 seconds… (attempt 4/10)
⎿ API Error (Request timed out.) · Retrying in 40 seconds… (attempt 9/10)
⎿ API Error (Request timed out.) · Retrying in 8 seconds… (attempt 5/10)
⎿ API Error (Request timed out.) · Retrying in 20 seconds… (attempt 6/10)
⎿ API Error (Request timed out.) · Retrying in 34 seconds… (attempt 10/10)
⎿ API Error (Request timed out.) · Retrying in 39 seconds… (attempt 7/10)
⎿ API Error (Request timed out.) · Retrying in 39 seconds… (attempt 8/10)
⎿ API Error (Request timed out.) · Retrying in 37 seconds… (attempt 9/10)
⎿ API Error (Request timed out.) · Retrying in 35 seconds… (attempt 10/10)
Is anybody else having this issue? It just started happening 2 days ago. I am using WSL in VS Code. How can I resolve this? It will sometimes work, but sometimes not. I have to constantly ask it to continue, and even though I am getting an API Error it is deducting from my Athropic credit balance. 10 of these "please continue" requests cost me $0.11.
Two days in a row now Claude Code is responding with "API Error (Request timed out.)" - and this is after logging out, upgrading it, changing to API-based billing and all.
Support hasn't been of help either - it's just an AI bot that supposedly refers you to a human, but never actually does.
Anyone else getting this? I'd understand if this was a free product, but for a service that I'm paying money for, this isn't really impressive.
I have a custom program that has been working fine with Claude API for months, but today started getting the error, The data couldn’t be read because it isn’t in the correct format. At the same time, I'm also getting lots of timeout errors. It feels like the API servers are having issues.
Anyone else seeing problems with the API today?
Request to https://api.anthropic.com/v1/messages:
{
"model": "claude-3-haiku-20240307",
"temperature": 0.1,
"max_tokens": 4096,
"system": "Please respond in the form of a bulleted list. Do not include an introduction or description of the list. Format as a Markdown list with no introduction.",
"messages": [
{
"role": "user",
"content": "list 10 popular facebook groups"
}
]
}
Response message in result->error:
The data couldn’t be read because it isn’t in the correct format.
I'm encountering a weird issue with Claude API calls through an api proxy in SillyTavern. The proxy provides openai-compatible api. Here's the situation:
Problem:
Getting consistent 504 Gateway Time-out errors when trying to use Claude(haiku, sonnet, opus) through a proxy
This started happening after a recent ST update
Both streaming and non-streaming requests fail with the same error
Changing prompts and params did not help.
Console Output:
Chat completion request error: Gateway Time-out <html> <head><title>504 Gateway Time-out</title></head> <body> <center><h1>504 Gateway Time-out</h1></center> <hr><center>nginx</center> </body> </html>
What makes this strange:
The same proxy works fine with other models (non-Claude)
The same proxy + Claude combination works perfectly in other apps (ChatBox app and my own node-fetch test)
Even rolled back to an old ST commit - same issue persists
This seems to be specific to SillyTavern + Claude + this proxy combination. I've compared the POST request contents but couldn't spot any differences that might cause this.
Unfortunately, I don't have access to other Claude APIs to test if this is a ST-specific issue with Claude handling.
Has anyone else experienced something similar or might have insights on what could be causing this?