Dropping online status

[Alexey]

The online score will return to its previous state, because it’s calculated over 30 days window. The historic lowering of the online score is not evacuated yet from the checking window

@daki82

i came to assist with a graphic.

If there are no new missing audit checks

My uptime should be 100% on all satellites i have not gotten any uptime robot notifications of downtime in months

Would you mind to provide dashboard from the uptimerobot? And also, please, provide result of the command: PowerShell 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} } bash for item in `…

Then it should recover in the next 30 days online.

It’s based on the analyze above

Dropping online status

Confirmed fixed on my end - thanks @elek. I re-ran the exact same measurement after your k8s/firewall fix: one hour of continuous SYN/SYN-ACK capture at my WAN interface, same vantage and same analysis as before. The in-range failures are gone. Source Source port Flows Failed Rate Storj sat (79.127.163.0/24 + 79.127.205.0/24) 30000–32767 62 0 0.00% (was 60/60 = 100%) Storj sat (79.127.163.0/24 + 79.127.205.0/24) anything else 2,934 0 0.00% every other network 30000–32767 140 0 0.00% …

The mentioned fix for the cache issue

Dropping online status

Usually - once a week, but sometimes there are point releases. I usually checks by the tag. I took a hash 73c543d796ea2ef5f557222e432ccd15268b05cd, then search for it on GitHub, it’s here contact: use WithForceDial for PingBack and PingMe dials · storj/storj@73c543d · GitHub Then I take a look on tags, there are no tags, only main, so it’s not released yet. Perhaps it would be released on the next week, like on 2026-08-09T17:00:00Z (UTC) (don’t check the time, it’s not a promise, it’s an est…

Is not released yet, but it should affect only nodes with frequent IP changes, as far as I understand.