Shows an Incorrect API Key error...which is weird. Nothing on the status page. (EDIT: Added to incident page: https://status.openai.com/incidents/01M3DCNWMW57HYK8FJ5FBFPA...)
Per Twitter/X this appears to be widespread
https://status.openai.com/incidents/01M3DCNWMW57HYK8FJ5FBFPA...
What happens when your entire day is depended on saas models? Anyone even considers using their locally hosted models in order to finish their work? Do you trust your local models to do any of you outstanding work? Do we even understand the code anymore to manually fix anything?
I don't know if related, but a half hour before it fully went down, it was flagging all of my requests as security violations which was bizarre.
Appears to be back online.
This outage is not just Codex, right? I am just using GTP-6 Astra for some administrative prompts and it has been returning, "Error in message stream", for several minutes now.
Friday afternoon in the US I guess, perfect time for things to go wrong.
They are not having a good week.
I am not even excited about the expected reset because the model quality has been less than stellar.
Testing something, can you guys post useless replies like "cool man" or "...okay?"
This outage started a lot longer than 13mins ago. At least now I have an excuse to leave the office and have a long coffee break.
These NS agents could have been dedicated to better platform resilience I guess.
ugh I thought it was just me, ended up reinstalling everything from scratch
was thinking there was something going on with my local network and realized I should look at HN...thank god it's not just me.
They getting ready to release a new model?
Codex is back
Nevermind. Switching to Opus 5.5.
It's crazy how fast these things became load-bearing
thank god I'm not the only one, pulling my hair out hitting ctrl+z ... Happy Friday I guess
Don't deploy to production after noon on Friday!
unrelated but also chatgpt is super buggy, try generating an image, click stop, now wong be able to send another message until you reload, this issue has been there for months
Somebody really wanted to cross one off the weekly TODO list :)
Codex took an unannounced early day off for the weekend. It happens.
inb4 Aeon
I amusingly was doing a "cleanup" of my various harnesses when this happened. Claude Code has a /doctor command which was actually quite helpful, so I decided to swap over to Codex and ask it to do a self-analysis and give me some recommendations if there's something I need to clean up. The response was a connection issue. And so was the next. And the next.
Took me the past 20 minutes to finally check for a status page and realize I hadn't broken something. Not before I created a new project, checked the settings to see my usage numbers, closed and opened the desktop app a couple times, logged out and logged in, used my phone to see if it was a general ChatGPT outage, and generally messing around trying to figure out what I had done.
I mean, you never know... it could have been my prompt that took the whole service down. (Sorry if it was).
[dead]
It easily took over 15 minutes of it being down for it to even register on the status page. The status page showed fake green for this long. This is as verified by myself and by many users on Reddit r/codex who have timed posts and comments. It is a scam.
If Reddit is more useful than a status page, then what good is a status page? A lie is a lie. 15 minutes can cause someone to reinstall their entire software stack as is documented on this page. For the sites I administer, I have immediate reporting, and I have never had a false alert.
At last someone ffin noticed! I've observed it for at least an hour before the announcement.
So much for status reporting from openai. Must have been vibe coded.
I'm seeing this locally (on the desktop MacOS app): unexpected status 401 Unauthorized: Incorrect API key provided