ChatGPT Work — OpenAI's agentic task mode for paid subscribers — spent most of Monday afternoon, August 31, 2026 in a partial outage. OpenAI's status page logs the incident from 11:04 AM to 4:28 PM ET (~5 hours 24 minutes), with Plus users losing Work mode entirely during the worst stretch.
If you routed production workflows through ChatGPT Work that day, this is your reminder that hosted agent modes need fallbacks — same lesson as prior Work-mode incidents and the reliability gap explainx.ai tracks in why agents haven't gone mainstream.
TL;DR — timeline
| Time (ET) | Status |
|---|---|
| 11:04 AM | Incident opened — elevated latency identified |
| 11:21 AM | Elevated errors; Plus users — Work mode unavailable |
| 12:02 PM – 3:29 PM | Multiple updates: users can't start/continue Work tasks |
| 4:01 PM | Mitigation applied; monitoring recovery |
| 4:28 PM | Resolved — all impacted services recovered |
OpenAI classified the event as Partial outage · ChatGPT Work seeing elevated errors and latency.
What users experienced
Per OpenAI status updates and third-party monitoring:
- Could not start new ChatGPT Work tasks
- Could not continue in-progress Work tasks
- Plus plan especially affected — Work mode listed as unavailable
- Elevated latency even when partial function returned
OpenAI's @ChatGPT account on X posted mid-incident: "ChatGPT Work isn't working right now. Sorry about that, we're working on a fix!"
Downdetector peaked at 1,100+ reports for OpenAI products during the window — smaller than Microsoft's same-day Outlook spike (~4,600) but enough to confirm user-visible failure, not a silent backend blip.
Same day, separate Microsoft Exchange issues
CNBC reported Microsoft Exchange Online degradation the same afternoon — "users may experience degraded functionality with various Exchange Online functionalities." Microsoft tracked it through its 365 status account.
No evidence links the two outages. But the coincidence matters operationally: teams running Grok Outlook connectors (full read-write access) plus ChatGPT Work agent tasks hit both email and agent surfaces degraded within hours — a realistic preview of multi-vendor agent stack fragility.
What builders should do differently
| Practice | Why |
|---|---|
| Fallback harness | Route critical loops through Claude Code, OpenCode, or local models when hosted Work mode fails |
| Status page monitoring | Subscribe to status.openai.com; don't discover outages via user tickets |
| Separate read vs. act paths | Work mode down ≠ chat down; design workflows that degrade gracefully |
| SLA assumptions | Five-hour Work outage is acceptable to OpenAI as "partial" — adjust your internal SLAs accordingly |
Compare to August 27, 2026 — OpenAI logged a separate incident where Workspace Agents and ChatGPT Work on web/mobile saw increased error rates for 4h 14m. Work-mode reliability is an recurring theme, not a one-off.
Related on explainx.ai
- Why AI agents haven't gone mainstream
- OpenAI rogue agent and pacing update
- What is an agent harness?
- Loop engineering for coding agents
- Grok Outlook read-write connectors
- ChatGPT ads $1B revenue run rate
- Build personal AI system local workflow
Official source: OpenAI status incident 01M1C5M4K0WC8PPT0Z175RJA1E.
Incident times and duration from OpenAI status logs as of September 1, 2026.