OpenAI had a bigger problem starting at 23:52 UTC on September 15, 2026. It recovered at 00:31 UTC on September 16, about 39 minutes later. OpenAI has since reported the issue resolved, though no detailed cause has been published.
Who this kind of outage hits
If you run automations, a product, or any workflow that calls OpenAI, a 39-minute window where things stop working can quietly swallow a lot. The hard part is that nothing inside your tool tells you. No alert fires. No red banner appears. Your workflow just stops producing output, your app goes quiet, and you find out when a customer writes in to ask why their summary never arrived, or why the chatbot stopped answering. That gap between “it broke” and “I heard about it” is where the damage happens.
Why this is especially rough without a technical background
If you are not an engineer, you have no logs to pull. There is no error on your screen. The work simply stops moving and you have no way to know whether the problem is on your side, OpenAI’s side, or somewhere in between. The first signal is usually an unhappy customer, or a colleague asking why the thing you built stopped working. By then you are already behind, already explaining, already apologizing for something that was never in your control.
Timeline
- 23:52 UTC, September 15, 2026 - OpenAI’s public status page reported a bigger problem.
- 00:31 UTC, September 16, 2026 - OpenAI reported the issue resolved.
- Total duration - about 39 minutes.
How a watcher catches this before your users do
NoCrash reads OpenAI’s public status page every minute. The moment that page flips from working to having trouble, NoCrash sends you a plain-language message, in words you can act on, without you having to go check anything yourself. That turns “my customer told me an hour later” into “I got a calm heads-up within a minute of OpenAI’s own report.” It also watches the things you ship: your n8n workflows through an API token, and your app through a URL or a small JS snippet you add once. So if something goes quiet on your own side, that surfaces too, sitting next to everything else you build on. NoCrash does not find the outage before OpenAI’s own status page does. It reads that page and tells you fast, in plain English, in one place.
For the authoritative account of this outage, check OpenAI’s official status page directly, as no external source link is available for this event.