Anthropic Status

Resolved: The fix finished deploying approximately 2 hours ago and new purchases should work correctly going forward. We're closing this statuspage for now, and will work to restore access and/or provide refunds as needed for all affected customers.

Identified: We are continuing to work on a fix for this issue.

Identified: The issue has been identified and a fix should be coming soon for new purchases. After the issue is fixed, we will issue refunds for all users who were incorrectly charged and/or properly grant subscription access.

The issue began around 10PM PST on 2026-01-08 and affected new subscriptions purchased through web

Investigating: We are investigating reports that some new customer subscriptions are charging customers without properly granting subscription access, which is also leading to accidental double or triple payments for some customers.

Resolved: This incident has been resolved.

Monitoring: A fix has been implemented and we are monitoring the results.

Identified: The issue has been identified and a fix is being implemented.

Investigating: We are continuing to investigate this issue.

Investigating: We are currently investigating this issue.

Resolved: This incident has been resolved.

Monitoring: A fix has been implemented and we are monitoring the results.

Identified: The issue has been identified and a fix is being implemented.

Investigating: We are continuing to investigate this issue.

Investigating: We are currently investigating this issue.

Resolved: This incident has been resolved.

Identified: The issue has been identified and a fix is being implemented.

Investigating: We are currently investigating this issue.

Postmortem: On January 12-13, 2026, Claude Opus 4.5 users experienced elevated error rates and degraded service for approximately 2 hours across two separate incidents. The root cause was a configuration mismatch between our inference servers that caused our load balancing system to route traffic unevenly, overloading a subset of our infrastructure. We have fixed the underlying configuration issue and added safeguards to prevent similar mismatches in the future.

Resolved: This incident has been resolved.

Monitoring: A fix has been implemented and we are monitoring the results.

Investigating: We are currently investigating this issue.

Postmortem: On January 14, 2026, users experienced errors when using Claude Opus 4.5 and Sonnet 4.5 due to a service deployment that temporarily reduced our serving capacity. We identified and rolled back the deployment, restored full capacity, and services returned to normal within approximately 4 hours. We are implementing safeguards to prevent similar deployment-related disruptions in the future.

Resolved: This incident has been resolved.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: A fix has been implemented and we are monitoring the results.

Identified: We are continuing to work on a fix for this issue.

Identified: We are continuing to work on a fix for this issue.

Identified: We are continuing to work on a fix for this issue.

Identified: We are continuing to work on a fix for this issue.

Identified: The issue has been identified and a fix is being implemented.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: A fix is being rolled out and we are monitoring the results.

Identified: The issue has been identified and a fix is being implemented.

Investigating: We are currently investigating this issue.

Resolved: This incident has been resolved.

Identified: The issue has been identified and a fix is being implemented.

Resolved: This incident has been resolved.

Monitoring: A fix has been implemented and we are monitoring the results.

Identified: The issue has been identified and a fix is being implemented.

Investigating: We are continuing to investigate this issue.

Investigating: We are currently investigating this issue.

Resolved: This incident has been resolved.

Identified: The issue has been identified and a fix is being implemented.

Investigating: We are currently investigating this issue.

Postmortem: On January 12-13, 2026, Claude Opus 4.5 users experienced elevated error rates and degraded service for approximately 2 hours across two separate incidents. The root cause was a configuration mismatch between our inference servers that caused our load balancing system to route traffic unevenly, overloading a subset of our infrastructure. We have fixed the underlying configuration issue and added safeguards to prevent similar mismatches in the future.

Resolved: This incident has been resolved.

Monitoring: A fix has been implemented and we are monitoring the results.

Investigating: We are currently investigating this issue.

Resolved: We've deployed a fix to resolve the issue.

Identified: This issue has been identified and we're working on a fix.

Investigating: We are continuing to investigate this issue.

Investigating: We are currently investigating a performance issue affecting API requests that use structured outputs and strict tool use.

Resolved: This incident has been resolved.

Monitoring: A fix has been implemented and we are monitoring the results.

Identified: The issue has been identified and a fix is being implemented.

Investigating: We are continuing to investigate this issue.

Investigating: We are currently investigating this issue.

Resolved: This incident has been resolved.

Monitoring: A fix has been implemented and we are monitoring the results.

Identified: The issue has been identified and a fix is being implemented.

Investigating: We are continuing to investigate this issue.

Investigating: We are currently investigating this issue.

Resolved: This incident has been resolved.

Identified: The issue has been identified and a fix is being implemented.

Investigating: We are currently investigating this issue.

Postmortem: On January 12-13, 2026, Claude Opus 4.5 users experienced elevated error rates and degraded service for approximately 2 hours across two separate incidents. The root cause was a configuration mismatch between our inference servers that caused our load balancing system to route traffic unevenly, overloading a subset of our infrastructure. We have fixed the underlying configuration issue and added safeguards to prevent similar mismatches in the future.

Resolved: This incident has been resolved.

Monitoring: A fix has been implemented and we are monitoring the results.

Investigating: We are currently investigating this issue.

Postmortem: On January 14, 2026, users experienced errors when using Claude Opus 4.5 and Sonnet 4.5 due to a service deployment that temporarily reduced our serving capacity. We identified and rolled back the deployment, restored full capacity, and services returned to normal within approximately 4 hours. We are implementing safeguards to prevent similar deployment-related disruptions in the future.

Resolved: This incident has been resolved.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: A fix has been implemented and we are monitoring the results.

Identified: We are continuing to work on a fix for this issue.

Identified: We are continuing to work on a fix for this issue.

Identified: We are continuing to work on a fix for this issue.

Identified: We are continuing to work on a fix for this issue.

Identified: The issue has been identified and a fix is being implemented.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: A fix is being rolled out and we are monitoring the results.

Identified: The issue has been identified and a fix is being implemented.

Investigating: We are currently investigating this issue.

Resolved: The fix finished deploying approximately 2 hours ago and new purchases should work correctly going forward. We're closing this statuspage for now, and will work to restore access and/or provide refunds as needed for all affected customers.

Identified: We are continuing to work on a fix for this issue.

Identified: The issue has been identified and a fix should be coming soon for new purchases. After the issue is fixed, we will issue refunds for all users who were incorrectly charged and/or properly grant subscription access.

The issue began around 10PM PST on 2026-01-08 and affected new subscriptions purchased through web

Investigating: We are investigating reports that some new customer subscriptions are charging customers without properly granting subscription access, which is also leading to accidental double or triple payments for some customers.

Resolved: This incident has been resolved.

Monitoring: A fix has been implemented and we are monitoring the results.

Identified: The issue has been identified and a fix is being implemented.

Investigating: We are continuing to investigate this issue.

Investigating: We are currently investigating this issue.

Resolved: This incident has been resolved.

Monitoring: A fix has been implemented and we are monitoring the results.

Identified: The issue has been identified and a fix is being implemented.

Investigating: We are continuing to investigate this issue.

Investigating: We are currently investigating this issue.

Resolved: This incident has been resolved.

Identified: The issue has been identified and a fix is being implemented.

Investigating: We are currently investigating this issue.

Postmortem: On January 12-13, 2026, Claude Opus 4.5 users experienced elevated error rates and degraded service for approximately 2 hours across two separate incidents. The root cause was a configuration mismatch between our inference servers that caused our load balancing system to route traffic unevenly, overloading a subset of our infrastructure. We have fixed the underlying configuration issue and added safeguards to prevent similar mismatches in the future.

Resolved: This incident has been resolved.

Monitoring: A fix has been implemented and we are monitoring the results.

Investigating: We are currently investigating this issue.

Postmortem: On January 14, 2026, users experienced errors when using Claude Opus 4.5 and Sonnet 4.5 due to a service deployment that temporarily reduced our serving capacity. We identified and rolled back the deployment, restored full capacity, and services returned to normal within approximately 4 hours. We are implementing safeguards to prevent similar deployment-related disruptions in the future.

Resolved: This incident has been resolved.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: A fix has been implemented and we are monitoring the results.

Identified: We are continuing to work on a fix for this issue.

Identified: We are continuing to work on a fix for this issue.

Identified: We are continuing to work on a fix for this issue.

Identified: We are continuing to work on a fix for this issue.

Identified: The issue has been identified and a fix is being implemented.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: A fix is being rolled out and we are monitoring the results.

Identified: The issue has been identified and a fix is being implemented.

Investigating: We are currently investigating this issue.