What happened
On August 31, 2026, OpenAI experienced a significant problem starting at 15:05 UTC. It lasted about five hours. OpenAI marked it resolved at 20:29 UTC. The disruption was described as a bigger problem, not a minor blip. OpenAI has since reported that it is resolved.
Who this hits and how they usually find out
If you have an automation, a product, or a workflow that calls OpenAI, you probably did not get an alert. You got a customer message. Or a colleague asking why the thing stopped working. That is the normal shape of this kind of trouble: the tool goes quiet, your work stops moving, and the first real signal is someone unhappy on the other end. Most operators who build on OpenAI are not watching its status page in a browser tab all day. They are doing other things. By the time the pattern becomes obvious, the outage has already been running for an hour or two.
Why this is especially rough without a watcher
There is no error on your screen when a third-party tool goes down. Your n8n workflow does not send you a message saying “I stopped.” Your app just starts returning nothing, or timing out, or silently queuing work that never runs. If you are not an engineer, there are no logs to pull, no alert to read. The first sign is a customer asking why their thing did not happen. That is a bad position to be in, and it is the default position for most solo operators and small teams.
Timeline
- 15:05 UTC, August 31, 2026 - OpenAI’s problem begins.
- Roughly five hours - the disruption runs. Anything calling OpenAI during this window would have been affected.
- 20:29 UTC, August 31, 2026 - OpenAI marks the issue resolved.
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 check anything yourself. You find out within a minute of OpenAI’s own report, not an hour later when a customer writes in.
It also watches the things you ship. If you have n8n workflows, NoCrash watches them through your API token. If you have an app, you can give it a URL or drop in a small JS snippet, and it watches that too. So if something goes quiet on your own side, that surfaces as well. What you get is one place where both the tools you build on and the things you ship are being watched, and a calm heads-up in plain English when something changes.
To be clear about what this is: NoCrash reads public status pages and watches what you point it at. It does not find trouble before the tool’s own status page does. It catches the report as fast as possible and tells you in language you can actually use.
The authoritative account
OpenAI has not provided a public source link for this specific outage. For the most current information, check OpenAI’s official status page directly.