OpenAI opened a status-page incident on October 13, 2026, for degraded performance in GPT-6.1 Sol Codex and Work mode. Its latest update reads: We have applied the mitigation and are monitoring the recovery.
What Happened?
- The incident page lists 1 affected component under ChatGPT and 4 affected components under Codex.
- OpenAI’s first notice to mitigation update took 80 minutes, by the page’s own timestamps.
- The status now reads Monitoring, not resolved. The page names no cause.
- OpenAI says availability metrics are reported at an aggregate level across all tiers, models and error types.
The incident names GPT-6.1 Sol Codex and Work mode as the affected scope. The second update repeats it as Degraded performance on GPT 6.1 Sol Codex and Work mode. That wording is the only description of the problem on the page.
The mitigation came after a sparse four-post trail
OpenAI’s status page logged its first update at 08:10 AM and its mitigation update at 09:30 AM, both read here as UTC. The two posts between them add no detail. One restates the incident title, and the other repeats the investigating line.
The investigating line reads, We are investigating the issue for the listed services. A Technobezz timeline lists the same four updates at 4:10, 4:18, 4:22 and 5:30 a.m. Eastern. The page itself does not label its timezone.
The record leaves cause and impact blank
OpenAI’s incident page gives no root cause, error rate or count of affected users for GPT-6.1 Sol Codex or Work mode. It offers one caveat instead. The page says Individual customer availability may vary depending on their subscription tier as well as the specific model and API features in use.
A team on one plan or model can therefore see a different picture than the aggregate one.
As the team is monitoring the issue, means a fix is in place and recovery is unconfirmed. The next marker is a Resolved update on the incident page. Until a Resolved update posts, teams that depend on Codex can keep a fallback workflow ready, which helps reduce disruption risk without guaranteeing continuity.
