OpenAI resolves the ChatGPT Work incident after about five and a half hours with no published cause

Sources: status page, discussion
Summary: The incident opened as elevated latency and was reclassified about 17 minutes later as elevated errors, naming Plus users as particularly affected and Work mode as unavailable for them, with later updates stating that users across multiple subscription plans may be unable to start or continue tasks. The status page now shows Resolved with all impacted services recovered, after a Monitoring update roughly half an hour earlier, and the elapsed time between the opening and closing markers is about five hours and twenty-four minutes. The page renders a twelve-hour clock with no explicit zone, so no resolution timestamp is asserted here in UTC. No root cause is published.
Why it matters: The incident is closed and no root cause is published, so teams that moved task execution into ChatGPT Work have a duration to plan against and nothing else.
Follow-up: Track whether OpenAI publishes a root cause or a post-incident review.