palcu

> On March 26–27, 2026, customers experienced elevated error rates when using Claude Opus 4.6 and Claude Sonnet 4.6. The issue was caused by a networking performance degradation within our cloud infrastructure that disrupted communication between components of our serving stack. We resolved the incident by migrating the affected workloads to healthy infrastructure, restoring normal service by 9:30 AM PT on March 27.

https://status.claude.com/incidents/b9802k1zb5l2

Comment · 7 months ago

Hey folks, I'm Palcu from the reliability engineering team at Anthropic. I just posted a small retro on the status page:

> Between 14:17 and 17:11 UTC, our primary application database experienced severely degraded I/O performance following a routine maintenance operation, causing slow or failed requests on Claude.ai and preventing new or refreshed sign-ins for Claude Code and the Console. API traffic via Claude Developer Platform was unaffected.

https://status.claude.com/incidents/jm3b4jjy2jrt

Sorry again, thanks for bearing with us as we're dealing with the influx of new users and scaling up all of our systems.

Comment · 9 months ago

Hey folks, I’m Alex from the reliability team at Anthropic. We’re sorry for the downtime and we’ve posted a mini retrospective on our status page. We’re also be doing a more in depth retrospective in the following days.

https://status.claude.com/incidents/pr6yx3bfr172

Comment · 10 months ago

Thank you! Opening an incident as soon as user impact begins is one of those instincts you develop after handling major incidents for years as an SRE at Google, and now at Anthropic.

I was also fortunate to be using Claude at that exact moment (for personal reasons), which meant I could immediately see the severity of the outage.

Comment · 10 months ago

Hello, I'm one of the engineers who worked on the incident. We have mitigated the incident as of 14:43 PT / 22:43 UTC. Sorry for the trouble.

Comment · 1 year ago

There is an external incident now.

https://status.cloud.google.com/incidents/8cY8jdUpEGGbsSMSQk...

Comment · 1 year ago

I confirm. I’m still doing reliability, but in a fun and exciting way for Claude and Anthropic.

Comment · 1 year ago

One of the problems has been that most users have requested that quotas get updated as fast as possible and that they should be consistent across regions, even for global quotas. As such people have been prioritising user experience rather than availability.

I hope the pendulum swings the other way around now in the discussion.

[disclaimer that I worked as a GCP SRE for a long time, but not left recently]

Comment · 1 year ago

seems to be OpenAI

https://news.ycombinator.com/item?id=36155028

Comment · 2 years ago

And the queries flow through.

Comment · 3 years ago

My adjacent teams in London who work in SRE on Google Cloud (GCE) got some well deserved doughnuts today for rolling out the patches on time.

Comment · 3 years ago

Yeah yeah, they've broken the old TweetDeck. You need to wait for the pop-up to ask you to transition to the new TweetDeck. Or, search on the internet for the Javascript variable you have to change in your console.

The more important question is that they've removed the Activity feed, where you could see likes from other people. Which was like a realtime feed to what your friends were doing on the website. The website is way more boring now.

Comment · 3 years ago

Life and experience, if you're looking for a short answer. For example, last year we had an outage in London[0] and the folks who worked on it learnt a lot. Now, they applied the learnings in this incident.

[0]: https://news.ycombinator.com/item?id=32161755