OPENAI

🟡 ChatGPT, Codex, and the Response API collectively decided to stop working across login, conversations, and basically everything else. OpenAI's status page is doing that thing where it says 'investigating' while engineers frantically Google 'why is everything broken.'. (Auto-resolved: no updates in 24h)

⏰ Jun 03, 2026 Fixed (for now) spotted via status_rss

// The official story

Elevated error rates on Codex, ChatGPT and Response API

// Status page says

Status: Investigating We are investigating the issue for the listed services. Affected components Login (Partial outage) Conversations (Partial outage) Responses (Partial outage) Codex Web (Partial outage) App (Partial outage)

🔗 Official status page (for the PR-approved version)

https://status.openai.com//incidents/01KT5XJ5ATD6RMYP908WS69FVD

Openai's Greatest Hits

🟢 OPENAI 3d ago

🟡 OpenAI's investigating why some workspace admins can't manage plugins—turns out giving people control over their workspace was just a beta feature. Connectors/Apps decided to ghost the people actually trying to run things here. (Auto-resolved: no updates in 24h)

🟢 OPENAI 3d ago

🟠 OpenAI's Android app is playing content gatekeeper, showing "unavailable" errors instead of letting you actually chat. The fix is trickling out slower than a 2G connection. Web version works fine if you want to escape the mobile experience entirely. (Auto-resolved: no updates in 24h)

🟢 OPENAI 6d ago

🟡 OpenAI's desktop app decided Work threads are overrated. Users now experiencing the cutting-edge feature of threads that simply don't exist. Engineering team is 'investigating' what surely won't take 6 hours to fix. (Auto-resolved: no updates in 24h)

🟢 OPENAI 6d ago

🟡 OpenAI's desktop app decided threads were too mainstream, now refusing to create them for regular users. Codex is having commitment issues. Engineers are investigating whether this was a feature or a bug—spoiler: it's a bug. (Auto-resolved: no updates in 24h)