Is Chat-GPT 4 Down?

No, Clear your cache, try in a different browser
 
It works fine on my end. Maybe your accounts have reached the limit, or you have some kind of connectivity problem.
 
It works fine on my end. Maybe your accounts have reached the limit, or you have some kind of connectivity problem.
It seems like my 5G wifi has a problem. I tried to switch a 2.5G wifi and it worked fine. That is an interesting problem.
 
It seems like my 5G wifi has a problem. I tried to switch a 2.5G wifi and it worked fine. That is an interesting problem.
It's not that much weird, I have also observed it. Connecting on 5Ghz band gives faster speed comparative to 2.4 Ghz band but, it can travel comparatively shorter distance and is more prone to obstacles. So prefer 5 Ghz when you are closer to the router and 2.4 Ghz when far from the router.
 
Sometimes, they are working behind the scenes, updates, and some other mini-updates that happen often.

Anyway, so far, I got a few "errors" here and there (in a few months) but their uptime is pretty good.

Always check the OpenAI Status.

https://status.openai.com/
All the best.
 
It has been down for me on both browsers since yesterday. Cleaned cache, changed accounts, etc nothing works. Anybody still have this issue?

There are a lot of errors on the browser console too like:
- Assertion failed: Input argument is not an HTMLInputElement (onloadwff.js:71:827091)
- TypeError: ReadableStream.getReader: Cannot get a new reader for a readable stream already locked by another reader (vendor-defc32c99357af4a.js:1:87702)
 
Last edited:
yesterday I had problems all day, today I used it in the morning and was working fine.
 
It has been down for me on both browsers since yesterday. Cleaned cache, changed accounts, etc nothing works. Anybody still have this issue?

There are a lot of errors on the browser console too like:
- Assertion failed: Input argument is not an HTMLInputElement (onloadwff.js:71:827091)
- TypeError: ReadableStream.getReader: Cannot get a new reader for a readable stream already locked by another reader (vendor-defc32c99357af4a.js:1:87702)
Cleaning all browser data solved the problem.
 
Back
Top