Changelog v1.16.1

[baker]

@littleskunk

Downtime Tracking Enabled
We still had a feature flag from the old days and the audit service didn’t report back offline nodes. This is now fixed. We expect to see a good uptime score on the storage node dashboard.

I believe this means that downtime tracking has been enabled, but DQ for downtime has not. The current plan once DQ for downtime is enabled is to start with up to 288 hours of downtime before disqualification (although this is a simplification since there are other factors at play). The hours of allowed downtime is expected to be reduced as the system is optimized. See this post for more info:

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…