Unverified50% confidenceFactExact time
From the first Investigating notice to the announcement of the fix deployment (Monitoring) was about 21 minutes, with the entire incident lasting less than half an hour from detection to fix.
1
Sources
50%
Confidence
Short-term (~14 days)
Relevance
10/25/2026
First Seen
Valid until: 11/8/2026
Sources
Related Entities
Related Claims
UnverifiedThis incident lasted about 1 hour and 38 minutes from the first report to full recovery.75% similarUnverifiedOfficials said that once mitigation measures are in place, recent usage data may take about 30 minutes to display; before the full fix, usage data for the most recent approximately 30 minutes may be delayed even longer.68% similarUnverifiedAt approximately 115K context, the model requires about 21 minutes of waiting before it begins generating, decoding drops to approximately 14 tok/s, but all four integrity checks pass.66% similarUnverifiedThe author's earlier article "We tested our own AI safety checks; they caught nothing" describes: after removing the answer from the text, the model borrowed another deadline from the same article (15 days instead of 30 days), and that 15 days belonged to the institution's reply deadline rather than the individual's complaint deadline, yet the check system still passed that answer.64% similarUnverifiedProcessing time per pack is about 47 minutes, down from about 70 minutes when the second model was added; subsequent prefix caching brought it down to about 37 minutes, but missed one more answer.64% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1095589API
curl https://kongchang.com/api/v1/knowledge/claims/1095589MCP
get_claim(id=1095589)