 | Really BAD Spikey Latency(1) | Category: Technical SupportFebruary-1-2016 2:16 PM PST (9 years ago)  |
| PING 68.48.86.92 (68.48.86.92) 56(84) bytes of data. 64 bytes from 68.48.86.92: icmp_seq=1 ttl=50 time=70.4 ms 64 bytes from 68.48.86.92: icmp_seq=2 ttl=50 time=71.0 ms 64 bytes from 68.48.86.92: icmp_seq=3 ttl=50 time=72.5 ms 64 bytes from 68.48.86.92: icmp_seq=4 ttl=50 time=71.1 ms --- 68.48.86.92 ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 3070ms rtt min/avg/max/mdev = 70.479/71.330/72.561/0.760 ms traceroute to 68.48.86.92 (68.48.86.92), 15 hops max, 60 byte packets 1 Blizzard (Blizzard) 0.486 ms 0.702 ms 0.809 ms 2 * * * 3 12.129.199.181 (12.129.199.181) 0.450 ms * * 4 206.16.68.53 (206.16.68.53) 0.447 ms 0.469 ms 0.519 ms 5 cr1.la2ca.ip.att.net (12.122.128.182) 4.621 ms 4.641 ms 4.648 ms 6 cr1.la2ca.ip.att.net (12.122.128.182) 4.653 ms 3.238 ms 3.230 ms 7 ggr2.la2ca.ip.att.net (12.122.128.97) 2.614 ms 2.631 ms 2.631 ms 8 192.205.37.26 (192.205.37.26) 1.949 ms 1.964 ms 1.803 ms 9 hu-0-5-0-0-cr02.losangeles.ca.ibone.comcast.net (68.86.83.17) 3.375 ms hu-1-0-0-0-cr02.losangeles.ca.ibone.comcast.net (68.86.88.9) 2.671 ms hu-0-5-0-1-cr02.losangeles.ca.ibone.comcast.net (68.86.83.21) 2.755 ms 10 * * * 11 * * * 12 be-11719-cr02.denver.co.ibone.comcast.net (68.86.86.77) 42.712 ms 42.130 ms 42.664 ms 13 be-10517-cr02.350ecermak.il.ibone.comcast.net (68.86.85.169) 55.881 ms 55.901 ms 55.679 ms 14 be-7922-ar02.pontiac.mi.michigan.comcast.net (68.86.90.46) 60.113 ms 59.997 ms 60.019 ms 15 xe-9-1-0-0-sur02.flint.mi.michigan.comcast.net (162.151.103.198) 60.494 ms 60.490 ms 60.526 ms HOST: Blizzard Loss% Snt Last Avg Best Wrst StDev 1. Blizzard 0.0% 10 0.5 0.5 0.3 0.7 0.2 2. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0 3. 12.129.199.181 0.0% 10 0.4 25.0 0.4 152.0 49.2 4. 206.16.68.53 0.0% 10 0.4 19.1 0.4 59.8 22.7 5. cr1.la2ca.ip.att.net 0.0% 10 5.2 3.1 1.3 5.7 1.5 6. cr1.la2ca.ip.att.net 0.0% 10 2.1 3.5 2.1 5.2 1.2 | ||
 | Really BAD Spikey Latency(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! | ||
