Quic misconfigured even with ports open and yougetsignal.com tells it works

[Alexey]

@Gaggenau

QUIC: couldn’t connect to node: rpc: quic: context deadline exceeded, so does that mean that it does not work?

yes. Did you change -p options to have it mapped?

Step 4. Configure QUIC - Storj Docs

@Gaggenau

i just didn’t want to get disqualified, espcially because the online % on the satelittes was going down, even tough the docker have an uptime of 38H and i have not had any drops in my internet connection.

Your node should be online for the next 30 days to recover. Each downtime requires an additional 30 days to recover.
See

How is the online score calculated? - Storj Docs

Just keep it online. You may also check, when your node was not available for the satellites:

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 `…