There are still problems for everybody, so it doesnāt seem to be a peering problem (which can be the case in specific networks). Regarding the network, I found this: https://docs.hetzner.com/robot/dedicated-server/troubleshooting/network-diagnosis-and-report-to-hetzner/
And for the last hop outside your local network, it looks good from a host at hetzer (not the same datacenter, but probably not that different):
HOST: host.example.com Loss% Snt Last Avg Best Wrst StDev
1.|-- static.ip1.clie 0.0% 1000 0.2 0.1 0.1 1.0 0.1
2.|-- static.ip2.clients. 0.0% 1000 0.6 0.6 0.4 13.8 0.9
3.|-- core24.fsn1.hetzner.com 10.9% 1000 7.0 5.7 0.4 93.8 9.1
4.|-- core0.fra.hetzner.com 0.0% 1000 9.7 8.0 5.0 54.3 6.1
5.|-- dx1.in.airtel.com 0.0% 1000 20.2 23.9 20.1 181.9 12.2
6.|-- 125.23.238.225 0.0% 1000 187.6 186.9 181.6 275.5 5.1
I was still seeing a few 500 errors this week, it was perhaps a bit worse two weeks ago.
The curl-test in my post above is still exactly the same. Itās just a bit above 60s, so Iām wondering if there is a timeout that is triggered after 60s.
I tried to ping the Nextcloud team on github (experiencing a lot of 500 errors with help.nextcloud.com... Ā· Issue #1613 Ā· nextcloud/nextcloud.com Ā· GitHub), if you have problems as well, give the original post a thumbs up to increase the visibility.