-
Notifications
You must be signed in to change notification settings - Fork 30.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Node.js website unavaliable #47120
Comments
i can't even install node me |
@ovflowd This sounds like it could be due to nodejs/nodejs.org#4991? |
@tniessen seems to be working for me. Both on CloudFlare and non-CloudFlare. But this page was broken a few hours ago indeed. I think we can close this for now and keep monitoring. |
@TimDaub Is this still an issue, even after a hard refresh? |
This also causes all binary releases to be unavailable for all GitHub CI. please fix this ASAP |
related nodejs/nodejs.org#5149 |
@himself65 please mind your tone 😅 we're working on the clock for the last 3-4 hours non-stop. The issue is something on CloudFlare side, due to cache invalidation issues, mixed with our server becoming unresponsive because of the sheer amount of requests coming in and the clients also caching these 404s. So it's a mix of a lot of things, and right now we're working on all angles but we're sadly outmanned. |
Also, the issue doesn't affect all binaries neither all releases. It is a spotty issue that changes from time to time. |
Sorry for the rudeness. |
seems to work for me again, thx |
URLs like these still seem to be down: This on the other hand seems to work: |
Same issue here, also with node docker images :/ |
Please see nodejs/nodejs.org#5149 (comment). Depending on your physical location and depending on which particular file you are attempting to access, you might see unexpected 404 status codes. We expect this to be resolved as we manually purge the cache for popular URLs, which takes a few minutes. The remaining URLs should be resolved within a few hours. |
Version
No response
Platform
No response
Subsystem
No response
What steps will reproduce the bug?
How often does it reproduce? Is there a required condition?
always
What is the expected behavior? Why is that the expected behavior?
shows the docs page
What do you see instead?
404 error
Additional information
No response
The text was updated successfully, but these errors were encountered: