← Back to the carnage
OPENAI
🟠 OpenAI's downstream supplier went sideways, turning ChatGPT conversations into a lottery for free users. They've slapped on a band-aid and are now watching it bleed. Current prognosis: monitoring, which is corporate speak for 'we'll know more when we know more.'. (Auto-resolved: no updates in 24h)
// The official story
Elevated errors in ChatGPT conversations for Free users
// Status page says
Status: Monitoring We’ve applied a mitigation and are monitoring recovery following an issue with a downstream provider. Affected components Conversations (Degraded performance)
🔗 Official status page (for the PR-approved version)
https://status.openai.com//incidents/01KZXVAJQ5XFH7PTM43XVPQWGJOpenai'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)