🚀 go-pugleaf

There's a problem somewhere on or near the satellite link, affecting
data coming in to Australia only. Outgoing data seems to flow quite
well, I guess any slowdown is due more to the loss of returning
acknowledgement packets than the loss of the outgoing packets
themselves.

I'm seeing something like 40% packet loss on average from sites all
over the US. The problem has been there for a couple of days at least.

Below are some traceroute fragments onto nearby networks in the US,
they seem to isolate the problem at or before the US end of the pipe.
Is there any official wisdom available?


 1  vic.GW.AU (128.250.1.1)  3 ms  3 ms  3 ms
 2  usa.gw.au (139.130.4.5)  7 ms  4 ms  4 ms
 3  arc2.nsn.nasa.gov (132.160.240.1)  568 ms  567 ms  567 ms
 4  ARC1.NSN.NASA.GOV (192.52.195.2)  568 ms *  571 ms

 1  vic.GW.AU (128.250.1.1)  8 ms  3 ms  3 ms
 2  usa.gw.au (139.130.4.5)  19 ms  4 ms  3 ms
 3  arc2.nsn.nasa.gov (132.160.240.1)  574 ms  566 ms  568 ms
 4  Palo_Alto.CA.NSS.NSF.NET (192.52.195.254)  568 ms  570 ms *

 1  vic.GW.AU (128.250.1.1)  44 ms  58 ms  4 ms
 2  usa.gw.au (139.130.4.5)  4 ms  4 ms  4 ms
 3  arc2.nsn.nasa.gov (132.160.240.1)  570 ms  568 ms  623 ms
 4  ARC1.NSN.NASA.GOV (192.52.195.2)  579 ms  602 ms  567 ms
 5  * * JPL1.NSN.NASA.GOV (128.161.4.2)  602 ms

 1  vic.GW.AU (128.250.1.1)  32 ms  3 ms  3 ms
 2  usa.gw.au (139.130.4.5)  3 ms  4 ms  3 ms
 3  arc2.nsn.nasa.gov (132.160.240.1)  566 ms *  566 ms
 4  t3-0.enss144.t3.nsf.net (192.52.195.253)  576 ms *  587 ms
 5  * t3-2.cnss9.t3.nsf.net (140.222.9.3)  582 ms  572 ms

--
Dan.