Yes, that's what I was thinking as well.
$ traceroute va2om.ampr.org traceroute to va2om.ampr.org (44.135.49.90), 30 hops max, 60 byte packets 1 gw.k5dat.ampr.org (44.92.0.81) 8.009 ms 8.739 ms 8.217 ms 2 ve2pkt.ampr.org (44.135.49.2) 82.958 ms 80.678 ms 83.147 ms 3 * * * 4 va2om.ampr.org (44.135.49.90) 118.908 ms 119.027 ms 126.604 ms
Lee K5DAT
On Tue, Mar 23, 2021 at 8:36 PM Dave Gingrich via 44Net < 44net@mailman.ampr.org> wrote:
44.127.48.1 is in Chicago with a 10 Gb interface. traceroute below shows it loops through UCSD, but the loss is between ve2pkt and ve2om.
-k9dc