
Originally Posted by
Einmimiria
Hello everyone,
As we proceed with our investigation, we ask that everyone run a traceroute to this IP address: 204.2.229.9. We would like to get results around the times the latency is being reported (7:30 PM PST / 8:30 PM MST / 10:30 PM EST).
To run a traceroute, press the windows key and “R” which will bring up the run command. Type “cmd” here and press “Enter” or the “OK” button. When the command prompt opens, type “tracert 204.2.229.9” and hit “Enter”. Copy and paste the results (or take a screen shot) here in this thread.
Thank you in advance for you cooperation and understanding in this matter. We hope we can use this information in our investigation to find a solution. Moving forward, we will continue to post updates as they are available.
Enjoy:
Code:
Tracing route to 204.2.229.9 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms RT-AC68U-5570 [192.168.1.1]
2 9 ms 8 ms 9 ms 96.120.28.53
3 18 ms 8 ms 9 ms te-0-7-0-8-sur03.chicago301.il.chicago.comcast.net [68.85.180.45]
4 8 ms 10 ms 8 ms 68.85.183.142
5 12 ms 10 ms 10 ms be-144-ar01.area4.il.chicago.comcast.net [162.151.45.69]
6 10 ms 11 ms 12 ms be-33491-cr02.350ecermak.il.ibone.comcast.net [68.86.91.165]
7 11 ms 10 ms 16 ms be-10577-pe03.350ecermak.il.ibone.comcast.net [68.86.86.2]
8 16 ms 12 ms 10 ms ae-26.a02.chcgil09.us.bb.gin.ntt.net [129.250.66.65]
9 193 ms 185 ms 185 ms ae-4.r08.chcgil09.us.bb.gin.ntt.net [129.250.4.157]
10 27 ms 10 ms 20 ms ae-0.r21.chcgil09.us.bb.gin.ntt.net [129.250.2.205]
11 189 ms 182 ms 186 ms ae-5.r22.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
12 181 ms 186 ms * ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121]
13 174 ms 181 ms 182 ms ae-2.a00.snjsca04.us.bb.gin.ntt.net [129.250.3.58]
14 187 ms 189 ms 187 ms xe-0-0-42-1.a00.snjsca04.us.ce.gin.ntt.net [129.250.195.42]
15 182 ms 188 ms 177 ms 204.2.229.242
16 192 ms 188 ms 189 ms 204.2.229.9