I need a work-around - if one exists.

I have a free trial with historyhit.com. During the day, it's OK, but in the evening it's terrible - far too slow. I investigated.

dig returns 3 IPs for historyhit.com. I did a traceroute for each. They rattle around my isp, and at no.4 the route gets to some Irish trunk router. After that, traceroute is all stars, all the way to 30. Each one looks identical.

So I tried a whois on the IPs. It turns out they're all in an Amazon data centre in Dublin's City West, not 12km from where I live! The trunk router I mentioned is in Clondalkin, again 12km or so from me. They would be nearer to each other. But I'm being routed via outer Mongolia or Timbuktu

So, I need a work-around - if one exists. Failing that, I would like advice on the appropriate action to take.

Is that a normal web site? If so, then use SSH with the -D option to create a SOCK5 proxy for your browser. You can even start a new, unique profile just for that session if you wish. Then it would be a matter of choosing a destination for SSH which takes the alternate route to your history site.

(Note that this method cannot work if HTTP/3 goes into wide spread deployment.)

Or, less productively, file a trouble ticket with your ISP.

I don't get your drift at all. I'm not working in this stuff. I hurredly covered CCNA 1-4 over 2 years of engineering lectures 7 years ago. We didn't read standards.

What I reckon is that what I'm calling a trunk router [inex1.dub2-br-tra-r2.amazon.com = 194.88.240.32] is in the West of the capital, and is probably routing stuff west to the underwater Atlantic cables to the Excited States. The historyhit website isn't 10km from that in CityWest, but my connection is probably going through heavy traffic over in the Excited States before coming back.

I did contact historyhit.com, pointing out that their 3 IPs seem to be served from one place; and that I can't get at it. I doubt my isp will do much but I can try.