AIToday
AI Coding AssistantsITmedia AI+Published: Sep 26, 2026, 10:00 JST

OpenAI Codex goes down about an hour, recovers 8:54 a.m.

OpenAI Codex goes down about an hour, recovers 8:54 a.m.

3 Key Points

  1. What happened

    OpenAI's Codex coding tool failed across web, API, CLI, and its VS Code extension starting before 8 a.m. JST on September 26; OpenAI confirmed the failure at 7:58 a.m.

  2. Why it matters

    A single outage erased every way developers could reach the tool for roughly an hour, and OpenAI called the cause an 'internal problem' without explaining it.

  3. What to watch

    The full impact hinges on whether Codex repeats the failure; OpenAI revealed no root cause, so watch for any further status updates from the company.

WHO IT HITSSoftware developers and engineering teams that rely on Codex for AI-assisted coding lost access to the tool through all its interfaces for about an hour, a reminder of the operational risk in depending on a single vendor's cloud service.

Not sure about something? Ask the AI

Questions and answers are published on this page.

Summaries like this, in your inbox every morning.

Context & Analysis

The incident unfolded quickly on the morning of September 26 Japan time. OpenAI confirmed the Codex failure at 7:58 a.m., and at 8:19 a.m. it advised users that they could access the tool by logging in with an API key. Full service returned at 8:54 a.m.

The disruption touched every way Codex can be used — the web version, API, CLI, and VS Code extension — which means developers had no workaround through another Codex interface during the hour. OpenAI attributed the outage to an 'internal problem' but gave no further detail, leaving the underlying cause undisclosed.

Whether the outage remains a one-off hinges on OpenAI's undisclosed diagnosis, so the company's follow-up status updates are the main thing to watch. For development teams that build Codex into daily coding work, the episode highlights how a single-service dependence can stall work when the service fails.

FAQ
How long was Codex down?
About an hour. OpenAI confirmed the failure at 7:58 a.m. JST and said all services recovered at 8:54 a.m.
What did OpenAI say caused the Codex outage?
OpenAI described the cause as an 'internal problem' but did not disclose details.
Did the outage affect ChatGPT or other OpenAI services?
No. ChatGPT and other OpenAI services were not affected.

Get the latest AI Coding Assistants news every morning

For example, today's edition would include:

  • Microsoft Copilot rebuilt with Home, Code, Autopilot tabsITmedia AI+ · 2h ago
  • Microsoft bundles Copilot AI into one app, usage-based pricingTop Companies AI · 6h ago
  • Shoeisha ships LLM eval book on September 24Top Companies AI · 6h ago

AI-summarized, only the topics you pick: one digest a day via Email, LINE, or Slack.

Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →

Ask AI

Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.

Questions and answers are published on this page.

Related Articles

Next articleDisney Picks Character.AI's Karandeep Anand as First CTO