The uptime calculation is based on the number of attempts at pinging the storage node from the satellite. So, if the satellite pings less often, the uptime for a given node will change more slowly as well as less precisely…
There is nothing you can do except ensure that your node is online 24/7 … If your node goes offline and a satellite attempts to ping, the lost ping will count against your uptime calculation.
However, low uptime is not currently considered as a disqualifying factor.
If you’ve made copies of the databases for which to use the payment estimator, you can perform the calculation yourself using the following query:
sqlite3 --header --column reputation.db "select hex(satellite_id),(100.00*uptime_success_count/uptime_total_count) as uptime from reputation;"
Here are my percentages:
hex(satellite_id) uptime
---------------------------------------------------------------- ----------------
A28B4F04E10BAE85D67F4C6CB82BF8D4C0F0F47A8EA72627524DEB6EC0000000 99.5445561570852
004AE89E970E703DF42BA4AB1416A3B30B7E1D8E14AA0E558F7EE26800000000 99.5972426612966
84A74C2CD43C5BA76535E1F42F5DF7C287ED68D33522782F4AFABFDB40000000 99.5077355836849
AF2C42003EFC826AB4361F73F9D890942146FE0EBE806786F8E7190800000000 99.6753811373254
To display the raw counts:
sqlite3 --header --column reputation.db "select hex(satellite_id),uptime_success_count,uptime_total_count from reputation;"
And here are my raw counts:
hex(satellite_id) uptime_success_count uptime_total_count
---------------------------------------------------------------- -------------------- ------------------
A28B4F04E10BAE85D67F4C6CB82BF8D4C0F0F47A8EA72627524DEB6EC0000000 11584 11637
004AE89E970E703DF42BA4AB1416A3B30B7E1D8E14AA0E558F7EE26800000000 12859 12911
84A74C2CD43C5BA76535E1F42F5DF7C287ED68D33522782F4AFABFDB40000000 9905 9954
AF2C42003EFC826AB4361F73F9D890942146FE0EBE806786F8E7190800000000 17195 17251
You’ll notice that the total count column varies widely. This is because the satellites don’t attempt to measure uptime at a particular uniform time. The displayed uptime in the Web Dashboard is rounded up. So, on my Dashboard, I have the following four different uptime measurements:
- 99.5%
- 99.6%
- 99.5%
- 99.7%
My node has been down for a singular 10 hour stretch in the beginning of September because of a telephone pole fire which melted the fiber optic connections. Other than that my node has been running 100% of the time with zero network failures to my WAN connection.
So, my actual downtime should be listed as 0.368% … but two of the four satellites don’t agree with that actual realtime measurement and one is a little bit more generous than reality.