Subscribe to UpdatesSubscribe
Get email notifications whenever Claude creates, updates or resolves an incident.
Get text message notifications whenever Claude creates or resolves an incident.
Get incident updates and maintenance status messages in Slack.
Subscribe via Slack
By subscribing you acknowledge our Privacy Policy. In addition, you agree to the Atlassian Cloud Terms of Service and acknowledge Atlassian's Privacy Policy.
Get incident updates and maintenance status messages in Microsoft Teams channel.
By subscribing you acknowledge our Privacy Policy. In addition, you agree to the Atlassian Cloud Terms of Service and acknowledge Atlassian's Privacy Policy.
Get webhook notifications whenever Claude creates an incident, updates an incident, resolves an incident or changes a component status.
Visit our support site.
All Systems Operational
Uptime over the past 90 days. View historical uptime.
claude.ai
Operational
90 days ago
99.35
% uptime
Today
platform.claude.com (formerly console.anthropic.com)
Operational
90 days ago
99.84
% uptime
Today
Claude API (api.anthropic.com)
Operational
90 days ago
99.66
% uptime
Today
Claude Code
Operational
90 days ago
99.67
% uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Related
No incidents or maintenance related to this downtime.
Past Incidents
Jan 16, 2026
No incidents reported today.
Jan 15, 2026
Resolved -
This incident has been resolved.
Jan 15, 17:02 UTC
Jan 15, 17:02 UTC
Identified -
The issue has been identified and a fix is being implemented.
Jan 15, 07:28 UTC
Jan 15, 07:28 UTC
Jan 14, 2026
Postmortem -
Read details
Jan 14, 15:44 UTC
Jan 14, 15:44 UTC
Resolved -
This incident has been resolved.
Jan 14, 14:17 UTC
Jan 14, 14:17 UTC
Update -
We are continuing to monitor for any further issues.
Jan 14, 14:06 UTC
Jan 14, 14:06 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
Jan 14, 13:31 UTC
Jan 14, 13:31 UTC
Update -
We are continuing to work on a fix for this issue.
Jan 14, 12:41 UTC
Jan 14, 12:41 UTC
Update -
We are continuing to work on a fix for this issue.
Jan 14, 11:22 UTC
Jan 14, 11:22 UTC
Update -
We are continuing to work on a fix for this issue.
Jan 14, 10:46 UTC
Jan 14, 10:46 UTC
Update -
We are continuing to work on a fix for this issue.
Jan 14, 10:24 UTC
Jan 14, 10:24 UTC
Identified -
The issue has been identified and a fix is being implemented.
Jan 14, 10:16 UTC
Jan 14, 10:16 UTC
Update -
We are continuing to monitor for any further issues.
Jan 14, 09:52 UTC
Jan 14, 09:52 UTC
Monitoring -
A fix is being rolled out and we are monitoring the results.
Jan 14, 09:34 UTC
Jan 14, 09:34 UTC
Identified -
The issue has been identified and a fix is being implemented.
Jan 14, 08:45 UTC
Jan 14, 08:45 UTC
Investigating -
We are currently investigating this issue.
Jan 14, 08:34 UTC
Jan 14, 08:34 UTC
Jan 13, 2026
Postmortem -
Read details
Jan 13, 18:58 UTC
Jan 13, 18:58 UTC
Resolved -
This incident has been resolved.
Jan 13, 07:49 UTC
Jan 13, 07:49 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
Jan 13, 07:39 UTC
Jan 13, 07:39 UTC
Investigating -
We are currently investigating this issue.
Jan 13, 07:27 UTC
Jan 13, 07:27 UTC
Jan 12, 2026
Resolved -
This incident has been resolved.
Jan 12, 20:14 UTC
Jan 12, 20:14 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
Jan 12, 18:39 UTC
Jan 12, 18:39 UTC
Identified -
The issue has been identified and a fix is being implemented.
Jan 12, 18:19 UTC
Jan 12, 18:19 UTC
Update -
We are continuing to investigate this issue.
Jan 12, 18:18 UTC
Jan 12, 18:18 UTC
Investigating -
We are currently investigating this issue.
Jan 12, 18:10 UTC
Jan 12, 18:10 UTC
Resolved -
This incident has been resolved.
Jan 12, 20:14 UTC
Jan 12, 20:14 UTC
Identified -
The issue has been identified and a fix is being implemented.
Jan 12, 20:07 UTC
Jan 12, 20:07 UTC
Investigating -
We are currently investigating this issue.
Jan 12, 19:21 UTC
Jan 12, 19:21 UTC
Jan 11, 2026
No incidents reported.
Jan 10, 2026
Resolved -
This incident has been resolved.
Jan 10, 15:41 UTC
Jan 10, 15:41 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
Jan 10, 15:16 UTC
Jan 10, 15:16 UTC
Identified -
The issue has been identified and a fix is being implemented.
Jan 10, 15:00 UTC
Jan 10, 15:00 UTC
Update -
We are continuing to investigate this issue.
Jan 10, 14:36 UTC
Jan 10, 14:36 UTC
Investigating -
We are currently investigating this issue.
Jan 10, 14:33 UTC
Jan 10, 14:33 UTC
Resolved -
We've deployed a fix to resolve the issue.
Jan 10, 06:38 UTC
Jan 10, 06:38 UTC
Identified -
This issue has been identified and we're working on a fix.
Jan 10, 04:40 UTC
Jan 10, 04:40 UTC
Update -
We are continuing to investigate this issue.
Jan 10, 03:37 UTC
Jan 10, 03:37 UTC
Investigating -
We are currently investigating a performance issue affecting API requests that use structured outputs and strict tool use.
Jan 10, 03:37 UTC
Jan 10, 03:37 UTC
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.
Jan 10, 04:55 UTC
Jan 10, 04:55 UTC
Update -
We are continuing to work on a fix for this issue.
Jan 9, 22:52 UTC
Jan 9, 22:52 UTC
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
Jan 9, 19:59 UTC
The issue began around 10PM PST on 2026-01-08 and affected new subscriptions purchased through web
Jan 9, 19:59 UTC
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.
Jan 9, 19:41 UTC
Jan 9, 19:41 UTC
Jan 9, 2026
Jan 8, 2026
Resolved -
This incident has been resolved.
Jan 8, 21:57 UTC
Jan 8, 21:57 UTC
Identified -
The issue has been identified and a fix is being implemented.
Jan 8, 17:43 UTC
Jan 8, 17:43 UTC
Investigating -
We are currently investigating this issue.
Jan 8, 17:23 UTC
Jan 8, 17:23 UTC
Resolved -
This incident has been resolved.
Jan 8, 05:06 UTC
Jan 8, 05:06 UTC
Update -
We are continuing to investigate this issue.
Jan 7, 19:20 UTC
Jan 7, 19:20 UTC
Investigating -
We are currently investigating this issue.
Jan 7, 19:07 UTC
Jan 7, 19:07 UTC
Jan 7, 2026
Resolved -
This incident has been resolved.
Jan 7, 10:04 UTC
Jan 7, 10:04 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
Jan 7, 09:28 UTC
Jan 7, 09:28 UTC
Identified -
The issue has been identified and a fix is being implemented.
Jan 7, 09:22 UTC
Jan 7, 09:22 UTC
Investigating -
We are currently investigating this issue.
Jan 7, 09:09 UTC
Jan 7, 09:09 UTC
Jan 6, 2026
Resolved -
This incident has been resolved.
Jan 6, 00:29 UTC
Jan 6, 00:29 UTC
Investigating -
We are currently investigating this issue.
Jan 6, 00:26 UTC
Jan 6, 00:26 UTC
Jan 5, 2026
No incidents reported.
Jan 4, 2026
No incidents reported.
Jan 3, 2026
No incidents reported.
Jan 2, 2026
No incidents reported.