Part of OpenAI

OpenAI API Outage History

OpenAI API is up right now

OpenAI API had 42 outages in the last 2 years — averaging 1.7 incidents per month.

There were 42 OpenAI API outages since January 27, 2026. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.openai.com

Minor May 13, 2026

Codex 5.5 engines are experiencing high error rate

Detected by Pingoru
May 13, 2026, 10:20 AM UTC
Resolved
May 13, 2026, 10:20 AM UTC
Duration
—
Affected: Codex WebCodex APICLIVS Code extensionApp
Timeline · 4 updates
  1. investigating May 13, 2026, 08:18 AM UTC

    Status: Investigating We are currently experiencing elevated error rates for gpt-5.5. Affected components CLI (Degraded performance) App (Degraded performance) VS Code extension (Degraded performance) Codex API (Degraded performance) Codex Web (Degraded performance)

  2. identified May 13, 2026, 09:00 AM UTC

    Status: Identified High error rate on codex gpt 5.5 for free users. Degraded latency on gpt 5.5 for all codex users. Affected components Codex API (Degraded performance) Codex Web (Degraded performance) CLI (Degraded performance) App (Degraded performance) VS Code extension (Degraded performance)

  3. monitoring May 13, 2026, 09:34 AM UTC

    Status: Monitoring We have applied the mitigation and are monitoring the recovery. Affected components Codex Web (Degraded performance) CLI (Degraded performance) App (Degraded performance) VS Code extension (Degraded performance) Codex API (Degraded performance)

  4. resolved May 13, 2026, 10:20 AM UTC

    Status: Resolved All impacted services have now fully recovered. Affected components Codex Web (Operational) CLI (Operational) App (Operational) VS Code extension (Operational) Codex API (Operational)

Read the full incident report →

Minor May 13, 2026

Realtime API - SIP/WebRTC flow are down

Detected by Pingoru
May 13, 2026, 09:23 AM UTC
Resolved
May 13, 2026, 09:23 AM UTC
Duration
—
Affected: Audio
Timeline · 3 updates
  1. investigating May 13, 2026, 06:28 AM UTC

    Status: Investigating We are investigating the issue for the listed services. Affected components Audio (Degraded performance)

  2. investigating May 13, 2026, 06:37 AM UTC

    Status: Investigating We are investigating the issue for the listed services. Affected components Audio (Degraded performance)

  3. resolved May 13, 2026, 09:23 AM UTC

    Status: Resolved All impacted services have now fully recovered. Affected components Audio (Operational)

Read the full incident report →

Minor May 11, 2026

Elevated error rates with GPT 5.5

Detected by Pingoru
May 11, 2026, 05:59 PM UTC
Resolved
May 11, 2026, 05:59 PM UTC
Duration
—
Affected: ResponsesChat Completions
Timeline · 4 updates
  1. investigating May 11, 2026, 04:11 PM UTC

    Status: Investigating We are investigating the issue for the listed services. Affected components Responses (Degraded performance) Chat Completions (Degraded performance)

  2. identified May 11, 2026, 04:35 PM UTC

    Status: Identified We have identified that users are experiencing elevated errors for the impacted services. We are working on implementing a mitigation. Affected components Chat Completions (Degraded performance) Responses (Degraded performance)

  3. monitoring May 11, 2026, 05:04 PM UTC

    Status: Monitoring We have applied the mitigation and are monitoring the recovery. Affected components Responses (Operational) Chat Completions (Operational)

  4. resolved May 11, 2026, 05:59 PM UTC

    Status: Resolved All impacted services have now fully recovered. Affected components Responses (Operational) Chat Completions (Operational)

Read the full incident report →

Minor May 11, 2026

Users may experience elevated errors in ChatGPT uploading files and Codex Cloud creating tasks

Detected by Pingoru
May 11, 2026, 05:35 AM UTC
Resolved
May 11, 2026, 05:35 AM UTC
Duration
—
Affected: Codex WebFile uploads
Timeline · 3 updates
  1. investigating May 11, 2026, 01:23 AM UTC

    Status: Investigating We are investigating the issue for the listed services. Affected components File uploads (Degraded performance) Codex Web (Degraded performance)

  2. monitoring May 11, 2026, 03:23 AM UTC

    Status: Monitoring We have applied the mitigation and are monitoring the recovery. Affected components File uploads (Degraded performance) Codex Web (Operational)

  3. resolved May 11, 2026, 05:35 AM UTC

    Status: Resolved All impacted services have now fully recovered. Affected components Codex Web (Operational) File uploads (Operational)

Read the full incident report →

Minor May 9, 2026

Elevated errors for Responses API

Detected by Pingoru
May 09, 2026, 12:08 AM UTC
Resolved
May 09, 2026, 12:08 AM UTC
Duration
—
Affected: Responses
Timeline · 2 updates
  1. monitoring May 09, 2026, 12:07 AM UTC

    Status: Monitoring Between 4:05pm and 4:40pm PT on May 8, some customers using the Responses API may have experienced elevated 404 errors. We identified the issue as related to a recent deploy and rolled it back. Responses API traffic has recovered, and we are marking this incident as resolved. Affected components Responses (Partial outage)

  2. resolved May 09, 2026, 12:08 AM UTC

    Status: Resolved All impacted services have now fully recovered. Between 4:05pm and 4:40pm PT on May 8, some customers using the Responses API may have experienced elevated 404 errors. We identified the issue as related to a recent deploy and rolled it back. Responses API traffic has recovered, and we are marking this incident as resolved. Affected components Responses (Operational)

Read the full incident report →

Minor May 8, 2026

Degraded Performance with Codex Cloud Tasks

Detected by Pingoru
May 08, 2026, 04:17 PM UTC
Resolved
May 08, 2026, 04:17 PM UTC
Duration
—
Affected: Codex WebCodex APICLIVS Code extensionApp
Timeline · 2 updates
  1. investigating May 08, 2026, 03:07 PM UTC

    Status: Investigating We are observing an issue with follow-up prompts to Codex Cloud tasks failing at higher than expected rate. We are investigating the issue. Affected components Codex Web (Degraded performance)

  2. resolved May 08, 2026, 04:17 PM UTC

    Status: Resolved All impacted services have now fully recovered. Affected components Codex Web (Operational) CLI (Operational) App (Operational) VS Code extension (Operational) Codex API (Operational)

Read the full incident report →

Minor May 8, 2026

Increased Error Rate for gpt-5.5 model in the API

Detected by Pingoru
May 08, 2026, 02:14 PM UTC
Resolved
May 08, 2026, 02:14 PM UTC
Duration
—
Affected: ResponsesChat Completions
Timeline · 5 updates
  1. investigating May 08, 2026, 12:31 PM UTC

    Status: Investigating We are investigating the issue for the listed services. Affected components Chat Completions (Degraded performance) Responses (Degraded performance)

  2. investigating May 08, 2026, 01:26 PM UTC

    Status: Investigating We are seeing partial recovery, but are still working on implementing additional mitigations. Affected components Chat Completions (Degraded performance) Responses (Degraded performance)

  3. identified May 08, 2026, 01:42 PM UTC

    Status: Identified We implemented the mitigations and are observing reduction in error rates, but are still seeing higher than normal latency. Affected components Chat Completions (Degraded performance) Responses (Degraded performance)

  4. monitoring May 08, 2026, 01:57 PM UTC

    Status: Monitoring We have applied the mitigation and are monitoring the recovery. Affected components Chat Completions (Degraded performance) Responses (Degraded performance)

  5. resolved May 08, 2026, 02:14 PM UTC

    Status: Resolved All impacted services have now fully recovered. Affected components Chat Completions (Operational) Responses (Operational)

Read the full incident report →

Minor May 8, 2026

Elevated transcription failures affecting ChatGPT & Codex

Detected by Pingoru
May 08, 2026, 08:31 AM UTC
Resolved
May 08, 2026, 08:31 AM UTC
Duration
—
Affected: Codex WebCodex APICLIVS Code extensionVoice modeApp
Timeline · 6 updates
  1. identified May 07, 2026, 05:15 PM UTC

    Status: Identified We have identified that users are experiencing elevated errors for the impacted services. We are working on implementing a mitigation. Affected components CLI (Degraded performance) App (Degraded performance) VS Code extension (Degraded performance) Codex API (Degraded performance) Voice mode (Degraded performance) Codex Web (Degraded performance)

  2. investigating May 07, 2026, 06:44 PM UTC

    Status: Investigating We are investigating the issue for the listed services. Affected components CLI (Degraded performance) App (Degraded performance) VS Code extension (Degraded performance) Codex API (Degraded performance) Voice mode (Degraded performance) Codex Web (Degraded performance)

  3. investigating May 07, 2026, 08:17 PM UTC

    Status: Investigating We are investigating the issue for the listed services. Affected components CLI (Degraded performance) App (Degraded performance) VS Code extension (Degraded performance) Codex API (Degraded performance) Voice mode (Degraded performance) Codex Web (Degraded performance)

  4. investigating May 07, 2026, 11:47 PM UTC

    Status: Investigating We are investigating the issue for the listed services. Affected components App (Degraded performance) VS Code extension (Degraded performance) Codex API (Degraded performance) Voice mode (Degraded performance) Codex Web (Degraded performance) CLI (Degraded performance)

  5. monitoring May 08, 2026, 06:15 AM UTC

    Status: Monitoring We have applied the mitigation and are monitoring the recovery. Affected components Voice mode (Degraded performance) Codex Web (Degraded performance) CLI (Degraded performance) App (Degraded performance) VS Code extension (Degraded performance) Codex API (Degraded performance)

  6. resolved May 08, 2026, 08:31 AM UTC

    Status: Resolved All impacted services have now fully recovered. Affected components Voice mode (Operational) Codex Web (Operational) CLI (Operational) App (Operational) VS Code extension (Operational) Codex API (Operational)

Read the full incident report →

Minor May 1, 2026

Elevated error rate for Responses API

Detected by Pingoru
May 01, 2026, 03:38 PM UTC
Resolved
May 01, 2026, 03:38 PM UTC
Duration
—
Affected: Responses
Timeline · 3 updates
  1. investigating May 01, 2026, 02:25 PM UTC

    Status: Investigating We are investigating the issue for the listed services. Affected components Responses (Degraded performance)

  2. monitoring May 01, 2026, 03:04 PM UTC

    Status: Monitoring We have applied the mitigation and are monitoring the recovery. Affected components Responses (Degraded performance)

  3. resolved May 01, 2026, 03:38 PM UTC

    Status: Resolved All impacted services have now fully recovered. Affected components Responses (Operational)

Read the full incident report →

Minor April 29, 2026

Users may experience elevated error rate for gpt-4o-mini in the API

Detected by Pingoru
Apr 29, 2026, 05:41 AM UTC
Resolved
Apr 29, 2026, 05:41 AM UTC
Duration
—
Affected: ResponsesChat Completions
Timeline · 3 updates
  1. identified Apr 29, 2026, 05:12 AM UTC

    Status: Identified We have identified that users are experiencing elevated errors for the impacted services. We are working on implementing a mitigation. Affected components Chat Completions (Degraded performance) Responses (Degraded performance)

  2. monitoring Apr 29, 2026, 05:19 AM UTC

    Status: Monitoring We have applied the mitigation and are monitoring the recovery. Affected components Chat Completions (Degraded performance) Responses (Degraded performance)

  3. resolved Apr 29, 2026, 05:41 AM UTC

    Status: Resolved All impacted services have now fully recovered. Affected components Responses (Operational) Chat Completions (Operational)

Read the full incident report →

Minor April 29, 2026

ChatGPT users may encounter issues in conversation

Detected by Pingoru
Apr 29, 2026, 05:27 AM UTC
Resolved
Apr 29, 2026, 05:27 AM UTC
Duration
—
Affected: ResponsesFine-tuningImagesBatchAudioModerationsSoraCodex WebCodex APICLIVS Code extensionChatGPT AtlasFedRAMPEmbeddingsChat CompletionsRealtimeFilesFile uploadsConversationsAgentVoice modeConnectors/AppsCompliance APIAppDeep ResearchSearchGPTsImage GenerationLogin
Timeline · 2 updates
  1. investigating Apr 29, 2026, 05:18 AM UTC

    Status: Investigating We are investigating the issue for the listed services. Affected components Compliance API (Operational) Sora (Operational) VS Code extension (Operational) File uploads (Operational) Connectors/Apps (Operational) ChatGPT Atlas (Operational) Search (Operational) Conversations (Partial outage) Realtime (Operational) Login (Operational) FedRAMP (Operational) Audio (Operational) Agent (Operational) Codex Web (Operational) Images (Operational) Image Generation (Operational) GPTs (Operational) Codex API (Operational) Fine-tuning (Operational) Files (Operational) Deep Research (Operational) CLI (Operational) App (Operational) Login (Operational) Batch (Operational) Chat Completions (Operational) Responses (Operational) Voice mode (Operational) Embeddings (Operational) Moderations (Operational)

  2. resolved Apr 29, 2026, 05:27 AM UTC

    Status: Resolved All impacted services have now fully recovered. Affected components File uploads (Operational) Embeddings (Operational) Image Generation (Operational) Codex Web (Operational) Login (Operational) Realtime (Operational) Files (Operational) Moderations (Operational) Connectors/Apps (Operational) Sora (Operational) Audio (Operational) Login (Operational) ChatGPT Atlas (Operational) Images (Operational) Fine-tuning (Operational) Conversations (Operational) Compliance API (Operational) Responses (Operational) GPTs (Operational) Codex API (Operational) Batch (Operational) Chat Completions (Operational) CLI (Operational) App (Operational) VS Code extension (Operational) Agent (Operational) Deep Research (Operational) Voice mode (Operational) Search (Operational) FedRAMP (Operational)

Read the full incident report →

Minor April 28, 2026

Codex stream is disconnecting intermittently

Detected by Pingoru
Apr 28, 2026, 11:12 PM UTC
Resolved
Apr 28, 2026, 11:12 PM UTC
Duration
—
Affected: Codex WebCodex APICLIVS Code extensionApp
Timeline · 3 updates
  1. identified Apr 28, 2026, 10:46 PM UTC

    Status: Identified We have identified that users are experiencing elevated errors for the impacted services. We are working on implementing a mitigation. Affected components Codex Web (Degraded performance) CLI (Degraded performance) App (Degraded performance) VS Code extension (Degraded performance) Codex API (Degraded performance)

  2. monitoring Apr 28, 2026, 10:58 PM UTC

    Status: Monitoring We have applied the mitigation and are monitoring the recovery. Affected components Codex API (Degraded performance) Codex Web (Degraded performance) CLI (Degraded performance) App (Degraded performance) VS Code extension (Degraded performance)

  3. resolved Apr 28, 2026, 11:12 PM UTC

    Status: Resolved All impacted services have now fully recovered. Affected components Codex Web (Operational) CLI (Operational) App (Operational) VS Code extension (Operational) Codex API (Operational)

Read the full incident report →

Minor April 24, 2026

Elevated errors on model gpt-5.5 in codex

Detected by Pingoru
Apr 24, 2026, 10:15 PM UTC
Resolved
Apr 24, 2026, 10:15 PM UTC
Duration
—
Affected: Codex API
Timeline · 2 updates
  1. investigating Apr 24, 2026, 09:24 PM UTC

    Status: Investigating We are investigating the issue for the listed services. Affected components Codex API (Degraded performance)

  2. resolved Apr 24, 2026, 10:15 PM UTC

    Status: Resolved All impacted services have now fully recovered. Affected components Codex API (Operational)

Read the full incident report →

Minor April 23, 2026

Elevated errors in Codex

Detected by Pingoru
Apr 23, 2026, 08:29 PM UTC
Resolved
Apr 23, 2026, 08:29 PM UTC
Duration
—
Affected: Codex WebCodex APICLIVS Code extensionApp
Timeline · 2 updates
  1. investigating Apr 23, 2026, 06:23 PM UTC

    Status: Investigating We’re investigating elevated errors affecting Codex gpt-5.5 usage. Some users may see intermittent “not found” errors when starting or updating requests. We’re working to mitigate the issue and will share another update soon. Affected components VS Code extension (Degraded performance) Codex API (Degraded performance) Codex Web (Degraded performance) CLI (Degraded performance) App (Degraded performance)

  2. resolved Apr 23, 2026, 08:29 PM UTC

    Status: Resolved GPT-5.5 is now available to all paid users in Codex. If you continue to see access issues, please update to the latest Codex version. We’ll share another update if needed. Affected components Codex Web (Operational) CLI (Operational) App (Operational) VS Code extension (Operational) Codex API (Operational)

Read the full incident report →

Minor April 23, 2026

Elevated error rates and latency for Moderation API

Detected by Pingoru
Apr 23, 2026, 05:57 PM UTC
Resolved
Apr 23, 2026, 05:57 PM UTC
Duration
—
Affected: Moderations
Timeline · 3 updates
  1. investigating Apr 23, 2026, 04:44 PM UTC

    Status: Investigating We are investigating elevated error rates and latency affecting the Moderation API. Affected components Moderations (Degraded performance)

  2. monitoring Apr 23, 2026, 05:41 PM UTC

    Status: Monitoring We applied mitigation by adding capacity, and error rates and latency are improving. Some API requests may continue to return errors or time out while recovery continues. We are monitoring to confirm the issue is fully resolved. Affected components Moderations (Degraded performance)

  3. resolved Apr 23, 2026, 05:57 PM UTC

    Status: Resolved Error rates and latency for the Moderation API have returned to normal levels after mitigation. Affected components Moderations (Operational)

Read the full incident report →

Minor April 21, 2026

Some users may encounter issues with GPT-5.4-C model in Codex

Detected by Pingoru
Apr 21, 2026, 04:33 AM UTC
Resolved
Apr 21, 2026, 04:33 AM UTC
Duration
—
Affected: Codex WebCodex APICLIVS Code extensionApp
Timeline · 2 updates
  1. monitoring Apr 21, 2026, 02:34 AM UTC

    Status: Monitoring We have applied the mitigation and are monitoring the recovery. Affected components CLI (Degraded performance) App (Degraded performance) VS Code extension (Degraded performance) Codex API (Degraded performance) Codex Web (Degraded performance)

  2. resolved Apr 21, 2026, 04:33 AM UTC

    Status: Resolved All impacted services have now fully recovered. Affected components CLI (Operational) App (Operational) VS Code extension (Operational) Codex API (Operational) Codex Web (Operational)

Read the full incident report →

Minor April 16, 2026

Responses API Streaming Error

Detected by Pingoru
Apr 16, 2026, 09:21 PM UTC
Resolved
Apr 16, 2026, 09:21 PM UTC
Duration
—
Affected: Responses
Timeline · 3 updates
  1. investigating Apr 16, 2026, 07:40 PM UTC

    Status: Investigating We have identified an issue affecting some customers using the OpenAI Java SDK with Responses API streaming.

  2. monitoring Apr 16, 2026, 08:31 PM UTC

    Status: Monitoring We have applied the mitigation and are monitoring the recovery. Affected components Responses (Degraded performance)

  3. resolved Apr 16, 2026, 09:21 PM UTC

    Status: Resolved All impacted services have now fully recovered. Affected components Responses (Operational)

Read the full incident report →

Minor April 15, 2026

ChatGPT FedRAMP workspaces not loading

Detected by Pingoru
Apr 15, 2026, 06:55 PM UTC
Resolved
Apr 15, 2026, 06:55 PM UTC
Duration
—
Affected: FedRAMP
Timeline · 4 updates
  1. investigating Apr 15, 2026, 05:55 PM UTC

    Status: Investigating We are investigating the issue for the listed services. Affected components FedRAMP (Full outage)

  2. identified Apr 15, 2026, 06:40 PM UTC

    Status: Identified We have identified that users are experiencing elevated errors for the impacted services. We are working on implementing a mitigation. Affected components FedRAMP (Full outage)

  3. monitoring Apr 15, 2026, 06:50 PM UTC

    Status: Monitoring We have applied the mitigation and are monitoring the recovery. Affected components FedRAMP (Operational)

  4. resolved Apr 15, 2026, 06:55 PM UTC

    Status: Resolved All impacted services have now fully recovered. Affected components FedRAMP (Operational)

Read the full incident report →

Minor April 6, 2026

GET /v1/responses endpoint is currently down and unable to serve requests

Detected by Pingoru
Apr 06, 2026, 10:39 AM UTC
Resolved
Apr 06, 2026, 10:39 AM UTC
Duration
—
Affected: Responses
Timeline · 4 updates
  1. investigating Apr 06, 2026, 10:07 AM UTC

    Status: Investigating We are investigating the issue for the listed services. Affected components Responses (Partial outage)

  2. investigating Apr 06, 2026, 10:14 AM UTC

    Status: Investigating We are investigating the issue for the listed services. Affected components Responses (Degraded performance)

  3. monitoring Apr 06, 2026, 10:23 AM UTC

    Status: Monitoring We are mostly mitigated and remain observing recovery. Affected components Responses (Degraded performance)

  4. resolved Apr 06, 2026, 10:39 AM UTC

    Status: Resolved All impacted services have now fully recovered. Affected components Responses (Operational)

Read the full incident report →

Minor April 2, 2026

High error rate for completionsapi-gpt-5-nano

Detected by Pingoru
Apr 02, 2026, 09:42 AM UTC
Resolved
Apr 02, 2026, 09:42 AM UTC
Duration
—
Affected: Chat Completions
Timeline · 3 updates
  1. identified Apr 02, 2026, 07:36 AM UTC

    Status: Identified We have identified that users are experiencing elevated errors for the impacted services. We are working on implementing a mitigation. Affected components Chat Completions (Degraded performance)

  2. monitoring Apr 02, 2026, 08:03 AM UTC

    Status: Monitoring We have applied the mitigation and are monitoring the recovery. Affected components Chat Completions (Degraded performance)

  3. resolved Apr 02, 2026, 09:42 AM UTC

    Status: Resolved The issue is now resolved. Affected components Chat Completions (Operational)

Read the full incident report →

Minor March 26, 2026

Responses API and Sora Increased Error Rates

Detected by Pingoru
Mar 26, 2026, 11:17 PM UTC
Resolved
Mar 26, 2026, 11:17 PM UTC
Duration
—
Affected: Responses
Timeline · 7 updates
  1. investigating Mar 26, 2026, 09:21 PM UTC

    Status: Investigating We are investigating the issue for the listed services. Affected components Responses (Partial outage)

  2. investigating Mar 26, 2026, 09:35 PM UTC

    Status: Investigating We are continuing to investigate this issue. We can share this only affects users using store: true param. Affected components Responses (Degraded performance)

  3. investigating Mar 26, 2026, 10:08 PM UTC

    Status: Investigating We are continuing to investigate this issue. At this point, the issue is impacting a portion of Sora traffic, as well as Responses API using store: true param. Affected components Responses (Degraded performance)

  4. investigating Mar 26, 2026, 10:55 PM UTC

    Status: Investigating We are investigating the issue for the listed services. Affected components Responses (Partial outage)

  5. identified Mar 26, 2026, 10:58 PM UTC

    Status: Identified We have identified the root cause for this issue, and have implemented a mitigation. We are seeing error rates starting to decline and normal service recovering. Affected components Responses (Partial outage)

  6. monitoring Mar 26, 2026, 11:03 PM UTC

    Status: Monitoring We have applied the mitigation and are monitoring the recovery. Affected components Responses (Partial outage)

  7. resolved Mar 26, 2026, 11:17 PM UTC

    Status: Resolved All impacted services have now fully recovered. Affected components Responses (Operational)

Read the full incident report →

Minor March 24, 2026

Elevated error rates on Realtime API SIP endpoints

Detected by Pingoru
Mar 24, 2026, 08:20 PM UTC
Resolved
Mar 24, 2026, 08:20 PM UTC
Duration
—
Affected: Realtime
Timeline · 5 updates
  1. investigating Mar 24, 2026, 05:24 PM UTC

    Status: Investigating We have identified that users are experiencing elevated errors for the impacted services. We are working on implementing a mitigation. Affected components Realtime (Degraded performance)

  2. investigating Mar 24, 2026, 05:31 PM UTC

    Status: Investigating We have identified that users are experiencing elevated errors for the Realtime API SIP endpoints beginning at approximately midnight Pacific time. We are currently investigating the issue. Affected components Realtime (Degraded performance)

  3. identified Mar 24, 2026, 05:55 PM UTC

    Status: Identified We have identified that users are experiencing elevated errors for the impacted services. Root cause has been identified and mitigation is underway. Affected components Realtime (Degraded performance)

  4. monitoring Mar 24, 2026, 07:31 PM UTC

    Status: Monitoring We have applied the mitigation and are monitoring the recovery. Affected components Realtime (Degraded performance)

  5. resolved Mar 24, 2026, 08:20 PM UTC

    Status: Resolved All impacted services have now fully recovered. Affected components Realtime (Operational)

Read the full incident report →

Minor March 24, 2026

Some customer may encounter errors creating, updating projects, and uploading files

Detected by Pingoru
Mar 24, 2026, 10:51 AM UTC
Resolved
Mar 24, 2026, 10:51 AM UTC
Duration
—
Affected: FilesFile uploads
Timeline · 6 updates
  1. investigating Mar 24, 2026, 03:53 AM UTC

    Status: Investigating We are investigating the issue for the listed services.

  2. investigating Mar 24, 2026, 04:24 AM UTC

    Status: Investigating We are investigating the issue for the listed services. Affected components File uploads (Degraded performance)

  3. identified Mar 24, 2026, 05:44 AM UTC

    Status: Identified We are still implementing the mitigation. Affected components File uploads (Degraded performance)

  4. monitoring Mar 24, 2026, 09:15 AM UTC

    Status: Monitoring We have applied the mitigation and are monitoring the recovery. Affected components File uploads (Degraded performance)

  5. monitoring Mar 24, 2026, 10:22 AM UTC

    Status: Monitoring We have identified additional impacted services and are actively rolling out the required mitigation Affected components File uploads (Degraded performance) Files (Degraded performance)

  6. resolved Mar 24, 2026, 10:51 AM UTC

    Status: Resolved All impacted services have now fully recovered. Affected components File uploads (Operational) Files (Operational)

Read the full incident report →