Earlier quoted context omitted.
chat.com is down for me but the models seem to still be working. But actually i noticed instability last night at 3am eastern when thinking kept repeatedly failing.
Zed is not able to access the API
Claude outage – Resolved
91–100 of 167 posts
Re: Claude outage – Resolved
#92Re: Claude outage – Resolved
#93EDIT: it was just 3.6 Flash, 3.1 Pro works it seems.
Re: Claude outage – Resolved
#94Grok models are struggling too: https://status.x.ai/ reply Looks like trouble in the SpaceX datacenters.
Re: Claude outage – Resolved
#95They are experiencing increased errors themselves.
Re: Claude outage – Resolved
#96Codex seems to also be down for some folks (me included) https://www.reddit.com/r/codex/comments/1w69ff6/whats_this_e... Their status page is hard to believe given how many folks are chiming in to report on Reddit https://status.openai.com/
Re: Claude outage – Resolved
#97Grok models are struggling too: https://status.x.ai/ reply Looks like trouble in the SpaceX datacenters.
Isn't this the classic blackout scenario? Claude goes down, then people move over to Codex, which is overwhelmed, and crashes, so people move to Grok...
Re: Claude outage – Resolved
#98Amusingly and frustratingly, this coincides with Codex also being down right now: https://www.reddit.com/r/codex/comments/1w69ff6/whats_this_e...
This of course could be a coincidence. But I suppose also that if one goes down the others get slammed, so there could be a cascade. If I were another provider I would possibly monitor Claude outages (or vice versa) as a load predictor.
Re: Claude outage – Resolved
#99A nice chance to try sonnet again, must say, I'm not missing the load bearing assumptions, honest read of the permission matrix, what's genuinely a Django convention and what's a design choice, what's worth my thinking, and what's worth being precise about. Long story short, it seems to be faster and less vocal but not much dumber (it's just my thinking partner, so I read a lot of the output as I create a large data…
My engineering has changed so much that I'm now using this time to catch up on emails and think about design and architecture for the next leg of work. (And post on HN, of course.) I would never have predicted this a year ago. I always scoffed about engineers not doing work during Github outages - I'd always find some kind of other engineering to do if PRs or builds were piling up. But during model outages, and since…
switching subs is kind of a PITA since you need to commit to a month at least