Discussion
All Systems Operational
lbriner: Funny that I just saw this after have "Console temporarily unavailable". I am currently at the stage that: 1) I think Claude Code is very impressive 2) I think pretty much everything else about them is terrible.* Support really poor, raised a ticket last week and have heard nothing back at all * Separation of claude.ai accounts and console accounts is super confusing * Couldn't log into the platform since I had an old org in the process of deletion even though I was invited to a new one (had to wait 7 days!) * Payments for more API credits were broken for about a week * Claude chat has really gone to s*t unless it always was. Just getting back terrible answers to simple questions. * The desktop app is a web app pretending to be a desktop app that doesn't always know it is a desktop app so you get things like, "this will only work in the desktop app". Yes I know, this is the desktop app! "Oh sorry about that but you need to use the desktop app". * mcp integration and debugging is dreadful, just a combination of generic "an error ocurred" and sometimes nothing at all * MCP only supports OAuth for shared connectors but auth key doesn't work even with "local" servers that are not necessarily local, just the config is local.You can put those on the health status!
deadbabe: While your developers are twiddling their thumbs waiting for Claude to come back online, your competitor is using alternatives to get work done right now and advancing on their go to market timeline.
mesmertech: We went from "Peak hours" meaning 2x usage plus slower to now it just does 500 errorhttps://mesmer.tools/random/is-it-peak-hours
sausagefeet: I just had to upgrade my plan because I ran out of tokens because medium effort had dementia and things only worked on high. Good to know I'm getting my money's worth...
christinetyip: It's been a bit disruptive to my workflows tbh. What alternatives are people using? Sell them to me please
mervz: I've found my brain is a good alternative.
awestroke: So are you offering api keys or...
youens: Arg. Constant.
parthdesai: Coding is solved
swader999: Waiting for 4.7....
xnx: Good time to try other models! Claude is good, but not exceptional.
cbg0: I'm glad I live in Europe, I can at least use the subscription I pay for even though the quality is worse even during off-peak hours.
ghc: It seems like Claude has taken Github's place in terms of developer reaction to it being unavailable. It's like everyone forgot how they did things 18 months ago.
Sol-: Once AGI is achieved, they'll reach the fabled superhuman "two nines" of uptime.
PunchyHamster: but the Github way of 89.09%
mrbungie: Not defending GH, but that's what tsunamies of slop can do to a system.
yoran: Anthropic support is reserved only for famous devs on X with > 100k followers.
dust42: Well, at least we know by now that Mythos is a mythos.
hobofan: Maybe Mythos identified too much uptime as a security risk.
ashirviskas: So, now that we're all here, what are you up to?
latentsea: Planning to retool the repo so that it has equal support for both Claude Code and Codex, so that outages don't throw a spanner in the works.
jakobloekke: Have anyone found good techniques to get a session out of Claude Code, so that I can point another tool at it and pick up there? This always seems to happen at the worst possible time, after having spent an hour getting deep into something – half finished edits across files, subagents running, etc.
embedding-shape: Copy-pasting previous plain-text conversation + a snippet of "inspect the current git changes, and resume where you left of" tends to do the trick, at least in Codex, worked with moving from CC, Gemini and a bunch of others.
chollida1: Shades of early twitter.Early twitter showed the fail whale as often as it showed tweets and yet it was an unstoppable juggernaut that people kept using.
robot_jesus: Same with Reddit. A decade ago it felt like they were down more than they were up. And it didn't slow down their growth trajectory. Instead, as soon as it was back there would be a thousand shitposts about "How did you all survive the outage? Did you <gasp> work?"
nafizh: OpenAI is very good in terms of not having as much outages as Anthropic, but almost all products except Codex and the pro model is unimpressive, anthropic has the opposite situation.
anonyfox: for the longest time, anthropic with claude+code was the goat and everything else was mid at best, sounds fmailiar? right now codex is just a pleasure to work with while anthropic is dropping balls left and right, hopefully the planned IPO makes a bit of fire under their asses to get their vibecoded messes sorted and the core experience competitive again. even Opus 17 won't fix this when it gets nerfed or straight up isn't reliable or too expensive for more than 3 prompts a week.
edf13: Seems to be a very regular occurrence starting around this time of day (14:30 UTC)...Claude Code returning: API Error: 500 {"type":"error","error":{"type":"api_error","message":"Internal server error"},"request_id":"---"}Over and over again!
walthamstow: US Pacific comes online while London is still working and they can't handle it. $380bn valuation btw.
jjcm: No amount of valuation can fix global supply issues for GPUs for inference unfortunately.I suspect they're highly oversubscribed, thus the reason why we're seeing them do other things to cut down on inference cost (ie changing their default thinking length).
natpalmer1776: Remember when OpenAI wasn’t allowing new subscriptions to their ChatGPT pro plans because they were oversubscribed? Pepperidge Farms remembers.
azalemeth: I literally just came to HN to ask if I was alone with the acurséd "API Error: 500 {"type":"error","error":{"type":"api_error","message":"Internal server error"},"request_id":"…"}" greeting me and telling me to get back to using my brain!
xnorswap: 500-series errors are server-side, 400 series are client side.A 500 error is almost never "just you".( 404 is a client error, because it's the client requesting a file that does not exist, a problem with the client, not the server, who is _obviously_ blameless in the file not existing. )
darkwater: > A 500 error is almost never "just you".I know you added the defensive "almost" but if I had a dollar each time I saw a 500 due to the session cookies being sent by the client that made the backend explode - for whatever root cause - well, I would have a fatter wallet.
xnorswap: Indeed, and also there's a special circle of hell reserved for anyone who dares change the interface on a public API, and forgets about client caching leading to invalid requests but only for one or two confused users in particular.Bonus points if due to the way that invalid requests are rejected, they are filtered out as invalid traffic and don't even show up as a spike in the application error logs.
nmfisher: This is why I keep a z.ai subscription as a backup.
scratchyone: is GLM genuinely comparable to claude models? haven't had a chance to test it yet.
jwithington: I think a cheat code here is to route your requests to GCP's Vertex AI, which has stronger uptimes. Can use it as a fallback or main provider.Caveats: 1) May not be economic for those on flat-rate Anthropic subscription plans 2) I work at Google.
scratchyone: does google actually host anthropic models themselves?? surprised anthropic allows that, given how notoriously crazy they are about distillation or weight leaks or any hints of their models being used in the wrong way.
scratchyone: maybe, but the response to GPU shortages being increased error rates is the concern imo. they could implement queuing or delayed response times. it's been long enough that they've had plenty of time to implement things like this, at least on their web-ui where they have full control. instead it still just errors with no further information.
hirako2000: Coding is a problem solved. Claud writes the code. I edit it. I code around it.Engineer roles dead in 6 months.
dijit: they've been getting worse and worse since way before LLMs.
skeledrew: Since they sold out.
pixel_popping: Anthropic still haven't fixed the major issue where we can't paste the token as well, and now, it starts to smell fishy, they likely did it on purpose. https://github.com/anthropics/claude-code/issues/47887
nateguchi: Is codex a good alternative? Or does Claude have a moat...
mvkel: Better at planning, worse at execution. Ultimately, creates a working product.
nateguchi: What about usage / quota?
mvkel: OpenAI sees an opportunity and is happy to set money on fire to have an edge over Anth. No issues
airstrike: If you mean Codex is better at planning, I've heard the exact opposite. I'm told it's a beast if you tell it exactly what you need as it will execute it to the T whereas Claude will push back or do its own thing either because it thinks it's wrong or because it's feeling lazy
mvkel: I use superpowers with both and have found the plan generation in codex to be a bit more thorough, so it's not the native planning mode necessarily
cdrnsf: Are they using Claude Code to author all of these systems as well?
erdaniels: Yes, as far as I've been told, they are. I imagine (hope) they run on a completely isolated version of it though.
Lord_Zero: "This should be fixed in 2.1.108" - ashwin-ant - 10 hours ago
pixel_popping: 2 days to fix a major issue where we can't login from any sort of web terminal? (even typing manually doesn't work as `n` char auto-exit the frame). All kind of CI/CD pipelines are broken if you were delogged for any reason.
obiefernandez: I'm getting Cloudflare protection screens while trying to use claude.ai web app. I wonder if they were getting DDoS'd...
trashface: Claude now the strait of hormuz for software development
ai-x: Nothing to do with coding and everything to do with capacity.In fact, this proves that there is no AI Bubble and we are massively capacity constrained (aka we under-invested in infrastructure)
AndroTux: I can't sign in. We're not at capacity for OAuth servers or relational databases. This proves that vibe coding your infrastructure is a bad idea.
ai-x: If you have this view in 2026 April, you are going to have a bad time
AndroTux: If you think AI can replace an SRE in 2026 April, I've got a bridge to sell you. I'm not saying "don't use AI." I'm saying don't turn off your brain and let AI drop your production database.
