No change on Suspension or Audit statistics after 3 days of actual downtime: why?

[jeremyfritzen]

I think the downtime calculation is described on these 2 posts below.

In a nutshell, what I understand is:

• the downtime score is based on audits (i.e. audits requests sent by the satellites to the node)
• the node may receive a varying number of audits from satellites
• then, for a given node, the score may be different depending on the satellite we are considering.

Please correct me or complete if I’m wrong or missing something.
(would be really nice to have a topic on this on https://support.storj.io/)

Changelog v1.12.3

I have an update for you. The storage node dashboard API contains a new uptime score. By default it is 1 aka 100%. It is not visible on the storage node dashboard. The score gets updated via audits. The currenty default settings are: # The length of time to give suspended SNOs to diagnose and fix issues causing downtime. Afterwards, they will have one tracking period to reach the minimum online score before disqualification # overlay.audit-history.grace-period: 168h0m0s # The point below whi…

Changelog v1.12.3

One update on the downtime tracking topic: If you managed to collect too much downtime you will get suspended first. The satellite gives you 7 days to fix the issue and additional 30 days later the satellite will make a decsision. So lets say we are strict and would suspend for 48 hours downtime and you managed to be offline for 2 days in a row. You get your storage node back online but these 48 hours of downtime will not go away for the next 30 days. You would be suspended for 30 days. Luckily…