14 comments

[ 2.7 ms ] story [ 5.0 ms ] thread
I'm seeing this locally (on the desktop MacOS app): unexpected status 401 Unauthorized: Incorrect API key provided
Good thing they don't promise SLA's.
ugh I thought it was just me, ended up reinstalling everything from scratch
Next time, wait for five to ten minutes and check r/codex.
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.
Sounds like you've never worked in Ops. Having immediate triggers for outages will absolutely flood you with useless alerts. 15 minutes is pretty normal before alerting as there are a zillion unsolvable intermittent issues (and non issues) that can cause a loss of connection to things.
On the contrary, what you're doing is "ops theater", not real ops. If you were doing real ops, you most definitely wouldn't have tolerances exceeding 3*2 = 6 minutes. People like you cost the organization customers. You've no idea how many people switch to a competitor due to your mis-ops.
I'm sorry but you clearly don't know what you're talking about. It can take 10 or more minutes to even verify your signal is correct.
ChatGPT also seems down for me.
It has been down in Work mode, not in Chat mode.
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.
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.

These NS agents could have been dedicated to better platform resilience I guess.