Another traceroute, same 204.2.229.234 packet loss. These are all done at different times of the day.

Tracing route to 204.2.229.10 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms RAC2V1S [192.168.1.1]
2 64 ms 23 ms 10 ms 142.254.237.25
3 54 ms 24 ms 33 ms agg61.mnvyca4302h.socal.rr.com [76.167.26.245]
4 17 ms 14 ms 19 ms 72.129.7.36
5 137 ms 21 ms 22 ms agg21.tustcaft01r.socal.rr.com [72.129.5.2]
6 17 ms 31 ms 22 ms bu-ether26.tustca4200w-bcr00.tbone.rr.com [66.109.3.232]
7 19 ms 17 ms 27 ms 66.109.5.247
8 26 ms 58 ms 33 ms las-b24-link.telia.net [62.115.156.224]
9 16 ms 17 ms 17 ms ntt-ic-326358-las-b24.c.telia.net [213.248.103.171]
10 18 ms 14 ms 15 ms ae-2.r23.lsanca07.us.bb.gin.ntt.net [129.250.3.237]
11 38 ms 26 ms 29 ms ae-12.r22.snjsca04.us.bb.gin.ntt.net [129.250.4.150]
12 31 ms 34 ms 30 ms ae-19.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.27]
13 32 ms 30 ms 31 ms ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
14 41 ms 34 ms 41 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [192.80.16.2]
15 39 ms 32 ms * 204.2.229.234
16 33 ms 36 ms 37 ms 204.2.229.10

Trace complete.