Hacker News new | past | comments | ask | show | jobs | submit login

HN was down much longer than I thought it was because the bad pages were stuck in caches. I had to do a force-reload to see that it was back up this morning.



HN was down much LESS time than I thought, because they told browsers that the "Sorry, but we're down" message should stay in cache until 2024! I believed the status report until today, because it didn't occur to me that someone would issue a status report on a temporary site-wide outage and instruct browsers to consider it permanent.


It was also down for much longer than a lot of services (e.g. status checkers) thought, since their only sensible method of working is to inspect the HTTP status. The result being that HN uptime looks better than it really is; of course, this isn't a paid service or something mission-critical, so exaggerating uptime doesn't really make much difference.


Similar problem on my phone and you can't Ctrl+F5 to force a reload on this device.


You can add a random query parameter to the url to force a reload if the option isn't given by other means.


Good point. Didn't think of that!


on some phones holding shift and enter will work for a hard refresh... (it's awkward to say the least)


same here, the only way i finally got out of bad state was to click on the logo to go to /news if i navigate to news.ycombinator.com i'm still seeing the "we're down" message in chrome.




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: