Live

Delays in customer support responses

All impacted services have now fully recovered.

The latest update from OpenAI.

State

Resolved

Started

9 d ago

2026-10-23 03:41 UTC

Lasted

2 h 17 min

until 2026-10-23 05:58 UTC

Worst impact

Notice

Timeline

5 updates
03:4104:1504:4905:2305:58
NoticeUpdate postedTimes in UTC

Investigating

1 h 2 min 45%

Identified

1 h 4 min 47%

Monitoring

11 min 8%

Updates

Times in UTC

As posted by OpenAI

Resolved2026-10-23 05:58 UTC

All impacted services have now fully recovered.

Monitoring2026-10-23 05:47 UTC

We have applied the mitigation and are monitoring the recovery.

Identified2026-10-23 04:43 UTC

A fix is being implemented for the issue affecting our support systems. Customers may continue to experience delays in receiving support responses. We will provide further updates as recovery progresses.

Investigating2026-10-23 03:57 UTC

As a temporary solution, customers looking to reach out to OpenAI Support can email [support@openai.com](mailto:support@openai.com "support@openai.com").

Investigating2026-10-23 03:41 UTC

We are investigating technical issues affecting our customer support systems. Customers may experience longer than usual response times. We are working to restore normal operations.

OpenAI in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

24

Days with an incident

16

Median duration

1 h 51 min

This incident

1.2× the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

3 days
median 1 h 51 min
90 days agoToday

Other OpenAI incidents

All incidents

Follow OpenAI

Your coding agent knows when OpenAI is down, and tells you when a failure is theirs, not yours. You can also get OpenAI incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "openai" and tell me if OpenAI has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.cc/feed.xml?providers=openai
Slack
/feed subscribe https://outages.cc/feed.xml?providers=openai

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane