Massive Inconsistent availability figures per satellite

[Alexey]

Each satellite checks your node independently, so it’s perfectly fine when they have an own reputation score for your node.
You may use these scripts to figure out, when your node was not available:

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…

Please search for “ping satellite failed” but not “ratelimit” in your logs, it may have details why your node was not available.

The next step would be to analyze your infrastructure for problems during these periods. It also possible, that your DDNS hostname could not be updated in time, or it has resolution problems (cannot be resolved from time to time due to DNS misconfiguration on DDNS provider’s side).
See

Your node has been disqualified saltlake.tardigrade.io:7777

@Pac in your case I found the record based on the port number. Looks like your DNS name is not very reliable. I tried to resolve it, sometimes it works, sometimes it doesn’t. (Even if I use 1.1.1.1 or 8.8.8.8 dns servers). Looks to be a problem on this dns provider. We checked our DNS servers and everything was fine. I would suggest to use different host names. (no-ip.com and dynv6.com were recommended for me.) If you changed your hostname, ping me, and I can fix the DQ state for you.