← Back to the carnage
OPENAI
🔴 OpenAI discovered their infrastructure provider is having a moment—elevated error rates across images, batch, fine-tuning, realtime, embeddings, and Codex. They're "working on mitigation" which is corporate for "we're calling them back and being very stern about it.". (Auto-resolved: no updates in 24h)
// The official story
Elevated error rates
// Status page says
Status: Identified We have identified that users are experiencing elevated errors for the impacted services. We are working on implementing a mitigation with the downstream infrastructure provider. Affected components Images (Operational) Batch (Operational) Fine-tuning (Operational) Realtime (Operational) Embeddings (Operational) Codex Web (Operational) Codex API (Operational)
🔗 Official status page (for the PR-approved version)
https://status.openai.com//incidents/01KY7SX5MYJ2BP51X5MXAPYX71Openai'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)