Same issue
Tracing route to 204.2.229.84 over a maximum of 30 hops

1 2 ms 2 ms 1 ms 10.0.0.1
2 10 ms 11 ms 9 ms 96.120.18.125
3 10 ms 9 ms 9 ms te-1-1-sr01.powhatan.va.richmond.comcast.net [68.86.124.17]
4 19 ms 11 ms 9 ms 69.139.165.201
5 10 ms 10 ms 10 ms 96.108.140.165
6 17 ms 18 ms 19 ms 162.151.163.173
7 25 ms 21 ms 22 ms be-21508-cr02.ashburn.va.ibone.comcast.net [68.86.91.53]
8 20 ms 20 ms 20 ms be-10189-pe07.ashburn.va.ibone.comcast.net [68.86.83.66]
9 26 ms 23 ms 24 ms ae-16.a02.asbnva02.us.bb.gin.ntt.net [129.250.66.49]
10 20 ms 20 ms 21 ms ae-69.r06.asbnva02.us.bb.gin.ntt.net [129.250.5.193]
11 * * * Request timed out.
12 212 ms 212 ms 215 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
13 216 ms 216 ms 217 ms 204.2.229.234
14 * 219 ms 218 ms 204.2.229.84

Trace complete.

That end ping is unacceptable and it's completely timing out on a node.