告诉HN:HN宕机了

63作者: uyzstvqs大约 3 小时前原帖
- HN 在所有经过身份验证的请求中出现了502 Bad Gateway错误。它仍然对有限的未认证请求作出了响应,返回的可能是未更新的缓存页面。最新帖子在/newest上声称“0分钟前”,但实际上已经很久以前(格林威治标准时间下午1:32:57),并不是最新的帖子。<p>- 这个状态页面实际上确认了故障:https://hackernews.onlineornot.com/ - Hund和Statuspal的页面没有显示故障。<p>- 故障发生前的最后一条帖子是:https://news.ycombinator.com/item?id=46301823(格林威治标准时间下午1:39:59)。最后一条评论是:https://news.ycombinator.com/item?id=46301848(格林威治标准时间下午1:41:54)。<p>- 在故障发生前,每条评论的平均响应时间约为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 &#x2F;newest claimed &quot;0 minutes ago&quot;, but was actually much older (1:32:57 PM GMT) and not the newest post.<p>- This status page actually identified the outage: https:&#x2F;&#x2F;hackernews.onlineornot.com&#x2F; - Pages by Hund and Statuspal did not show the outage.<p>- The last post before the outage was https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=46301823 (1:39:59 PM GMT). The last comment was https:&#x2F;&#x2F;news.ycombinator.com&#x2F;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.