History

This incident has been resolved.

1. investigating Jun 17, 2026, 4:24 PM GMT+08:00

   We are currently investigating this issue.

2. identified Jun 17, 2026, 4:54 PM GMT+08:00

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

3. monitoring Jun 17, 2026, 5:37 PM GMT+08:00

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

4. resolved Jun 17, 2026, 6:03 PM GMT+08:00

   This incident has been resolved.

This incident has been resolved. Requests to Claude Opus 4.8 received elevated errors between 9:59pm PT / 04:59 UTC and 10:41pm PT / 05:41 UTC.

1. investigating Jun 17, 2026, 1:08 PM GMT+08:00

   We are currently investigating this issue.

2. monitoring Jun 17, 2026, 1:44 PM GMT+08:00

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

3. resolved Jun 17, 2026, 2:37 PM GMT+08:00

   This incident has been resolved. Requests to Claude Opus 4.8 received elevated errors between 9:59pm PT / 04:59 UTC and 10:41pm PT / 05:41 UTC.

This incident has been resolved.

1. investigating Jun 17, 2026, 8:47 AM GMT+08:00

   We are currently investigating this issue.

2. identified Jun 17, 2026, 9:52 AM GMT+08:00

   At this time, success rates for Claude Sonnet 4.6 have recovered and we are working to resolve an issue resulting in elevated errors on Opus 4.8. We will provide additional updates as soon as possible.

3. resolved Jun 17, 2026, 10:50 AM GMT+08:00

   This incident has been resolved.

This issue has been resolved. We saw elevated errors on requests to Claude Opus 4.8 between 1:45pm PT / 20:45 UTC and 1:58pm PT / 20:58 UTC.

1. investigating Jun 17, 2026, 4:50 AM GMT+08:00

   We are investigating elevated errors on requests to Claude Opus 4.8. We will provide an update as soon as possible.

2. monitoring Jun 17, 2026, 5:01 AM GMT+08:00

   We have resolved the issue resulting in elevated errors on requests to Claude Opus 4.8, and are currently monitoring closely to prevent any further issues.

3. resolved Jun 17, 2026, 6:02 AM GMT+08:00

   This issue has been resolved. We saw elevated errors on requests to Claude Opus 4.8 between 1:45pm PT / 20:45 UTC and 1:58pm PT / 20:58 UTC.

This incident has been resolved.

1. monitoring Jun 17, 2026, 3:59 AM GMT+08:00

   Opus 4.8 error rates were elevated from 12:41 PDT to approximately 12:53 PDT. The team is monitoring.

2. resolved Jun 17, 2026, 4:16 AM GMT+08:00

   This incident has been resolved.

The incident has now been resolved. We had two phases: * between 10:23 PT / 17:23 UTC to 11:00 PT / 18:00 UTC -- all Sonnet and Opus models were affected, reaching an error rate of around 10% * after 11:00 PT / 18:00 UTC and until 12:20 PT / 19:20 UTC -- Opus 4.8 had an average error rate of 10% The incident is now resolved.

1. investigating Jun 17, 2026, 1:29 AM GMT+08:00

   We are currently investigating this issue.

2. monitoring Jun 17, 2026, 2:00 AM GMT+08:00

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

3. identified Jun 17, 2026, 2:15 AM GMT+08:00

   We are still seeing errors on Opus 4.8 and Haiku 4.5.

4. identified Jun 17, 2026, 3:00 AM GMT+08:00

   We are continuing to work to resolve an elevated rate of errors on requests to Claude Opus 4.8, and will provide an additional update as soon as possible.

5. identified Jun 17, 2026, 3:08 AM GMT+08:00

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

6. monitoring Jun 17, 2026, 3:22 AM GMT+08:00

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

7. resolved Jun 17, 2026, 3:32 AM GMT+08:00

   The incident has now been resolved. We had two phases: * between 10:23 PT / 17:23 UTC to 11:00 PT / 18:00 UTC -- all Sonnet and Opus models were affected, reaching an error rate of around 10% * after 11:00 PT / 18:00 UTC and until 12:20 PT / 19:20 UTC -- Opus 4.8 had an average error rate of 10% The incident is now resolved.

All impacted services have now fully recovered.

1. identified Jun 16, 2026, 6:32 PM GMT+08:00

   We have identified that users are experiencing elevated errors for the impacted services. We are working on implementing a mitigation.

2. monitoring Jun 16, 2026, 9:32 PM GMT+08:00

   We have applied the mitigation and are monitoring the recovery.

3. resolved Jun 16, 2026, 9:48 PM GMT+08:00

   All impacted services have now fully recovered.

All impacted services have now fully recovered.

1. investigating Jun 16, 2026, 8:07 AM GMT+08:00

   We are investigating the issue for the listed services.

2. resolved Jun 16, 2026, 8:55 AM GMT+08:00

   All impacted services have now fully recovered.

We are still investigating the issue for the listed services.

1. identified Jun 16, 2026, 5:23 AM GMT+08:00

   We have identified that users are experiencing elevated errors for the impacted services. We are working on implementing a mitigation.

2. investigating Jun 16, 2026, 6:16 AM GMT+08:00

   We are investigating the issue for the listed services.

3. investigating Jun 17, 2026, 9:24 AM GMT+08:00

   We are still investigating the issue for the listed services.

All impacted services have now fully recovered.

1. identified Jun 16, 2026, 2:05 AM GMT+08:00

   We have identified that users are experiencing an error when attempting to create an account or logging in using Google OAuth for the impacted services. We are working on implementing a mitigation.

2. resolved Jun 16, 2026, 4:12 AM GMT+08:00

   All impacted services have now fully recovered.

This incident has been resolved.

1. investigating Jun 15, 2026, 2:20 PM GMT+08:00

   We are currently investigating this issue.

2. monitoring Jun 15, 2026, 4:14 PM GMT+08:00

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

3. resolved Jun 15, 2026, 4:56 PM GMT+08:00

   This incident has been resolved.

This incident has been resolved.

1. investigating Jun 13, 2026, 10:03 AM GMT+08:00

   We are currently investigating this issue.

2. resolved Jun 13, 2026, 10:11 AM GMT+08:00

   This incident has been resolved.

Learn more here: https://anthropic.com/news/fable-mythos-access

1. monitoring Jun 13, 2026, 8:50 AM GMT+08:00

   Learn more here: https://anthropic.com/news/fable-mythos-access

All impacted services have now fully recovered.

1. identified Jun 12, 2026, 6:22 AM GMT+08:00

   We have identified that some users are experiencing elevated 431 errors for the impacted services. We are working on implementing a mitigation.

2. investigating Jun 12, 2026, 6:59 AM GMT+08:00

   We are continuing to investigate the issue regarding elevated 431 errors and are working on the mitigation.

3. monitoring Jun 12, 2026, 7:25 AM GMT+08:00

   We have applied the mitigation and are monitoring the recovery.

4. resolved Jun 12, 2026, 8:47 AM GMT+08:00

   All impacted services have now fully recovered.

All impacted services have now fully recovered.

1. identified Jun 12, 2026, 4:59 AM GMT+08:00

   We have identified that users are experiencing elevated errors when using GPT 5.5 in Codex. We are working on implementing a mitigation.

2. monitoring Jun 12, 2026, 5:33 AM GMT+08:00

   We have applied the mitigation and are monitoring the recovery.

3. resolved Jun 12, 2026, 6:28 AM GMT+08:00

   All impacted services have now fully recovered.

The issue affecting various models has been resolved. Impact occurred from 09:42am PT / 16:42 UTC to 10:03am PT / 17:03 UTC.

1. investigating Jun 12, 2026, 12:54 AM GMT+08:00

   We are currently investigating this issue.

2. monitoring Jun 12, 2026, 1:27 AM GMT+08:00

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

3. resolved Jun 12, 2026, 1:56 AM GMT+08:00

   The issue affecting various models has been resolved. Impact occurred from 09:42am PT / 16:42 UTC to 10:03am PT / 17:03 UTC.

This incident has been resolved.

1. investigating Jun 11, 2026, 10:37 PM GMT+08:00

   We are currently investigating this issue.

2. identified Jun 11, 2026, 10:37 PM GMT+08:00

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

3. monitoring Jun 11, 2026, 10:58 PM GMT+08:00

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

4. resolved Jun 11, 2026, 11:01 PM GMT+08:00

   This incident has been resolved.

All impacted services have now fully recovered.

1. identified Jun 11, 2026, 9:03 PM GMT+08:00

   We have identified that some ChatGPT Free and Go users are experiencing elevated errors when using conversations. We are working to implement a mitigation.

2. resolved Jun 11, 2026, 10:04 PM GMT+08:00

   All impacted services have now fully recovered.

This incident has been resolved.

1. investigating Jun 10, 2026, 9:06 PM GMT+08:00

   We are currently investigating this issue.

2. identified Jun 10, 2026, 9:19 PM GMT+08:00

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

3. identified Jun 10, 2026, 10:59 PM GMT+08:00

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

4. monitoring Jun 11, 2026, 12:20 AM GMT+08:00

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

5. monitoring Jun 11, 2026, 1:13 AM GMT+08:00

   We are continuing to monitor Claude Haiku 4.5 towards full recovery, and at this point have seen success rates recover to close to normal operating levels. We are working to ensure there are no further issues.

6. resolved Jun 11, 2026, 1:21 AM GMT+08:00

   This incident has been resolved.

From 1:20pm PT / 20:20 UTC through 2:05pm PT / 21:05 PT, we saw elevated errors on requests to Claude Opus 4.6. This issue has been resolved.

1. investigating Jun 10, 2026, 4:32 AM GMT+08:00

   We are currently investigating this issue.

2. resolved Jun 10, 2026, 6:10 AM GMT+08:00

   From 1:20pm PT / 20:20 UTC through 2:05pm PT / 21:05 PT, we saw elevated errors on requests to Claude Opus 4.6. This issue has been resolved.

This issue has been resolved. If you are experiencing issues with selecting Claude Fable within the Claude Code Desktop application, please ensure you have updated to the latest version.

1. investigating Jun 10, 2026, 2:24 AM GMT+08:00

   We are currently investigating this issue.

2. identified Jun 10, 2026, 2:35 AM GMT+08:00

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

3. monitoring Jun 10, 2026, 4:16 AM GMT+08:00

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

4. resolved Jun 10, 2026, 5:03 AM GMT+08:00

   This issue has been resolved. If you are experiencing issues with selecting Claude Fable within the Claude Code Desktop application, please ensure you have updated to the latest version.

This issue has been resolved. Claude Opus 4.8 (Fast Mode) saw elevated errors from 7:50 PM PT / 02:50 UTC to 8:30 PM PT / 03:30 UTC.

1. investigating Jun 9, 2026, 11:13 AM GMT+08:00

   We are currently investigating this issue.

2. resolved Jun 9, 2026, 11:42 AM GMT+08:00

   This issue has been resolved. Claude Opus 4.8 (Fast Mode) saw elevated errors from 7:50 PM PT / 02:50 UTC to 8:30 PM PT / 03:30 UTC.

This issue has been resolved. Claude Opus 4.8 saw elevated errors from 3:06 PT / 22:06 UTC through 3:28 PT / 22:28 UTC.

1. investigating Jun 9, 2026, 6:20 AM GMT+08:00

   We are currently investigating this issue.

2. resolved Jun 9, 2026, 6:36 AM GMT+08:00

   This issue has been resolved. Claude Opus 4.8 saw elevated errors from 3:06 PT / 22:06 UTC through 3:28 PT / 22:28 UTC.

This issue has been resolved. Claude Opus 4.7 saw elevated errors from 2:01 PT / 21:01 UTC through 2:27 PT / 21:27 UTC.

1. investigating Jun 9, 2026, 5:05 AM GMT+08:00

   We are currently investigating this issue.

2. monitoring Jun 9, 2026, 5:35 AM GMT+08:00

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

3. resolved Jun 9, 2026, 5:56 AM GMT+08:00

   This issue has been resolved. Claude Opus 4.7 saw elevated errors from 2:01 PT / 21:01 UTC through 2:27 PT / 21:27 UTC.

The incident is now resolved. The impact started at 11:35 PT / 18:35 UTC and ended at 12:30 PT / 19:30 UTC.

1. investigating Jun 9, 2026, 3:10 AM GMT+08:00

   We are currently investigating this issue.

2. resolved Jun 9, 2026, 3:52 AM GMT+08:00

   The incident is now resolved. The impact started at 11:35 PT / 18:35 UTC and ended at 12:30 PT / 19:30 UTC.

This issue has been resolved. We saw errors affecting Opus 4.7 from 16:56–17:47 UTC.

1. investigating Jun 9, 2026, 1:15 AM GMT+08:00

   We are currently investigating this issue.

2. monitoring Jun 9, 2026, 1:55 AM GMT+08:00

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

3. resolved Jun 9, 2026, 3:22 AM GMT+08:00

   This issue has been resolved. We saw errors affecting Opus 4.7 from 16:56–17:47 UTC.

All impacted services have now fully recovered.

1. identified Jun 8, 2026, 3:19 AM GMT+08:00

   We have identified that Go users are experiencing elevated errors for the impacted services. We are working on implementing a mitigation.

2. resolved Jun 8, 2026, 3:25 AM GMT+08:00

   All impacted services have now fully recovered.

3. investigating Jun 8, 2026, 3:21 PM GMT+08:00

   We are investigating the issue for the listed services.

4. resolved Jun 8, 2026, 3:40 PM GMT+08:00

   All impacted services have now fully recovered.

All impacted services have now fully recovered.

1. identified Jun 7, 2026, 11:08 PM GMT+08:00

   We have identified the issue for the listed services. We are currently working on a mitigation.

2. resolved Jun 8, 2026, 2:06 AM GMT+08:00

   All impacted services have now fully recovered.

This incident has been resolved.

1. investigating Jun 7, 2026, 10:35 PM GMT+08:00

   We are currently investigating this issue.

2. identified Jun 7, 2026, 10:42 PM GMT+08:00

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

3. monitoring Jun 7, 2026, 10:57 PM GMT+08:00

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

4. resolved Jun 7, 2026, 11:41 PM GMT+08:00

   This incident has been resolved.

We have resolved an issue resulting in elevated errors on requests to some Claude Models.

1. investigating Jun 7, 2026, 11:31 AM GMT+08:00

   We are investigating elevated errors on requests to Claude Opus 4.7. We will provide an update as soon as possible.

2. identified Jun 7, 2026, 11:41 AM GMT+08:00

   We have identified the cause of elevated errors on requests to several Claude models and are working to resolve these issues.

3. resolved Jun 7, 2026, 12:28 PM GMT+08:00

   We have resolved an issue resulting in elevated errors on requests to some Claude Models.

From 18:12–18:55, we saw elevated errors on requests to Claude Opus 4.8. This issue has been resolved.

1. identified Jun 7, 2026, 2:37 AM GMT+08:00

   We are experiencing elevated error rates on Claude Opus 4.8. Our team has identified the issue and is working to fully resolve these errors.

2. resolved Jun 7, 2026, 3:05 AM GMT+08:00

   From 18:12–18:55, we saw elevated errors on requests to Claude Opus 4.8. This issue has been resolved.

This incident has been resolved.

1. investigating Jun 6, 2026, 5:27 PM GMT+08:00

   We are currently investigating this issue.

2. identified Jun 6, 2026, 5:43 PM GMT+08:00

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

3. monitoring Jun 6, 2026, 5:59 PM GMT+08:00

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

4. resolved Jun 6, 2026, 6:14 PM GMT+08:00

   This incident has been resolved.

All impacted services have now fully recovered.

1. identified Jun 6, 2026, 1:59 AM GMT+08:00

   We have identified that users are experiencing elevated errors for the impacted services. We are working on implementing a mitigation.

2. investigating Jun 6, 2026, 2:04 AM GMT+08:00

   We are investigating the issue for the listed services.

3. monitoring Jun 6, 2026, 3:04 AM GMT+08:00

   We have applied the mitigation and are monitoring the recovery.

4. resolved Jun 6, 2026, 3:04 AM GMT+08:00

   All impacted services have now fully recovered.

This incident has been resolved.

1. investigating Jun 5, 2026, 11:19 PM GMT+08:00

   We are currently investigating this issue.

2. identified Jun 5, 2026, 11:43 PM GMT+08:00

   We have identified the issue and we are working to mitigate the issue. Current ongoing issues with frontier models are with Opus 4.7 and Opus 4.8 and other models have recovered.

3. identified Jun 6, 2026, 12:46 AM GMT+08:00

   We are continuing to work to resolve issues affecting success rates on Opus 4.7 and 4.8, and will provide additional updates as soon as possible.

4. monitoring Jun 6, 2026, 1:13 AM GMT+08:00

   Success rates across all models have returned to expected levels. We are continuing to monitor closely to ensure no further issues will recur.

5. monitoring Jun 6, 2026, 2:27 AM GMT+08:00

   The incident started at 8:08 PT / 15:08 UTC. Recovery times per model were: Opus 4.6 - 8:25 PT / 15:25 UTC Sonnet 4.6 — 9:23 PT / 16:23 UTC Opus 4.8 — 9:59 PT / 16:59 UTC Opus 4.7 — 10:12 PT / 17:12 UTC Opus 4.5 — 10:29 PT / 17:29 UTC All models have now fully recovered.

6. resolved Jun 6, 2026, 2:28 AM GMT+08:00

   This incident has been resolved.

All impacted services have now fully recovered.

1. investigating Jun 5, 2026, 10:48 PM GMT+08:00

   We are investigating the issue for the listed services.

2. monitoring Jun 5, 2026, 11:24 PM GMT+08:00

   We have applied the mitigation and are monitoring the recovery.

3. resolved Jun 5, 2026, 11:58 PM GMT+08:00

   All impacted services have now fully recovered.

All impacted services have now fully recovered.

1. investigating Jun 5, 2026, 10:11 PM GMT+08:00

   We are investigating the issue for the listed services.

2. identified Jun 5, 2026, 10:36 PM GMT+08:00

   We have identified that users are experiencing elevated errors for the impacted services. We are working on implementing a mitigation.

3. monitoring Jun 5, 2026, 11:28 PM GMT+08:00

   We have applied the mitigation and are monitoring the recovery.

4. resolved Jun 5, 2026, 11:37 PM GMT+08:00

   All impacted services have now fully recovered.

Incorrectly suspended users have been restored access and received an email about their account and subscription information, if relevant. Impacted services have recovered.

1. investigating Jun 5, 2026, 9:26 PM GMT+08:00

   We are investigating the issue for the listed services.

2. identified Jun 5, 2026, 10:20 PM GMT+08:00

   We have identified the issue impacting account access for some users, and we are working on a fix.

3. identified Jun 5, 2026, 10:52 PM GMT+08:00

   We are still implementing the mitigation.

4. identified Jun 5, 2026, 11:19 PM GMT+08:00

   An issue caused some user accounts to be incorrectly suspended. We’re restoring account access and working through related subscription and credit impacts for affected users.

5. resolved Jun 6, 2026, 12:09 AM GMT+08:00

   All impacted services have now fully recovered.

6. monitoring Jun 6, 2026, 3:09 AM GMT+08:00

   We’ve restored account access for users. The team is working through related subscription and credit impacts for affected users.

7. monitoring Jun 6, 2026, 3:47 AM GMT+08:00

   The team is still working through related subscription and credit impacts for affected users. Impacted users will be receiving an email shortly.

8. monitoring Jun 6, 2026, 4:53 AM GMT+08:00

   All users impacted should have received an email with more information. The team is monitoring for additional changes.

9. monitoring Jun 6, 2026, 5:19 AM GMT+08:00

   The team is uncovering some additional impacted users and is still working through related subscription and credit impacts for affected users. Impacted users will be receiving an email shortly.

10. resolved Jun 6, 2026, 2:16 PM GMT+08:00

    Incorrectly suspended users have been restored access and received an email about their account and subscription information, if relevant. Impacted services have recovered.

All impacted services have now fully recovered.

1. identified Jun 5, 2026, 3:12 AM GMT+08:00

   We have identified that users are experiencing elevated errors for the impacted services. We are working on implementing a mitigation.

2. monitoring Jun 5, 2026, 3:36 AM GMT+08:00

   We have applied the mitigation and are monitoring the recovery.

3. resolved Jun 5, 2026, 3:52 AM GMT+08:00

   All impacted services have now fully recovered.

All impacted services have now fully recovered.

1. identified Jun 4, 2026, 10:57 AM GMT+08:00

   We have identified that users are experiencing elevated latency for the impacted services. We are working on implementing a mitigation.

2. resolved Jun 4, 2026, 12:37 PM GMT+08:00

   All impacted services have now fully recovered.

This incident has been resolved.

1. investigating Jun 3, 2026, 3:10 PM GMT+08:00

   We are currently investigating this issue.

2. monitoring Jun 3, 2026, 3:28 PM GMT+08:00

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

3. resolved Jun 3, 2026, 3:38 PM GMT+08:00

   This incident has been resolved.

Incident resolved.

1. investigating Jun 3, 2026, 12:58 PM GMT+08:00

   Elevated error rates on Codex, ChatGPT and Responses API

2. investigating Jun 3, 2026, 1:11 PM GMT+08:00

   Elevated error rates on Codex, ChatGPT and Responses API

3. investigating Jun 3, 2026, 1:12 PM GMT+08:00

   Elevated error rates on Codex, ChatGPT and Responses API

4. investigating Jun 3, 2026, 1:22 PM GMT+08:00

   Elevated error rates on Codex, ChatGPT and Responses API

5. investigating Jun 3, 2026, 1:42 PM GMT+08:00

   Elevated error rates on Codex, ChatGPT and Responses API

6. investigating Jun 3, 2026, 2:16 PM GMT+08:00

   Elevated error rates on Codex, ChatGPT and Responses API

7. investigating Jun 3, 2026, 2:34 PM GMT+08:00

   Elevated error rates on Codex, ChatGPT and Responses API

8. investigating Jun 3, 2026, 2:50 PM GMT+08:00

   Elevated error rates on Codex, ChatGPT and Responses API

9. investigating Jun 3, 2026, 3:11 PM GMT+08:00

   Elevated error rates on Codex, ChatGPT and Responses API

10. monitoring Jun 3, 2026, 3:16 PM GMT+08:00

    Monitoring recovery.

11. monitoring Jun 3, 2026, 3:55 PM GMT+08:00

    Monitoring recovery.

12. monitoring Jun 3, 2026, 5:20 PM GMT+08:00

    Monitoring recovery.

13. monitoring Jun 3, 2026, 6:21 PM GMT+08:00

    Monitoring recovery.

14. resolved Jun 3, 2026, 7:09 PM GMT+08:00

    Incident resolved.

This incident has been resolved.

1. investigating Jun 3, 2026, 12:17 PM GMT+08:00

   We have identified an issue which is resulting in some Claude Code services being degraded. As a result of this issue, users will see issues with Claude Code security reviews, code reviews, routines and some Claude Code web sessions. Our engineers are working to resolve these issues as soon as possible.

2. resolved Jun 3, 2026, 3:36 PM GMT+08:00

   This incident has been resolved.

Incident resolved.

1. monitoring Jun 3, 2026, 7:35 AM GMT+08:00

   Monitoring recovery.

2. resolved Jun 3, 2026, 8:13 AM GMT+08:00

   Incident resolved.

Incident resolved.

1. identified Jun 3, 2026, 7:28 AM GMT+08:00

   Issue identified.

2. monitoring Jun 3, 2026, 7:36 AM GMT+08:00

   Monitoring recovery.

3. resolved Jun 3, 2026, 8:14 AM GMT+08:00

   Incident resolved.

Incident resolved.

1. investigating Jun 2, 2026, 8:04 PM GMT+08:00

   Guest users are experiencing elevated error rate when using ChatGPT conversations.

2. monitoring Jun 2, 2026, 8:47 PM GMT+08:00

   Monitoring recovery.

3. resolved Jun 2, 2026, 9:16 PM GMT+08:00

   Incident resolved.

This incident has been resolved.

1. investigating Jun 2, 2026, 2:04 PM GMT+08:00

   We are currently investigating this issue.

2. identified Jun 2, 2026, 2:39 PM GMT+08:00

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

3. identified Jun 2, 2026, 5:33 PM GMT+08:00

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

4. monitoring Jun 2, 2026, 6:42 PM GMT+08:00

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

5. resolved Jun 2, 2026, 7:49 PM GMT+08:00

   This incident has been resolved.

This issue has been resolved.

1. investigating Jun 2, 2026, 2:28 AM GMT+08:00

   We are investigating elevated errors on requests to Claude Sonnet 4.6. We will provide an update as soon as possible.

2. resolved Jun 2, 2026, 3:06 AM GMT+08:00

   This issue has been resolved.

Incident resolved.

1. identified Jun 2, 2026, 12:26 AM GMT+08:00

   Issue identified.

2. monitoring Jun 2, 2026, 12:56 AM GMT+08:00

   Monitoring recovery.

3. resolved Jun 2, 2026, 1:28 AM GMT+08:00

   Incident resolved.

This incident has been resolved.

1. identified Jun 1, 2026, 10:40 PM GMT+08:00

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

2. monitoring Jun 1, 2026, 11:21 PM GMT+08:00

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

3. resolved Jun 1, 2026, 11:41 PM GMT+08:00

   This incident has been resolved.

This incident has been resolved.

1. investigating Jun 1, 2026, 8:15 PM GMT+08:00

   We are currently investigating this issue.

2. identified Jun 1, 2026, 8:19 PM GMT+08:00

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

3. monitoring Jun 1, 2026, 8:48 PM GMT+08:00

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

4. resolved Jun 1, 2026, 9:33 PM GMT+08:00

   This incident has been resolved.

This incident has been resolved.

1. investigating Jun 1, 2026, 5:08 PM GMT+08:00

   We are currently investigating this issue.

2. monitoring Jun 1, 2026, 5:13 PM GMT+08:00

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

3. monitoring Jun 1, 2026, 5:17 PM GMT+08:00

   We are continuing to monitor for any further issues.

4. resolved Jun 1, 2026, 5:28 PM GMT+08:00

   This incident has been resolved.

This incident has been resolved.

1. investigating Jun 1, 2026, 2:48 PM GMT+08:00

   We are currently investigating this issue.

2. monitoring Jun 1, 2026, 3:08 PM GMT+08:00

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

3. resolved Jun 1, 2026, 3:22 PM GMT+08:00

   This incident has been resolved.

Registration SMS delivery has recovered.

1. investigating May 31, 2026, 4:22 PM GMT+08:00

   We are investigating registration SMS delivery issues.

2. monitoring May 31, 2026, 5:01 PM GMT+08:00

   A fix has been applied. We are monitoring recovery.

3. resolved May 31, 2026, 5:07 PM GMT+08:00

   Registration SMS delivery has recovered.

This incident has been resolved.

1. investigating May 31, 2026, 6:58 AM GMT+08:00

   We are currently investigating this issue.

2. resolved May 31, 2026, 8:16 AM GMT+08:00

   This incident has been resolved.

This issue has been resolved.

1. investigating May 30, 2026, 2:35 AM GMT+08:00

   We are investigating elevated errors on requests to Claude Opus 4.8. We will provide an update as soon as possible.

2. monitoring May 30, 2026, 2:55 AM GMT+08:00

   A fix has been deployed for Claude Opus 4.8 and success rates have returned to normal. Users saw elevated errors on requests to the model from 18:16–18:42 UTC.

3. resolved May 30, 2026, 3:12 AM GMT+08:00

   This issue has been resolved.

Incident resolved.

1. investigating May 29, 2026, 9:20 PM GMT+08:00

   Users May Experience Issues Accessing ChatGPT

2. resolved May 29, 2026, 9:28 PM GMT+08:00

   Incident resolved.

This incident has been resolved.

1. investigating May 29, 2026, 4:30 PM GMT+08:00

   We are currently investigating this issue.

2. monitoring May 29, 2026, 4:39 PM GMT+08:00

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

3. resolved May 29, 2026, 4:45 PM GMT+08:00

   This incident has been resolved.

Incident resolved.

1. investigating May 29, 2026, 11:18 AM GMT+08:00

   Users may encounter issues with conversations

2. monitoring May 29, 2026, 11:29 AM GMT+08:00

   Monitoring recovery.

3. resolved May 29, 2026, 12:58 PM GMT+08:00

   Incident resolved.

Incident resolved.

1. investigating May 29, 2026, 11:12 AM GMT+08:00

   Users may encounter issues logging in or creating an account

2. monitoring May 29, 2026, 11:28 AM GMT+08:00

   Monitoring recovery.

3. resolved May 29, 2026, 12:57 PM GMT+08:00

   Incident resolved.

Incident resolved.

1. investigating May 29, 2026, 4:46 AM GMT+08:00

   Business plan subscription checkout issues on web and mobile web

2. monitoring May 29, 2026, 8:09 AM GMT+08:00

   Monitoring recovery.

3. resolved May 29, 2026, 9:29 AM GMT+08:00

   Incident resolved.

The issue affecting Claude services has been resolved. Impact occurred from 18:27 UTC to 19:05 UTC.

1. identified May 29, 2026, 3:04 AM GMT+08:00

   We are currently experiencing issues with billing and subscription management on claude.ai and the Anthropic Console. Users may see errors when viewing subscription details, payment methods, or attempting to upgrade or change plans. Chat and API access are not affected. We have identified the cause and are working on a fix.

2. monitoring May 29, 2026, 3:17 AM GMT+08:00

   A fix has been deployed for the issue affecting Claude services and we are monitoring for recovery.

3. resolved May 29, 2026, 3:23 AM GMT+08:00

   The issue affecting Claude services has been resolved. Impact occurred from 18:27 UTC to 19:05 UTC.

Incident resolved.

1. resolved May 28, 2026, 1:27 PM GMT+08:00

   Incident resolved.

This incident has been resolved.

1. investigating May 28, 2026, 4:38 PM GMT+08:00

   We are currently investigating this issue.

2. resolved May 28, 2026, 5:17 PM GMT+08:00

   This incident has been resolved.

Incident resolved.

1. identified May 28, 2026, 1:57 AM GMT+08:00

   Issue identified.

2. investigating May 28, 2026, 8:14 AM GMT+08:00

   Codex Context Compaction Latency

3. investigating May 28, 2026, 9:47 AM GMT+08:00

   Codex Context Compaction Latency

4. identified May 28, 2026, 10:31 AM GMT+08:00

   Issue identified.

5. monitoring May 28, 2026, 11:09 AM GMT+08:00

   Monitoring recovery.

6. resolved May 28, 2026, 2:59 PM GMT+08:00

   Incident resolved.

Incident resolved.

1. investigating May 28, 2026, 12:24 AM GMT+08:00

   Android ChatGPT Business users having trouble switching workspaces

2. resolved May 28, 2026, 11:59 AM GMT+08:00

   Incident resolved.

Incident resolved.

1. investigating May 27, 2026, 10:47 PM GMT+08:00

   Elevated Latency and Errors on API

2. investigating May 27, 2026, 11:21 PM GMT+08:00

   Elevated Latency and Errors on API

3. identified May 27, 2026, 11:45 PM GMT+08:00

   Issue identified.

4. monitoring May 27, 2026, 11:59 PM GMT+08:00

   Monitoring recovery.

5. resolved May 28, 2026, 1:12 AM GMT+08:00

   Incident resolved.

6. monitoring May 28, 2026, 1:54 AM GMT+08:00

   Monitoring recovery.

7. resolved May 28, 2026, 4:06 AM GMT+08:00

   Incident resolved.

This incident has been resolved.

1. investigating May 27, 2026, 4:04 PM GMT+08:00

   We are currently investigating this issue.

2. monitoring May 27, 2026, 5:11 PM GMT+08:00

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

3. resolved May 27, 2026, 5:41 PM GMT+08:00

   This incident has been resolved.

This incident has been resolved.

1. investigating May 27, 2026, 1:43 PM GMT+08:00

   We are currently investigating this issue.

2. monitoring May 27, 2026, 2:01 PM GMT+08:00

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

3. resolved May 27, 2026, 2:40 PM GMT+08:00

   This incident has been resolved.

Incident resolved.

1. identified May 27, 2026, 4:27 AM GMT+08:00

   Issue identified.

2. resolved May 27, 2026, 4:30 AM GMT+08:00

   Incident resolved.

Incident resolved.

1. investigating May 26, 2026, 9:59 PM GMT+08:00

   Login issues for FedRAMP users who recently logged out

2. identified May 26, 2026, 10:20 PM GMT+08:00

   Issue identified.

3. monitoring May 27, 2026, 1:29 PM GMT+08:00

   Monitoring recovery.

4. resolved May 27, 2026, 2:01 PM GMT+08:00

   Incident resolved.

This incident has been resolved.

1. investigating May 26, 2026, 9:56 AM GMT+08:00

   We are currently investigating this issue.

2. resolved May 26, 2026, 1:19 PM GMT+08:00

   This incident has been resolved.

This incident has been resolved.

1. monitoring May 25, 2026, 6:32 PM GMT+08:00

   We had an elevated error rate on Opus 4.7 from 6:30 UTC until 10:30 UTC

2. resolved May 25, 2026, 6:39 PM GMT+08:00

   This incident has been resolved.

Incident resolved.

1. investigating May 23, 2026, 12:37 AM GMT+08:00

   Increase in users hitting Codex rate limits

2. monitoring May 23, 2026, 3:16 AM GMT+08:00

   Monitoring recovery.

3. monitoring May 23, 2026, 3:16 AM GMT+08:00

   Monitoring recovery.

4. resolved May 23, 2026, 6:58 PM GMT+08:00

   Incident resolved.

This incident has been resolved.

1. investigating May 22, 2026, 6:17 PM GMT+08:00

   We are currently investigating this issue.

2. monitoring May 22, 2026, 6:26 PM GMT+08:00

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

3. resolved May 22, 2026, 6:31 PM GMT+08:00

   This incident has been resolved.

This issue has been resolved.

1. investigating May 22, 2026, 12:16 PM GMT+08:00

   We are currently investigating this issue.

2. identified May 22, 2026, 12:40 PM GMT+08:00

   We have identified an issue resulting in elevated error rates, primarily on Claude Opus 4.7 and Sonnet 4.6. We are working to resolve these issues, and will provide additional updates as soon as possible.

3. identified May 22, 2026, 1:25 PM GMT+08:00

   We are continuing to work to fully resolve issues impacting Claude Opus 4.7, and Sonnet 4.6. At this time, success rates on Claude Opus 4.7 have stabilized. We will provide additional updates shortly.

4. monitoring May 22, 2026, 1:53 PM GMT+08:00

   We have seen success rates on Claude Opus 4.7 and Sonnet 4.6 return to normal. We are monitoring closely to ensure no further issues, and will provide an additional update shortly.

5. monitoring May 22, 2026, 2:17 PM GMT+08:00

   We are currently working to resolve some additional errors impacting Claude Opus 4.7 and Haiku 4.5, we will provide an additional update shortly.

6. monitoring May 22, 2026, 2:32 PM GMT+08:00

   We are monitoring recovery on Claude Opus 4.7, and working to fully resolve remaining errors impacting Haiku 4.5. We will provide additional updates shortly.

7. resolved May 22, 2026, 4:50 PM GMT+08:00

   This issue has been resolved.

Incident resolved.

1. identified May 22, 2026, 6:05 AM GMT+08:00

   Issue identified.

2. monitoring May 22, 2026, 6:25 AM GMT+08:00

   Monitoring recovery.

3. monitoring May 22, 2026, 6:57 AM GMT+08:00

   Monitoring recovery.

4. resolved May 22, 2026, 7:22 AM GMT+08:00

   Incident resolved.

This incident has been resolved.

1. investigating May 22, 2026, 4:24 AM GMT+08:00

   We are investigating elevated errors for users of Claude.ai, and will provide an update as soon as possible.

2. monitoring May 22, 2026, 4:42 AM GMT+08:00

   We have applied a fix and success rates for requests on Claude.ai have returned to normal. We are monitoring closely to ensure no further issues.

3. resolved May 22, 2026, 5:08 AM GMT+08:00

   This incident has been resolved.

Incident resolved.

1. identified May 21, 2026, 9:52 PM GMT+08:00

   Issue identified.

2. monitoring May 21, 2026, 10:52 PM GMT+08:00

   Monitoring recovery.

3. resolved May 21, 2026, 11:23 PM GMT+08:00

   Incident resolved.

4. identified May 22, 2026, 4:17 AM GMT+08:00

   Issue identified.

5. monitoring May 22, 2026, 4:25 AM GMT+08:00

   Monitoring recovery.

6. monitoring May 22, 2026, 4:44 AM GMT+08:00

   Monitoring recovery.

7. monitoring May 22, 2026, 5:02 AM GMT+08:00

   Monitoring recovery.

8. monitoring May 22, 2026, 5:21 AM GMT+08:00

   Monitoring recovery.

9. resolved May 22, 2026, 5:51 AM GMT+08:00

   Incident resolved.

This incident has been resolved.

1. investigating May 20, 2026, 10:43 PM GMT+08:00

   We are currently investigating this issue.

2. monitoring May 20, 2026, 11:56 PM GMT+08:00

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

3. resolved May 21, 2026, 12:04 AM GMT+08:00

   This incident has been resolved.

This incident has been resolved.

1. investigating May 20, 2026, 4:14 PM GMT+08:00

   We are currently investigating this issue.

2. monitoring May 20, 2026, 4:31 PM GMT+08:00

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

3. resolved May 20, 2026, 4:49 PM GMT+08:00

   This incident has been resolved.

OpenAI has recovered.

1. investigating May 20, 2026, 11:44 AM GMT+08:00

   Status storage update failed.

2. resolved May 20, 2026, 12:06 PM GMT+08:00

   OpenAI has recovered.

Incident resolved.

1. identified May 20, 2026, 7:32 AM GMT+08:00

   Issue identified.

2. monitoring May 20, 2026, 7:38 AM GMT+08:00

   Monitoring recovery.

3. monitoring May 20, 2026, 7:59 AM GMT+08:00

   Monitoring recovery.

4. resolved May 20, 2026, 8:37 AM GMT+08:00

   Incident resolved.

This incident has been resolved.

1. investigating May 19, 2026, 10:03 PM GMT+08:00

   We are currently investigating this issue.

2. monitoring May 19, 2026, 11:19 PM GMT+08:00

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

3. monitoring May 19, 2026, 11:21 PM GMT+08:00

   We are continuing to monitor for any further issues.

4. resolved May 19, 2026, 11:40 PM GMT+08:00

   This incident has been resolved.

This incident has been resolved.

1. investigating May 19, 2026, 4:41 PM GMT+08:00

   We are currently investigating this issue.

2. resolved May 19, 2026, 6:08 PM GMT+08:00

   This incident has been resolved.

This incident has been resolved.

1. investigating May 19, 2026, 3:00 PM GMT+08:00

   We are currently investigating this issue.

2. monitoring May 19, 2026, 3:56 PM GMT+08:00

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

3. resolved May 19, 2026, 4:30 PM GMT+08:00

   This incident has been resolved.

This issue has been resolved.

1. monitoring May 19, 2026, 12:46 PM GMT+08:00

   From 04:34–04:42 UTC, we saw elevated errors and latency on requests within the Claude.ai applications. Additionally, users may have experienced errors when attempting to login, including authenticating Claude Code via Claude.ai. We are monitoring closely to ensure no further issues, and will provide an additional update shortly.

2. resolved May 19, 2026, 12:51 PM GMT+08:00

   This issue has been resolved.

The issue affecting Claude services has been resolved. Impact occurred from 21:47 to 22:18 UTC.

1. investigating May 19, 2026, 6:10 AM GMT+08:00

   We are investigating elevated errors on requests to Claude Opus 4.7. We will provide an update as soon as possible.

2. resolved May 19, 2026, 6:19 AM GMT+08:00

   The issue affecting Claude services has been resolved. Impact occurred from 21:47 to 22:18 UTC.

This incident has been resolved.

1. investigating May 18, 2026, 2:12 PM GMT+08:00

   We are currently investigating this issue.

2. monitoring May 18, 2026, 3:28 PM GMT+08:00

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

3. resolved May 18, 2026, 4:07 PM GMT+08:00

   This incident has been resolved.

This incident has been resolved.

1. investigating May 17, 2026, 2:08 AM GMT+08:00

   We are currently investigating this issue.

2. monitoring May 17, 2026, 2:18 AM GMT+08:00

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

3. resolved May 17, 2026, 2:24 AM GMT+08:00

   This incident has been resolved.

Identity Provider has recovered.

1. investigating May 16, 2026, 10:13 AM GMT+08:00

   HTTP 404 from status check.

2. identified May 16, 2026, 10:30 AM GMT+08:00

   HTTP 503 from status check.

3. resolved May 16, 2026, 10:37 AM GMT+08:00

   Identity Provider has recovered.

Incident resolved.

1. investigating May 16, 2026, 12:11 AM GMT+08:00

   GPT5.5 Performance Degradation

2. monitoring May 16, 2026, 8:35 AM GMT+08:00

   Monitoring recovery.

3. resolved May 17, 2026, 8:15 AM GMT+08:00

   Incident resolved.

This incident has been resolved.

1. investigating May 15, 2026, 8:18 AM GMT+08:00

   We are currently investigating this issue.

2. investigating May 15, 2026, 8:19 AM GMT+08:00

   We are continuing to investigate this issue.

3. identified May 15, 2026, 9:06 AM GMT+08:00

   We are currently working to resolve issues affecting requests to Claude Opus and Sonnet 4.6, though success rates for Opus 4.7 have returned to normal.

4. identified May 15, 2026, 9:26 AM GMT+08:00

   We are working to resolve errors impacting Claude Opus 4.6, and have seen both Sonnet 4.6 and Opus 4.7 return to normal success rates.

5. resolved May 15, 2026, 9:46 AM GMT+08:00

   This incident has been resolved.