 | pathping 1 15 2016(1) | Category: Technical SupportJanuary-15-2016 8:01 PM PST (8 years ago)  |
| as requested by @BlizzardCS twitter when I asked for help: Tracing route to 12.129.222.10 over a maximum of 30 hops 0 AsusJHR.Belkin [192.168.2.4] 1 . [192.168.2.1] 2 96.120.70.81 3 GE-9-1-rr02.bristol.ct.hartford.comcast.net [68.87.180.173] 4 be-23-sur03.needham.ma.boston.comcast.net [69.139.221.230] 5 be-39-ar01.needham.ma.boston.comcast.net [69.139.221.1] 6 be-7015-cr02.newyork.ny.ibone.comcast.net [68.86.90.217] 7 c-eth-0-3-0-pe04.111eighthave.ny.ibone.comcast.net [68.86.87.110] 8 192.205.37.33 9 cr2.n54ny.ip.att.net [12.122.130.110] 10 12.122.94.237 11 * * * Computing statistics for 250 seconds... Source to Here This Node/Link Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address 0 AsusJHR.Belkin [192.168.2.4] 0/ 100 = 0% | 1 1ms 0/ 100 = 0% 0/ 100 = 0% . [192.168.2.1] 19/ 100 = 19% | 2 12ms 20/ 100 = 20% 1/ 100 = 1% 96.120.70.81 0/ 100 = 0% | 3 12ms 20/ 100 = 20% 1/ 100 = 1% GE-9-1-rr02.bristol.ct.hartford.comcast.net [68.87.180.173] 0/ 100 = 0% | 4 13ms 19/ 100 = 19% 0/ 100 = 0% be-23-sur03.needham.ma.boston.comcast.net [69.139.221.230] 0/ 100 = 0% | 5 26ms 20/ 100 = 20% 1/ 100 = 1% be-39-ar01.needham.ma.boston.comcast.net [69.139.221.1] 0/ 100 = 0% | 6 28ms 19/ 100 = 19% 0/ 100 = 0% be-7015-cr02.newyork.ny.ibone.comcast.net [68.86.90.217] 3/ 100 = 3% | 7 34ms 22/ 100 = 22% 0/ 100 = 0% c-eth-0-3-0-pe04.111eighthave.ny.ibone.comcast.net [68.86.87.110] 0/ 100 = 0% | 8 33ms 22/ 100 = 22% 0/ 100 = 0% 192.205.37.33 78/ 100 = 78% | 9 --- 100/ 100 =100% 0/ 100 = 0% cr2.n54ny.ip.att.net [12.122.130.110] 0/ 100 = 0% | 10 --- 100/ 100 =100% 0/ 100 = 0% 12.122.94.237 Trace complete. | ||
 | pathping 1 15 2016(2) | January-15-2016 8:06 PM PST (8 years ago) |
0 AsusJHR.Belkin [192.168.2.4] 0/ 100 = 0% | 1 1ms 0/ 100 = 0% 0/ 100 = 0% . [192.168.2.1] 19/ 100 = 19% | Dasbif, it looks like you are experiencing some pretty severe packet loss immediately after your computer connects to your router/modem. Let's try restarting your network devices in order, and then performing a DNS Flush to see if this addresses the issue. Give that a shot and let us know how it goes! | ||
