 | latency spikes hardcore(1) | Category: Technical SupportFebruary-1-2016 2:15 PM PST (9 years ago)  |
| Tracing route to 12.129.222.10 over a maximum of 30 hops 0 xxxxxxxx [192.168.1.145] 1 xxxxxxxx [192.168.1.1] 2 10.70.192.1 3 105-12-226-24.rev.cgocable.net [24.226.12.105] 4 6-6-226-24.rev.cgocable.net [24.226.6.6] 5 4.59.214.129 6 ae-105-3505.bar2.Tustin1.Level3.net [4.69.158.98] 7 ae-105-3505.bar2.Tustin1.Level3.net [4.69.158.98] 8 192.205.37.145 9 cr1.la2ca.ip.att.net [12.122.128.102] 10 12.122.90.29 11 * * * Computing statistics for 250 seconds... Source to Here This Node/Link Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address 0 xxxxxxx [192.168.1.145] 0/ 100 = 0% | 1 0ms 0/ 100 = 0% 0/ 100 = 0% xxxxxxxxx [192.168.1.1] 0/ 100 = 0% | 2 --- 100/ 100 =100% 100/ 100 =100% 10.70.192.1 0/ 100 = 0% | 3 27ms 0/ 100 = 0% 0/ 100 = 0% 105-12-226-24.rev.cgocable.net [24.226.12.105] 0/ 100 = 0% | 4 20ms 0/ 100 = 0% 0/ 100 = 0% 6-6-226-24.rev.cgocable.net [24.226.6.6] 0/ 100 = 0% | 5 23ms 0/ 100 = 0% 0/ 100 = 0% 4.59.214.129 100/ 100 =100% | 6 --- 100/ 100 =100% 0/ 100 = 0% ae-105-3505.bar2.Tustin1.Level3.net [4.69.158.98] 0/ 100 = 0% | 7 --- 100/ 100 =100% 0/ 100 = 0% ae-105-3505.bar2.Tustin1.Level3.net [4.69.158.98] 0/ 100 = 0% | 8 --- 100/ 100 =100% 0/ 100 = 0% 192.205.37.145 0/ 100 = 0% | 9 --- 100/ 100 =100% 0/ 100 = 0% cr1.la2ca.ip.att.net [12.122.128.102] 0/ 100 = 0% | 10 --- 100/ 100 =100% 0/ 100 = 0% 12.122.90.29 Trace complete. traceroute to 72.38.206.199 (72.38.206.199), 15 hops max, 60 byte packets 1 Blizzard (Blizzard) 0.496 ms 0.721 ms 0.831 ms 2 * * * 3 12.129.248.117 (12.129.248.117) 0.394 ms * * 4 206.16.68.41 (206.16.68.41) 0.433 ms 0.457 ms 0.600 ms 5 12-122-254-229.attens.net (12.122.254.229) 16.908 ms 16.933 ms 16.940 ms 6 cr1.la2ca.ip.att.net (12.122.85.34) 3.474 ms 3.056 ms 3.043 ms 7 ggr2.la2ca.ip.att.net (12.122.128.97) 4.753 ms 4.751 ms 4.748 ms 8 las-bb1-link.telia.net (80.239.193.213) 1.828 ms 1.860 ms 1.983 ms 9 nyk-bb2-link.telia.net (213.155.135.118) 93.817 ms 93.747 ms 93.797 ms 10 toro-b1-link.telia.net (213.155.137.71) 81.713 ms 81.755 ms 81.768 ms 11 cogeco-ic-309384-toro-b1.c.telia.net (80.239.194.194) 84.402 ms 84.425 ms 85.458 ms 12 110-12-226-24.rev.cgocable.net (24.226.12.110) 84.100 ms 84.115 ms 84.038 ms 13 d72-38-206-199.commercial1.cgocable.net (72.38.206.199) 93.412 ms 96.745 ms 94.114 ms PING 72.38.206.199 (72.38.206.199) 56(84) bytes of data. 64 bytes from 72.38.206.199: icmp_seq=1 ttl=115 time=91.5 ms 64 bytes from 72.38.206.199: icmp_seq=2 ttl=115 time=90.5 ms 64 bytes from 72.38.206.199: icmp_seq=3 ttl=115 time=97.5 ms 64 bytes from 72.38.206.199: icmp_seq=4 ttl=115 time=92.1 ms HOST: Blizzard Loss% Snt Last Avg Best Wrst StDev 1. Blizzard 0.0% 10 0.4 0.7 0.4 1.2 0.3 2. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0 3. 12.129.248.117 0.0% 10 0.4 0.4 0.4 0.6 0.1 4. 206.16.68.41 0.0% 10 0.3 40.4 0.3 147.5 53.5 5. 12-122-254-229.attens.net 0.0% 10 1.2 6.6 1.1 52.7 16.2 spikes worse then ever 3k plus pings) as of about 2 hours ago and havent stopped most def impossible to play in this | ||
 | latency spikes hardcore(2) | February-1-2016 2:30 PM PST (9 years ago) |
| We're currently investigating reports of latency in Diablo III for some ISPs. Please see this thread for details and updates. Thanks! | ||
