I am not that smart. I will admit though I do run my weather site on the server too.That’s besides the issue with this site consuming more battery resources than other sites. I just figured Scott was mining bitcoins on the side while we were connected to his site, or someone was paying to utilize our CPU resources while kicking back a little to Scott to help keep the lights on.
Doesn't really say much as the timeout could be intentional as they could block ICMP responses.... The reverse traceroute is important too which we don't have as the path it takes might not involved cogentco at all. Here is from SFO.43 seconds for the initial request to return and then it all loaded, it did this a couple times before I opened inspector.
View attachment 178583
I do have a timeout on my tracert to satguys between twelve99 and cogent.
View attachment 178584
Most times it's actually fine but then there are the others.I meant one can also have a reverse traceroute script installed on SG so the members can show the path back to them from SG as all we have now is the forward traceroute so with both we can see the whole picture. Here is a sample reverse traceroute script:
https://github.com/HSAnet/reverse-traceroute
Personally though, I have not experienced the slowness yet but it could be the time I am visiting the forum and actively using it.