Elevated error rates on Opus 4.6

We are currently investigating this issue.

We are currently investigating this issue.

We are currently investigating this issue.

We are currently investigating this issue.

We are currently investigating this issue.

We are currently investigating this issue.

We are currently investigating this issue.

We are currently investigating this issue.

We are currently investigating this issue.

We are currently investigating this issue.

We are currently investigating this issue.

We are currently investigating this issue.

We are currently investigating this issue.

We are continuing to investigate the ongoing incident.

We are continuing to investigate the ongoing incident.

We are continuing to investigate the ongoing incident.

We are continuing to investigate the ongoing incident.

We are continuing to investigate the ongoing incident.

We are continuing to investigate the ongoing incident.

We are continuing to investigate the ongoing incident.

We are continuing to investigate the ongoing incident.

We are continuing to investigate the ongoing incident.

We are continuing to investigate the ongoing incident.

We are continuing to investigate the ongoing incident.

We are continuing to investigate the ongoing incident.

We are continuing to investigate the ongoing incident.

Sonnet 4.6 is also showing elevated errors.

Sonnet 4.6 is also showing elevated errors.

Sonnet 4.6 is also showing elevated errors.

Sonnet 4.6 is also showing elevated errors.

Sonnet 4.6 is also showing elevated errors.

Sonnet 4.6 is also showing elevated errors.

Sonnet 4.6 is also showing elevated errors.

Sonnet 4.6 is also showing elevated errors.

Sonnet 4.6 is also showing elevated errors.

Sonnet 4.6 is also showing elevated errors.

Sonnet 4.6 is also showing elevated errors.

Sonnet 4.6 is also showing elevated errors.

Sonnet 4.6 is also showing elevated errors.

As of 5:00 PT / 12:00 UTC Sonnet 4.6 is now healthy. We are still working to fix Opus 4.6.

As of 5:00 PT / 12:00 UTC Sonnet 4.6 is now healthy. We are still working to fix Opus 4.6.

As of 5:00 PT / 12:00 UTC Sonnet 4.6 is now healthy. We are still working to fix Opus 4.6.

As of 5:00 PT / 12:00 UTC Sonnet 4.6 is now healthy. We are still working to fix Opus 4.6.

As of 5:00 PT / 12:00 UTC Sonnet 4.6 is now healthy. We are still working to fix Opus 4.6.

As of 5:00 PT / 12:00 UTC Sonnet 4.6 is now healthy. We are still working to fix Opus 4.6.

As of 5:00 PT / 12:00 UTC Sonnet 4.6 is now healthy. We are still working to fix Opus 4.6.

As of 5:00 PT / 12:00 UTC Sonnet 4.6 is now healthy. We are still working to fix Opus 4.6.

As of 5:00 PT / 12:00 UTC Sonnet 4.6 is now healthy. We are still working to fix Opus 4.6.

As of 5:00 PT / 12:00 UTC Sonnet 4.6 is now healthy. We are still working to fix Opus 4.6.

As of 5:00 PT / 12:00 UTC Sonnet 4.6 is now healthy. We are still working to fix Opus 4.6.

As of 5:00 PT / 12:00 UTC Sonnet 4.6 is now healthy. We are still working to fix Opus 4.6.

As of 5:00 PT / 12:00 UTC Sonnet 4.6 is now healthy. We are still working to fix Opus 4.6.

We have mitigated the main issue and the error rate for Opus 4.6 is hovering around 0.4% which is still high, but much better than the performance during the previous hours. We are waiting for a more permanent fix to land in the near future.

We have mitigated the main issue and the error rate for Opus 4.6 is hovering around 0.4% which is still high, but much better than the performance during the previous hours. We are waiting for a more permanent fix to land in the near future.

We have mitigated the main issue and the error rate for Opus 4.6 is hovering around 0.4% which is still high, but much better than the performance during the previous hours. We are waiting for a more permanent fix to land in the near future.

We have mitigated the main issue and the error rate for Opus 4.6 is hovering around 0.4% which is still high, but much better than the performance during the previous hours. We are waiting for a more permanent fix to land in the near future.

We have mitigated the main issue and the error rate for Opus 4.6 is hovering around 0.4% which is still high, but much better than the performance during the previous hours. We are waiting for a more permanent fix to land in the near future.

We have mitigated the main issue and the error rate for Opus 4.6 is hovering around 0.4% which is still high, but much better than the performance during the previous hours. We are waiting for a more permanent fix to land in the near future.

We have mitigated the main issue and the error rate for Opus 4.6 is hovering around 0.4% which is still high, but much better than the performance during the previous hours. We are waiting for a more permanent fix to land in the near future.

We have mitigated the main issue and the error rate for Opus 4.6 is hovering around 0.4% which is still high, but much better than the performance during the previous hours. We are waiting for a more permanent fix to land in the near future.

We have mitigated the main issue and the error rate for Opus 4.6 is hovering around 0.4% which is still high, but much better than the performance during the previous hours. We are waiting for a more permanent fix to land in the near future.

We have mitigated the main issue and the error rate for Opus 4.6 is hovering around 0.4% which is still high, but much better than the performance during the previous hours. We are waiting for a more permanent fix to land in the near future.

We have mitigated the main issue and the error rate for Opus 4.6 is hovering around 0.4% which is still high, but much better than the performance during the previous hours. We are waiting for a more permanent fix to land in the near future.

We have mitigated the main issue and the error rate for Opus 4.6 is hovering around 0.4% which is still high, but much better than the performance during the previous hours. We are waiting for a more permanent fix to land in the near future.

We have mitigated the main issue and the error rate for Opus 4.6 is hovering around 0.4% which is still high, but much better than the performance during the previous hours. We are waiting for a more permanent fix to land in the near future.

As of 6:40 PT / 13:40 UTC our error rate has returned to the baseline. We are still monitoring the current situation.

As of 6:40 PT / 13:40 UTC our error rate has returned to the baseline. We are still monitoring the current situation.

As of 6:40 PT / 13:40 UTC our error rate has returned to the baseline. We are still monitoring the current situation.

As of 6:40 PT / 13:40 UTC our error rate has returned to the baseline. We are still monitoring the current situation.

As of 6:40 PT / 13:40 UTC our error rate has returned to the baseline. We are still monitoring the current situation.

As of 6:40 PT / 13:40 UTC our error rate has returned to the baseline. We are still monitoring the current situation.

As of 6:40 PT / 13:40 UTC our error rate has returned to the baseline. We are still monitoring the current situation.

As of 6:40 PT / 13:40 UTC our error rate has returned to the baseline. We are still monitoring the current situation.

As of 6:40 PT / 13:40 UTC our error rate has returned to the baseline. We are still monitoring the current situation.

As of 6:40 PT / 13:40 UTC our error rate has returned to the baseline. We are still monitoring the current situation.

As of 6:40 PT / 13:40 UTC our error rate has returned to the baseline. We are still monitoring the current situation.

As of 6:40 PT / 13:40 UTC our error rate has returned to the baseline. We are still monitoring the current situation.

As of 6:40 PT / 13:40 UTC our error rate has returned to the baseline. We are still monitoring the current situation.

This incident has been mitigated as of 9:30 PT / 16:30 UTC.

This incident has been mitigated as of 9:30 PT / 16:30 UTC.

This incident has been mitigated as of 9:30 PT / 16:30 UTC.

This incident has been mitigated as of 9:30 PT / 16:30 UTC.

This incident has been mitigated as of 9:30 PT / 16:30 UTC.

This incident has been mitigated as of 9:30 PT / 16:30 UTC.

This incident has been mitigated as of 9:30 PT / 16:30 UTC.

This incident has been mitigated as of 9:30 PT / 16:30 UTC.

This incident has been mitigated as of 9:30 PT / 16:30 UTC.

This incident has been mitigated as of 9:30 PT / 16:30 UTC.

This incident has been mitigated as of 9:30 PT / 16:30 UTC.

This incident has been mitigated as of 9:30 PT / 16:30 UTC.

This incident has been mitigated as of 9:30 PT / 16:30 UTC.

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 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.

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 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.

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 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.

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 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.

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 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.

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 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.

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 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.

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 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.

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 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.

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 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.

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 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.

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 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.

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 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.