On this page

OpenAI's status page and status API opened incident id 01M6P50GPP1V98EF8MJ9SH393R on the evening of 2026-11-05 Asia/Shanghai under the name ChatGPT Issues, with status investigating and impact minor, at 23:25:03 Asia/Shanghai. The same record later moved to identified at 2026-11-06 00:57:41 Asia/Shanghai and to monitoring at 01:05:56 Asia/Shanghai. The current title is ChatGPT Work and Dots Errors. The status API says a mitigation has been applied and the affected services are being watched to confirm recovery. Impact remains minor, and resolved_at is still empty—the incident is not yet marked resolved.

The status page banner still states that issues are currently being experienced. In the same check, status.json reads All Systems Operational with indicator none. When those two views sit side by side, the notes follow the incident record: monitoring, not a closed ticket, and not a report that every OpenAI surface has stopped. We haven't tested ChatGPT, ChatGPT Work, or Dots for this incident; everything below is a status-page / status-API self-report, not a live product test.

This ticket is not the same as the earlier 2026-11-05 incident about elevated error rates on paid ChatGPT when sending messages, which OpenAI marked resolved at 08:32:37 Asia/Shanghai. That earlier note is here: Paid ChatGPT Message Errors Rise on OpenAI Status—Now Resolved. Related DigIntoAI notes: ChatGPT Plus vs Pro—Price, Limits, and Who Should Upgrade (November 2026), ChatGPT Pricing (November 2026), and ChatGPT Pro and Business Can Claim Up to $500 Monthly API Credits.

What OpenAI reported

At 2026-11-05 23:25:03 Asia/Shanghai (2026-11-05T15:25:03Z), the incident opened in investigating with this wording: *We're investigating a potential issue for the listed services and checking how it affects users. We'll share an update when we know more.*

At 23:30:00 Asia/Shanghai (2026-11-05T15:30:00Z), a second investigating update repeated the same sentence. That later stamp is not a second round of progress, a new symptom list, or a root-cause note—it restates the opening text.

At 2026-11-06 00:26:31 Asia/Shanghai (2026-11-05T16:26:31Z), a third investigating update used the same sentence again. That stamp is also not a new progress note or a new symptom list.

At 00:57:41 Asia/Shanghai (2026-11-05T16:57:41Z), the record moved to identified: *We have identified that users are experiencing elevated errors for the impacted services.* / *We are working on implementing a mitigation.* The public update does not name a root cause or list specific failed actions.

At 01:05:56 Asia/Shanghai (2026-11-05T17:05:56Z), the record moved to monitoring: *We've applied a mitigation and are monitoring the affected services to confirm recovery.*

The status page card now titles the incident ChatGPT Work and Dots Errors and shows Monitoring. Public status-API updates still list affected_components as None; the notes follow the official current name, which already points to ChatGPT Work and Dots, and do not add an unverified component roster or a list of failed operations. Surfaces such as the API or Chat Completions are not named as failing in this incident's public updates.

All Systems Operational ≠ this incident resolved

During the investigating stage, the same status.json overview read Partial System Degradation with indicator minor. A later check of status.json shows description All Systems Operational and indicator none. page.updated_at matches the monitoring stamp (2026-11-05T17:05:56Z, 2026-11-06 01:05:56 Asia/Shanghai).

That overview green is not the same as this incident being marked resolved. The incident status remains monitoring, and resolved_at is still empty. Impact remains minor. The notes follow the incident record rather than treating the homepage overview as a closed ticket.

Not the same incident as this morning's paid message errors

Earlier on 2026-11-05, OpenAI carried a separate minor incident, id 01M6MBCX427A7113A3T4FJ1N6Y, titled Elevated error rates across paid ChatGPT plans. That record pointed at paid-plan users seeing errors when sending messages and was marked resolved at 2026-11-05 08:32:37 Asia/Shanghai (2026-11-05T00:32:37Z). The later record—opened as ChatGPT Issues, now titled ChatGPT Work and Dots Errors—is a new id, now monitoring, with resolved_at empty—it is not a reopening of the morning ticket, and it is not yet marked resolved.

Timeline (Asia/Shanghai, with UTC)

Clock (Asia/Shanghai)UTCStatus API step
2026-11-05 23:25:032026-11-05T15:25:03Zinvestigating — potential issue for listed services; checking how it affects users
2026-11-05 23:30:002026-11-05T15:30:00Zinvestigating — same wording; not a second progress note
2026-11-06 00:26:312026-11-05T16:26:31Zinvestigating — same wording again; not a new progress note
2026-11-06 00:57:412026-11-05T16:57:41Zidentified — elevated errors for the impacted services; working on a mitigation
2026-11-06 01:05:562026-11-05T17:05:56Zmonitoring — mitigation applied; monitoring to confirm recovery; name now ChatGPT Work and Dots Errors
Check ~2026-11-06 02:05—Still monitoring; resolved_at empty; name ChatGPT Work and Dots Errors; overview All Systems Operational / none (≠ this incident resolved); impact still minor

DigIntoAI status

We haven't tested ChatGPT, ChatGPT Work, or Dots for this incident—no login, and no attempt to reproduce an error or a recovery. The notes follow the OpenAI status page and status API self-report only. Product status can change afterward; the OpenAI status page and status API take precedence.

Quick facts

  1. Source. OpenAI status page + status API (status.json / incidents.json).
  2. Incident. 01M6P50GPP1V98EF8MJ9SH393R — opened as ChatGPT Issues; current name ChatGPT Work and Dots Errors.
  3. Status / impact. monitoring / minor; resolved_at empty.
  4. Opened. 2026-11-05 23:25:03 Asia/Shanghai; identified at 2026-11-06 00:57:41; monitoring at 01:05:56.
  5. Official wording (latest). Mitigation applied; monitoring the affected services to confirm recovery.
  6. Page line. Current title ChatGPT Work and Dots Errors; status line Monitoring. The banner still notes issues are currently being experienced, alongside minor impact and a record that is not yet resolved.
  7. Overview. All Systems Operational / indicator none—not the same as this incident being resolved. Earlier, during investigating, the overview read Partial System Degradation / minor.
  8. Not the morning ticket. Paid ChatGPT send-message errors (01M6MBCX427A7113A3T4FJ1N6Y) resolved at 08:32:37 Asia/Shanghai.
  9. Live test. Status self-report only; no live ChatGPT, ChatGPT Work, or Dots test.

In short

OpenAI's status page and status API show a minor incident opened 2026-11-05 23:25:03 Asia/Shanghai as ChatGPT Issues, later identified at 00:57:41 and moved to monitoring at 01:05:56 Asia/Shanghai, now titled ChatGPT Work and Dots Errors. A mitigation has been applied and recovery is being watched; resolved_at is still empty, so the ticket is not yet marked resolved. Overview reads All Systems Operational, which is not the same as this incident being closed. This is not the resolved morning ticket about paid ChatGPT send-message errors. We haven't tested ChatGPT, ChatGPT Work, or Dots; the notes follow the OpenAI status page and status API only.