告诉 HN：HN 宕机了
63 分•作者: uyzstvqs•大约 24 小时前
- HN 在所有需要身份验证的请求上都出现了 502 Bad Gateway 错误。它仍然对少量未经身份验证的请求做出响应，这些请求很可能是使用了缓存页面，但这些页面并未更新。/newest 页面上的最后一篇文章显示“0 分钟前”，但实际上要早得多（格林威治标准时间下午 1:32:57），而且并非最新文章。
- 这个状态页面实际上指出了这次故障：https://hackernews.onlineornot.com/ - Hund 和 Statuspal 提供的页面并未显示这次故障。
- 故障前的最后一篇文章是 https://news.ycombinator.com/item?id=46301823（格林威治标准时间下午 1:39:59）。最后一条评论是 https://news.ycombinator.com/item?id=46301848（格林威治标准时间下午 1:41:54）。
- 故障前，平均每条评论大约需要 4 秒钟。基于此，HN 很有可能在格林威治标准时间下午 1:41:58 宕机。
查看原文
- HN errored on all authenticated requests with 502 Bad Gateway. It did still respond to a limited amount of unauthenticated requests with presumably cached pages, which did not get updated. The last post on /newest claimed "0 minutes ago", but was actually much older (1:32:57 PM GMT) and not the newest post.<p>- This status page actually identified the outage: https://hackernews.onlineornot.com/ - Pages by Hund and Statuspal did not show the outage.<p>- The last post before the outage was https://news.ycombinator.com/item?id=46301823 (1:39:59 PM GMT). The last comment was https://news.ycombinator.com/item?id=46301848 (1:41:54 PM GMT).<p>- There was an average of ~4 seconds per comment just prior to the outage. Based on this, HN likely went down at 1:41:58 PM GMT.