How to make lossy, long fat pipe network download faster?

[Logan]

Hi guys.
My network is not slow (varys, 10-90Mbps), but have really high latency (200-900 ms) and high packet loss (10-30%).
This prevent me from using the full download bandwidth on most sites, but download from google/youtube is not affected, as well as any upload (because Google and I use BBR TCP congestion control, which don't care about packet loss).
The problem is, TCP congestion control is for senders, and I cannot change websites' server settings. So... any idea how can I get aroung this problem?
Thanks!

[mariush]

I'd suggest looking into a download manager that supports resume and multiple download threads (to download  multiple sections of a single file in parallel, if the remote server allows it).

First such tool that comes to mind is FlashGet but its years since I last used it, and I don't know anything about the latest version so can't vouch for it.
Maybe check out JDownloader for an open source alternative : https://jdownloader.org/download/index

Other than that... all that comes to mind is maybe you'd be willing to spend 5-10$ a month on a VPS and set up a VPN or a proxy server on it, and maybe download bigger files on it, then ftp the files to your computer.

If you're in a country they accept, Kimsufi has a promo now with VPSes starting from 1$ a month for the first year ( 1 core, 2 GB ram, 20GB disk space and 100 mbps unmetered, well probably under 1 TB then it's capped at 10mbps for the rest of the month) : https://www.ovhcloud.com/en/vps/
There's tutorials on how to set up a proxy or a ftp server out there, and the specs are enough for that.

[Foxxz]

I would also suggest setting up a proxy server that has a better connection where you can tune the connection parameters between the proxy and your lossy endpoint.

[mapleLC]

I don't know what all this google bullshit you are using is, but I suspect it's data mining trash.

https://docs.pi-hole.net/guides/dns/unbound/

DNS is a cause for latency, I would recommend pi-hole.  In addition to your local DNS cache, you filter all the trash on the internet (especially from google) that is data mining your home.

My installation has 23% of ALL internet traffic requests in blocked.  23% is a gigantic number... almost one of every 4 HTTP requests is to a data mining junkhole.  My internet was noticeably quicker right after installation.

[ejeffrey]

An http proxy with a more reliable connection would seem to be the best approach.  Then you control both sides of the connection that traverses the lossy link.  Making sure http/3 is enabled might help but right now most clients enable it by default, the bottleneck is the servers.

[Halcyon]

Rather than treating the symptom, is it possible to treat the cause, in other words, look into why your packet loss figures are so high.

Is it a fault on the line causing retransmissions? If so, your ISP should be fixing the issues. Even 10% is very high. It should be zero pretty much all the time if everything is working as it should.

[ejeffrey]

Good point. Also, how is that measured?  Are you sure it's that high in real world use? I would expect any standard TCP implementation  to be essentially unusable with 10% packet loss.

Is this a commercial ISP? I wouldn't expect any commercial ISP to be able to offer such a service for this reason.  If it's a custom setup and you have access to both sides of the link then there are more options.