Claude Sonnet 5.5 incident status changes to Identified, while text still says investigation is ongoing
The Claude Status entry dated 27 October at 15:09 UTC marks the incident affecting the Claude Sonnet 5.5 model as Identified. The accompanying text still says that elevated request error rates are being investigated.
In an entry dated 27 October at 15:09 UTC, Claude Status marked the incident affecting the Claude Sonnet 5.5 model as Identified, indicating that the problem had been identified. However, the accompanying text still says that elevated request error rates are being investigated. The status label alone therefore cannot be presented as confirmation of a specific cause or a completed fix.
The morning history records an investigation into elevated error rates starting at 09:14 UTC, the deployment of a fix and monitoring of recovery at 09:38 UTC, and the issue being marked as resolved at 09:56 UTC. The later entry at 15:09 UTC reports elevated error rates again; the morning resolution announcement therefore does not confirm that the afternoon issue has been resolved.
Why it matters
Elevated error rates may interrupt work that depends on responses from the Claude Sonnet 5.5 model. The afternoon entry is essential for assessing current reliability, rather than relying solely on the morning resolution announcement.
What was added since the original report
Verified updates
-
The entry dated 27 October at 15:09 UTC marks the incident status as Identified.
Two audiences, two different impacts
What this means
For individuals
If you use the Claude Sonnet 5.5 model for work, some requests may fail and task completion may be delayed.
For a business
For business workflows that depend on the Claude Sonnet 5.5 model, the reported error rate poses a risk of automated tasks being left unfinished.
ProcessesCheck the original
Event sources
clearly official source · 1 publisher, 0 independent. We count feeds from the same owner only once.