On 2 October 2026, ChatGPT users hit errors running code, analysing data or creating files. OpenAI applied a mitigation and says it is monitoring recovery, but as of the last update the incident is still open.
Started
16:03 UTC
Duration
Ongoing
Source
IsDown
Next time
OpenAI is degraded. Is your product working?
An incident on their side does not always mean an outage on yours, and the only way to know is to already be watching your own endpoints. Set that up in under a minute and you will be notified the next time your own site is affected. And there will be a next time.
50 monitors for your own websites. No card.
What happened?
OpenAI's status page logged one incident on this day, starting at 16:03 UTC, titled "Issues with data analysis and file creation in ChatGPT". The single update posted says some users experienced errors when running code, analysing data or creating files in ChatGPT, and that OpenAI had applied a mitigation and was monitoring the recovery. No further update has been filed since, so the incident remains open at 16:03 UTC, the last point OpenAI published anything. No duration is recorded because no resolution has been logged. No components are listed as affected on the page, and no user reports were filed during this window, so you have only OpenAI's own account to go on. That one filing is doing all the work here: it tells you the mitigation step happened, but not whether it fully worked, and not what caused the errors in the first place. OpenAI's status page does not say why code execution, data analysis or file creation broke. Over the past 90 days OpenAI has logged 98 incidents with a median duration of 1 hour 52 minutes, and across its full history it averages 15.1 incidents a month, so a single-digit-hour data analysis fault is not unusual for this provider. Whether this one resolves quickly or runs long is not yet on the record.
Learning
This incident sits in a specific layer: the code execution and file handling pipeline behind ChatGPT, not the basic chat endpoint, which is why a simple uptime check against OpenAI's main API or chat interface could easily stay green while you can't analyse a file or run code. UptimeRobot's own 30-day figures show 41 incidents against OpenAI with a median duration of 1h 17m, which is the kind of pattern that only shows up when you are watching the provider's side independently of your own product. If your product calls OpenAI for data analysis or file generation, pinging your own endpoint tells you your server is up, but it says nothing about whether the model backend can actually run code right now. That gap is exactly where this outage lives. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.
