Tracing route to 24.105.62.129 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.0.1
2 2 ms 2 ms 2 ms stpl-dsl-gw21.stpl.qwest [207.109.2.21]
3 3 ms 8 ms 5 ms stpl-agw1.inet.qwest [207.109.3.161]
4 3 ms 2 ms 2 ms 216-160-19-2.mpls.qwest [216.160.19.2]
5 2366 ms * * ae-2-3602.ear3.Washington1.Level3 [4.69.206.81]
6 29 ms 29 ms 29 ms BLIZZARD-EN.ear3.Washington1.Level3 [4.16.70.182]
7 30 ms 29 ms 29 ms ae1-br01-eqdc2.as57976 [137.221.72.33]
8 30 ms 30 ms 35 ms et-0-0-2-br01-eqch2.as57976 [137.221.65.13]
9 34 ms 30 ms 29 ms be1-pe01-eqch2.as57976 [137.221.69.67]
10 34 ms 31 ms 33 ms chi-eqch2-ia-bons-02.as57976 [137.221.66.11]
11 30 ms 30 ms 31 ms 24.105.62.129
Trace complete.
My ISP says there is nothing they can do, and this only started happening after service was restored on Monday. My ISP is Centurylink and they claim they have no control over that node but the own it…
Also had to remove every dot net to post, all addresses had a dot net.