Earlier quoted context omitted.
The hamster in the datacenter died.
Alas, poor Whiskers
Claude: Elevated errors across all models – Resolved
31–40 of 275 posts
Re: Claude: Elevated errors across all models – Resolved
#32Re: Claude: Elevated errors across all models – Resolved
#33Re: Claude: Elevated errors across all models – Resolved
#34Lol, I just bought the Max plan for the first time and tried to create my first prompt in Fable, and now it’s crashing xD
Re: Claude: Elevated errors across all models – Resolved
#35I'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.
Re: Claude: Elevated errors across all models – Resolved
#36I got Opus 5 lots of HTTP 529 errors. By switching to Fable 5, it seems to be working still.
Re: Claude: Elevated errors across all models – Resolved
#37Re: Claude: Elevated errors across all models – Resolved
#38Re: Claude: Elevated errors across all models – Resolved
#39Re: Claude: Elevated errors across all models – Resolved
#40Aaaaand there goes my cache. Damnit. Edit: > We are currently investigating this issue. > Posted 1 hour ago There goes everyone's cache.
It's cached until the "/clear will save you 500k tokens" right? Claude caches for 1hr, codex for 5hrs? Anything else I'm missing?
Let’s say I’ve already worked on something, so the KV cache is already there. If I use /clear, I’ll have to do that work again.
And yes, the KV cache will remain available for one hour, but who knows when this claude api will recover? We might forget about it, and when we come back after an hour—boom - we’ll be charged for cold writes.