Navier AI - Notice history

All impacted services have now fully recovered.

This is impacting users in India, Japan, and Korea. We have applied the mitigation and are monitoring the recovery.

The issue affecting other Claude models has been resolved.

All impacted services have now fully recovered.

We have applied the mitigation and are monitoring the recovery.

All impacted services have now fully recovered.

We have applied the mitigation and are monitoring the recovery.

All impacted services have now fully recovered.

All impacted services have now fully recovered.

We have applied the mitigation and are monitoring the recovery.

We have implemented an initial mitigation and are seeing improvements in API latency. We are continuing to investigate the scope of the issue and apply additional mitigations as needed. Some requests to the Responses and Chat Completions APIs may still experience elevated latency or timeouts.

We have identified that users are experiencing elevated latency for the impacted services.

We are working on implementing a mitigation.

All impacted services have now fully recovered.

The issue causing elevated errors across ChatGPT, Codex, and the API has been resolved, and all affected services have recovered.

Thank you for your patience while we worked to restore service.

The detailed Root Cause Analysis (RCA) will be published in the next 5 business days.

We have applied the mitigation and are monitoring the recovery.

We have applied the mitigation and are monitoring the recovery.

We have applied the mitigation and are monitoring the recovery.

We have applied the mitigation and are monitoring the recovery.

We’re still investigating elevated errors affecting ChatGPT, Codex, and the API including the Agents API.

Some users may experience failed requests, difficulty logging in or signing up, and tasks that do not complete. We’ll share updates as we learn more.

We’re investigating elevated errors affecting ChatGPT, Codex, and the API including the Agents API.

Some users may experience failed requests, difficulty logging in or signing up, and tasks that do not complete. We’ll share updates as we learn more.

The issue affecting Claude.ai, the Claude desktop and mobile apps, Claude Code, Claude Cowork, and the Claude API has been resolved, and services have been operating normally since recovery. Impact occurred from 07:00 PT / 14:00 UTC to 07:59 PT / 14:59 UTC.

All services have been operating normally since 14:59 UTC. We are continuing to monitor.

Most services have recovered as of 14:59 UTC. Signing in, starting new chats, voice conversations, Claude Code and Cowork sessions, purchases and file uploads are working again. Some messages sent between 14:00 and 14:59 UTC may not have been saved. We are monitoring closely and will post another update within 30 minutes.

The errors that began at 14:00 UTC were mitigated at 14:36 UTC, and existing conversations are mostly working again. A second issue is preventing many users from signing in (single sign-on and Sign in with Apple are unavailable), starting new chats, voice conversations and Claude Code or Cowork sessions, making purchases, and uploading files. If you're signed in, please don't sign out. We're working on a fix and will post another update within 30 minutes.

We have applied a mitigation and error rates have dropped substantially. Some sign-in attempts, account actions and Claude Code and Cowork sessions are still failing. We are continuing to work on a full fix.

We are investigating reports of degraded performance affecting claude.ai, platform.claude.com, the Claude API, Claude Code, and Claude Cowork. We will provide an update as soon as possible.

We are investigating elevated error rates affecting Claude.ai (including the desktop and mobile apps), Claude Code and Claude Cowork. Some requests to the Claude API are also returning errors. We will provide an update as soon as possible.

This issue has been resolved. Impact occurred from 5:50pm PT / 00:50 UTC to 7:10pm PT / 02:10 UTC.

We have seen success rates return to normal across affected models, and are monitoring closely to ensure no further issues.

We are continuing to work to resolve errors affecting some models. At this time, requests to Claude Fable 5 and 5.1 and Mythos 5 and 5.1 have returned to normal success rates. We are working to resolve remaining errors affecting Claude Opus 5, and will provide an additional update shortly.

We have identified the cause of elevated errors on requests to Claude Mythos 5.1, Claude Fable 5.1, and Claude Opus 5 and are working on a fix. We will provide an update as soon as possible.

All impacted services have now fully recovered.

We have applied the mitigation and are monitoring the recovery.

All impacted services have now fully recovered.

We have applied the mitigation and are monitoring the recovery.

We are implementing the mitigation.

We have identified elevated latencies impacting Responses API on the US endpoint.

We have applied the mitigation and are monitoring the recovery.

We have applied a mitigation and are monitoring recovery.

This issue has been resolved. From 9:50pm PT / 04:50 UTC through 00:36am PT / 07:36 UTC, users saw elevated errors on requests to Claude models, including Claude Opus 5 and Fable 5.

At this time, we have seen errors stabilize on Opus 5 and Fable 5, and are working to fully resolve success rates on all affected models. We will provide an update as soon as possible.

We are continuing to work to resolve issues causing elevated requests on multiple models. We will provide an update as soon as possible.

We have identified the cause of elevated errors on requests to Claude Mythos 5, Claude Fable 5, Claude Opus 5, and other Claude models and are working on a fix. We will provide an update as soon as possible.

This issue has been resolved.

This issue has been resolved.

This incident has been resolved.

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