Multiple engines are down: incident report for OpenAI
status.openai.com
Multiple engines are down: incident report for OpenAI
1–10 of 15 posts
Re: Multiple engines are down: incident report for OpenAI
#2That incident report is about an issue two days ago, the title of this post (which matches the page) is misleading.
They have however also been having issues today, at least with chatGPT, that looked to me to be issues with the web server configuration for their Next.js ChatGPT front end. It seemed to be returning the apps root html file for all requests for JS. All seems fine now though.
Re: Multiple engines are down: incident report for OpenAI
#3azure strikes again
Re: Multiple engines are down: incident report for OpenAI
#4That incident report is about an issue two days ago, the title of this post (which matches the page) is misleading. They have however also been having issues today, at least with chatGPT, that looked to me to be issues with the web server configuration for their Next.js ChatGPT front end. It seemed to be returning the apps root html file for all requests for JS. All seems fine now though.
[deleted]
Re: Multiple engines are down: incident report for OpenAI
#5That incident report is about an issue two days ago, the title of this post (which matches the page) is misleading. They have however also been having issues today, at least with chatGPT, that looked to me to be issues with the web server configuration for their Next.js ChatGPT front end. It seemed to be returning the apps root html file for all requests for JS. All seems fine now though.
When chatGPT is down, does it dream?
Re: Multiple engines are down: incident report for OpenAI
#6> Other issues are due to misbehaving bad hardware that need to be identified and removed from operation.
> We are actively working on addressing those limitations this quarter.
This always boggles the mind, but I've seen similar several times in the past on different HPC clusters. Hardware bugs that you just cannot seem to shake down, that are triggered just often enough to be a problem but seldom enough to be "impossible" to debug.
Re: Multiple engines are down: incident report for OpenAI
#7This was pretty annoying. I had a lot of homework and a science fair due today!
Re: Multiple engines are down: incident report for OpenAI
#8Looks like openai infra is either kubernetes based or nomad based. Would love to learn how the infra is actually setup.
Re: Multiple engines are down: incident report for OpenAI
#9That incident report is about an issue two days ago, the title of this post (which matches the page) is misleading. They have however also been having issues today, at least with chatGPT, that looked to me to be issues with the web server configuration for their Next.js ChatGPT front end. It seemed to be returning the apps root html file for all requests for JS. All seems fine now though.
When chatGPT is down, does it dream?
And does it dream of pets or cattle?
Re: Multiple engines are down: incident report for OpenAI
#10> Other issues are due to misbehaving bad hardware that need to be identified and removed from operation. > We are actively working on addressing those limitations this quarter. This always boggles the mind, but I've seen similar several times in the past on different HPC clusters. Hardware bugs that you just cannot seem to shake down, that are triggered just often enough to be a problem but seldom enough to be "impo…
That sounds like almost every dodgy disk drive I've encountered, and those clusters can have hundreds of them.