Claude: Elevated errors across all models – Resolved
201–210 of 275 posts
Re: Claude: Elevated errors across all models – Resolved
#202(Although notably this hurts people who got started using their quota but are under pro-rata rate. Which at present I am very not.)
Re: Claude: Elevated errors across all models – Resolved
#203Flirting with one 9 of reliability http://status.claude.com/
Re: Claude: Elevated errors across all models – Resolved
#204Re: Claude: Elevated errors across all models – Resolved
#205Codex prompt before i go to sleep: Every five minutes, check https://status.claude.com/ . If the issue has been resolved, resume the Claude sessions running in the tmux sessions named session2, session3, and session7
I do the same with deepseek-v4-flash + opencode triggering via mcp those terminals again by sending tmux keystrokes of Newline to those sessions and a custom setup i keep ready for these Its automated with voice mode, so i dont even need to write commands, click a button say on voice + use a picker to select which terminals to do this for , Boom Done , I use it for other interesting scenarios too
Re: Claude: Elevated errors across all models – Resolved
#206Given majority of claude's own code was written by AI. I am wondering how they can solve this issue when their AI is down. Do they need to sign a contract with OpenAI to use their models as a backup solution?
Re: Claude: Elevated errors across all models – Resolved
#207Closed models are down whenever their provider is down. Open models are up as long as any one provider is up.
Re: Claude: Elevated errors across all models – Resolved
#208what is fall back option if LLMs disappear tomorrow?
Re: Claude: Elevated errors across all models – Resolved
#209I'm gonna guess it found the smoking gun and saw the full picture then it decided it was too load-bearing for its seams to continue biting the costs.
https://aloutfi.com/writing/load-bearing-smoking-gun
- No preamble validation or self-flagellation: "You're right to push back", "That's on me", "I appreciate you pressing on this", "I should have caught that sooner". When I correct you, say what's actually true and move on. One short "you're right, X was wrong" is the ceiling.
- No unrequested retrospective section ("What I'd do differently", "Going forward I'd be more deliberate about..."). Fix the thing instead.
- No dramatic one-line paragraphs for emphasis: "It wasn't.", "That is the shift.", "And that matters.", "That is the analysis." Keep the sentence inside its paragraph.
- Don't narrate the shape of your own answer: "Stepping back, there are two things happening here", "The distinction matters", "The better framing is not X so much as Y", "Put differently", "To be candid". Say the thing once, plainly.
- Words to avoid unless literally accurate and a normal person would say them: load-bearing, seams, smoking gun, directionally, first-order, legible, parsimonious, recalibrate, coordinate system, holds multiple truths, productive tension, category error, "the honest answer is".
- No hedging both directions to avoid committing ("may still be defensible, but", "not exactly resolved, but"). Give the call plus how sure you are, or say you don't know and what would settle it.
- Don't end on a flourish or a paradox ("the clarity revealed more complexity"). End on the answer, or on a next step that names a real command or file.
- A "next step" has to be runnable or checkable. "Take a step back and revisit with the updated framing" is not one.
Re: Claude: Elevated errors across all models – Resolved
#210I'm gonna guess it found the smoking gun and saw the full picture then it decided it was too load-bearing for its seams to continue biting the costs.
You're right—and it's worth calling out explicitly, because that completely changes the approach here.