Sespension & Audit show warning


Noticed that some of the addresses in the Suspension & Audit section show warnings.
Node is online. QUIC status ok.

Hello and welcome. The percentages of the online status are affected either by disconnections of your internet line or by very slow pings and therefore the satellite is as if it did not find you online. Check these things out. To check the response pings of your nodes go to Storjnet.info

Bye

Node 24/ online, about ping duno.
Let’s say europe-north-1.tardigrade.io I have ping 25 ms, but still got a warning for this domain name.
And what means slow ping, 200ms, or 1000ms?

The ping to the satellite doesn’t matter, since data transfer is performed directly between the customer and the node. The satellite is only address book, payment processor, audit and repair services, it doesn’t proxy data transfers.

What @digitalfrank is meant perhaps related to communications between the satellite and your node during audit - if your node is unable to provide a piece for audit for the 5 minutes and did the same two more times for the same piece - such audit considered as failed. But in such a case the audit score will be affected.
The online score is affected only when your node did not answer at all - so it were offline for that satellite.
Please note, the running node != online node. The node considered online if it’s able to answer on audits with any result (the audit result doesn’t matter for the online score).
You can check when your node was offline with this script:

Then you can search in your network infrastructure - why your node was not available for audits on that time.

It’s also helpful to configure external online monitoring like described in this guide: How do I check my node when I'm away from my machine? | Storj Docs

Ok, but still do not get why
eu1.storj.io:7777 has 98,94% online time
saltlake.tardigrade.io:7777 has 91,67% online time.
Should they have the same online time?

Afte

`foreach ($item in ((Invoke-WebRequest http://localhost:14002/api/sno).Content | ConvertFrom-Json).satellites.id) {
    ((Invoke-WebRequest http://localhost:14002/api/sno/satellite/$item).Content | ConvertFrom-Json).auditHistory.windows |
        Where-Object{$_.totalCount -ne $_.onlineCount} | ForEach-Object{Write-Host $item; $_ | Format-Table -AutoSize}
}`

Getting

12tRQrMTWUWwzwGh18i7Fqs67kmdhH9t6aToeiwbo5mfS2rUmo

windowStart          totalCount onlineCount
-----------          ---------- -----------
2022-04-12T00:00:00Z          2           0


12tRQrMTWUWwzwGh18i7Fqs67kmdhH9t6aToeiwbo5mfS2rUmo

windowStart          totalCount onlineCount
-----------          ---------- -----------
2022-04-12T12:00:00Z          1           0


1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE

windowStart          totalCount onlineCount
-----------          ---------- -----------
2022-04-12T12:00:00Z          1           0


121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6

windowStart          totalCount onlineCount
-----------          ---------- -----------
2022-04-12T00:00:00Z         11           5


121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6

windowStart          totalCount onlineCount
-----------          ---------- -----------
2022-04-12T12:00:00Z         10           6


12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S

windowStart          totalCount onlineCount
-----------          ---------- -----------
2022-04-04T12:00:00Z         71          70


12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S

windowStart          totalCount onlineCount
-----------          ---------- -----------
2022-04-05T00:00:00Z         44          38


12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S

windowStart          totalCount onlineCount
-----------          ---------- -----------
2022-04-05T12:00:00Z         57          56


12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S

windowStart          totalCount onlineCount
-----------          ---------- -----------
2022-04-12T00:00:00Z         82          42


12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S

windowStart          totalCount onlineCount
-----------          ---------- -----------
2022-04-12T12:00:00Z        137         133


12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs

windowStart          totalCount onlineCount
-----------          ---------- -----------
2022-04-12T00:00:00Z         79          46


12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs

windowStart          totalCount onlineCount
-----------          ---------- -----------
2022-04-12T12:00:00Z         10           8


12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs

windowStart          totalCount onlineCount
-----------          ---------- -----------
2022-04-13T12:00:00Z         52          51


12rfG3sh9NCWiX3ivPjq2HtdLmbqCrvHVEzJubnzFzosMuawymB

windowStart          totalCount onlineCount
-----------          ---------- -----------
2022-04-12T00:00:00Z          1           0

Each satellite checks and calculates an online score independently of each other. Online score is affected by GET_AUDIT requests. These requests are more frequent the more data you hold from a given satellite. So for the same time period where your node is unreachable, it is possible that some satellites try and audit you more than others, or some might not try at all during that time period.

2 Likes

Sorry @Alexey rightly you’re right I didn’t remember. The audits if you accept the file or not, the online only if you are reachable. However, I wanted to remind @Maksvell that the percentage of online takes time to go back, it is calculated on the average time of online presence of the node of the last 30 days. So to get back to 100% you have to wait at least 30 days from the last time you were offline.

1 Like