that’s the end goal, or what storj labs would like people to keep it to…
but i’m sure in that there will also be room for extended downtime, in that so long as the avg is maintained, even amazon aws datacenters have downtime, as demonstrated a week or two ago when most of the northamerican accessed websites run on aws was inaccessible because aws added so many computers to their datacenter that their network or whatever errored out… and took the better part of a day for them to figure out what was happening.
so 5 hours pr month is unreasonable for basically anyone, storj labs would also have to accept that natural disaster and whatever can take down large portions of nodes which will then have to be allowed for extra downtime atleast in a short period.
so yeah long story short… they want 5 hours per month, but current also accept that is a near impossible goal which they will have to figure out a way that works for everybody.
so currently its 288 hours and then a node gets suspended…
however my main node lost internet for 9 hours and that resulted in 120gb of data got deleted, so it’s not like extended downtime is free… the network will ensure data is available and if it considers you a risk, data will be moved to other places, i’m sure it’s much more complex than that… but thats how i understand it… you might also be lucky that it doesn’t change anything at all…
my main node is 14.5 TB so not really a bit hit… less than 1% so doesn’t really change anything.
so atleast for now, aim for 5 hours of dt avg pr month, but less can work.
if you hit the 288 hour downtime in a month, your node will enter suspended mode, which means it will not get any more ingress, it will still be able to earn money from egress i believe.
after 1 month of stable operation the node will go out of suspension, if the problem persists the plan is that it can get Disqualified / DQ but not sure if that part is active yet… nor how long that takes.