High latency node (part deux)

Hello again,

I was once again experiencing a frustrating and inconsistent issue with my backups. I use both Restic and BorgBackup, which use scp/sftp tunnels to backup.

Unfortunately, that means they are sensitive to disconnects and unstable connections. This prompted an entire day of debugging and network testing my LAN, the servers to which I'm backing up, and testing various network configurations.

I have tested many things, including but not limited to:

• Disabling ipv6 and only using ipv4
• Using non DFS channels
• Ratelimiting my upload
• Using 2.4ghz only, not 5 or 6ghz channels
• Factory resetting my modem/router
• Rebooting the modem/router
• Uploading to a BorgBase US server
• Uploading to a BorgBase EU server
• Uploading to a Hetzner DE server
• Uploading to a Hetzner Fin Server
• Changing the upload network buffer
• Scp'ing and rsyncing the files over SSH instead of Borg/Restic
• Altering the SSH keepalive settings (enabled or disabled; changing ServerKeepAlive{,Max} values to recommended settings)

Not to be deterred, I then suspected that my network is fine, but there is a hop somewhere that is causing rapid inconsistent disconnects.

And wouldn't you know it, ye olde node from this thread (https://forums.xfinity.com/conversations/your-home-network/high-latency-node/66ad86a759bf556396a1e032) has reappeared as a high-loss node, consistently.

That thread mentions be-300-arsc1.sacramento.ca.ccal.comcast.net.

I see two extremely high loss nodes (see image)

• be-300-arsc1.sacramento.ca.ccal.comcast.net has ~90% loss on this route
• lag-39.ear3.sjo1.sp.lumen.tech is even worse

Please please please investigate this this time. This does not appear to be an issue on my end.