Unverified50% confidenceEventExact time
Officially, the fix was deployed at 05:41 UTC and the service entered the monitoring phase, and at 05:53 UTC it was formally marked as resolved.
1
Sources
50%
Confidence
Short-term (~14 days)
Relevance
10/24/2026
First Seen
Valid until: 11/7/2026
Sources
Related Entities
Related Claims
UnverifiedThe official status page first posted an "Investigating" status at 00:31 UTC on October 24, and updated it to "Resolved" about 6 minutes later (00:37 UTC).74% similarUnverifiedTwenty minutes after the first report, the team updated the status to 'Identified'; at UTC 01:35 some models (Claude Fable 5 and 5.1, Mythos 5 and 5.1) recovered, at UTC 02:11 all affected models returned to normal and entered monitoring, and at UTC 02:35 the status was marked as 'Resolved.'70% similarUnverifiedThe Anthropic status page made two updates for this incident: at 01:20 UTC it confirmed the high-frequency errors, and at 02:33 UTC it issued a resolved notice.66% similarUnverifiedOfficials marked the incident status as Resolved, indicating it had been located and fixed.63% similarUnverifiedIncident timeline: a large number of error reports was first confirmed at 14:21 UTC; it expanded to the Claude API at 14:28 UTC; mitigation measures were implemented at 14:36 UTC and the error rate dropped significantly; most services recovered at 14:59 UTC but a second independent issue was exposed (SSO and Apple login unavailable); and at 16:27 UTC all issues were announced as resolved.59% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1092565API
curl https://kongchang.com/api/v1/knowledge/claims/1092565MCP
get_claim(id=1092565)