I alas expect moria to be down until at least Monday, due to surprise hardware fixes. But with luck, once this particular episode does finish, we might have some new hardware and things will be on a better trajectory. ________________________________________ From: tor-consensus-health <tor-consensus-health-bounces@lists.torproject.org> on behalf of gk@torproject.org <gk@torproject.org> Sent: Friday, September 30, 2022 3:09 PM To: tor-consensus-health@lists.torproject.org Cc: adejoode@gmail.com Subject: [tor-consensus-health] Consensus issues ERROR: Unable to retrieve the consensus from moria1 (http://128.31.0.34:9131/tor/status-vote/current/consensus): Failed to download from http://128.31.0.34:9131/tor/status-vote/current/consensus (URLError): <urlopen error timed out> ERROR: Unable to retrieve the consensus from dizum (http://45.66.33.45:80/tor/status-vote/current/consensus): Failed to download from http://45.66.33.45:80/tor/status-vote/current/consensus (URLError): <urlopen error timed out> ERROR: Unable to retrieve the vote from moria1 (http://128.31.0.34:9131/tor/status-vote/current/authority): Failed to download from http://128.31.0.34:9131/tor/status-vote/current/authority (URLError): <urlopen error timed out> NOTICE: Consensus fetched from gabelmoo was missing the following authority signatures: dizum, moria1 NOTICE: Consensus fetched from maatuska was missing the following authority signatures: dizum, moria1 NOTICE: Consensus fetched from Faravahar was missing the following authority signatures: dizum, moria1 NOTICE: Consensus fetched from longclaw was missing the following authority signatures: dizum, moria1 NOTICE: Consensus fetched from bastet was missing the following authority signatures: dizum, moria1 WARNING: The following authorities are missing from the consensus: moria1