The recorded impact window was 15 hours 24 minutes. That does not mean every user or request failed for the entire window, and it does not measure current service reliability.
What the incident record shows
OpenAI’s incident record describes effects on ChatGPT and API services from late June 9 through June 10, 2025, Pacific time. The total impact window was 15 hours 24 minutes, with partial-outage and degraded-performance classifications, followed by resolution.
A long incident window is not the same as a complete outage for every user. The useful lesson is operational: what work can the team keep using, what requires an online service, and how can an interrupted assignment resume?
Separate preserving work from continuing computation
A saved report, project folder, or decision record can remain useful when a remote service is unavailable. That does not make an online model call, browser task, or connected-system update available without the service it needs.
- Keep important deliverables and approved decisions in usable files.
- Record dependencies and a fallback process for interrupted tasks.
- Check actual system state before retrying a send, publication, or other consequential action.
A PRACTICAL THADDEUS WORKFLOW
Keep the work, not just the conversation.
Thaddeus stores core project state and generated files locally and supports continuity across assignments. Use those records and portable exports to preserve completed work and prepare a deliberate restart, while identifying operations that still depend on external services.
Try this assignment
Save the completed research brief and its sources in the project. Record what is finished, what remains, and which steps need online services. Before resuming any external action, check whether it already completed so we do not repeat it.
Local-first is not fully offline. Timers and schedules do not guarantee continuous availability, and preserved files do not make remote AI or connected services work during an outage.
Sources & further reading
- June 2025 ChatGPT and API incident write-up ↗
OpenAI Status. June 9 to 10, 2025, Pacific time.
Educational information, not a security audit, professional advice, or guarantee. The assignment is an example to evaluate, not a completed demonstration. Historical incidents and product capabilities do not establish comparative safety. Confirm current policies and agreements for your intended workflow.