 | Latency / Lag issues (Midwest)(1) | Category: Technical SupportMarch-10-2014 4:34 PM PDT (9 years ago)  |
| I was running the game fine up until last night, but today the issues with latency started here in the Midwest as well. 87% packet loss. Ouch! ISP: Time Warner Cable Location: Racine, WI (between Milwaukee/Chicago) Tracert 1 <1 ms <1 ms <1 ms local [192.168.1.1] 2 11 ms 10 ms 9 ms 142.254.152.213 3 20 ms 9 ms 7 ms tge3-3.racnwiracn-swt401.wi.rr.com [24.160.224.54] 4 12 ms 10 ms 20 ms tge1-8-0-6.gnfdwibb-ccr01.midwest.rr.com [65.29.46.138] 5 14 ms 15 ms 11 ms ae-6-0.cr0.chi10.tbone.rr.com [66.109.6.204] 6 * 10 ms 11 ms ae0.pr1.chi10.tbone.rr.com [107.14.17.192] 7 11 ms 11 ms 10 ms 216.1.94.65 8 45 ms 30 ms 32 ms 207.88.15.90.ptr.us.xo.net [207.88.15.90] 9 65 ms 68 ms 68 ms 206.111.2.90.ptr.us.xo.net [206.111.2.90] 10 109 ms 113 ms * cr1.cgcil.ip.att.net [12.122.133.34] 11 118 ms * 113 ms cr2.dvmco.ip.att.net [12.122.31.85] 12 118 ms 116 ms 114 ms cr1.slkut.ip.att.net [12.122.30.25] 13 114 ms 115 ms * cr2.la2ca.ip.att.net [12.122.30.30] 14 109 ms * 111 ms gar20.la2ca.ip.att.net [12.122.128.181] 15 116 ms 110 ms 120 ms 12.122.251.190 16 110 ms 111 ms 115 ms mdf001c7613r0002.lax1.attens.net [206.16.68.54] 17 * 107 ms 113 ms 12.129.209.68 pathping Tracing route to 12.129.209.68 over a maximum of 30 hops 0 A21273 [192.168.1.101] 1 ROUTER [192.168.1.1] 2 142.254.152.213 3 tge3-3.racnwiracn-swt401.wi.rr.com [24.160.224.54] 4 tge1-8-0-6.gnfdwibb-ccr01.midwest.rr.com [65.29.46.138] 5 ae-6-0.cr0.chi10.tbone.rr.com [66.109.6.204] 6 ae0.pr1.chi10.tbone.rr.com [107.14.17.192] 7 216.1.94.65 8 207.88.15.90.ptr.us.xo.net [207.88.15.90] 9 206.111.2.90.ptr.us.xo.net [206.111.2.90] 10 cr1.cgcil.ip.att.net [12.122.133.34] 11 cr2.dvmco.ip.att.net [12.122.31.85] 12 cr1.slkut.ip.att.net [12.122.30.25] 13 cr2.la2ca.ip.att.net [12.122.30.30] 14 gar20.la2ca.ip.att.net [12.122.128.181] 15 12.122.251.190 16 mdf001c7613r0002.lax1.attens.net [206.16.68.54] 17 * 12.129.209.68 Computing statistics for 425 seconds... Source to Here This Node/Link Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address 0 A21273 [192.168.1.101] 0/ 100 = 0% | 1 0ms 0/ 100 = 0% 0/ 100 = 0% ROUTER [192.168.1.1] 0/ 100 = 0% | 2 8ms 0/ 100 = 0% 0/ 100 = 0% 142.254.152.213 0/ 100 = 0% | 3 9ms 0/ 100 = 0% 0/ 100 = 0% tge3-3.racnwiracn-swt401.wi.rr.com [24.160.224.54] 0/ 100 = 0% | 4 11ms 0/ 100 = 0% 0/ 100 = 0% tge1-8-0-6.gnfdwibb-ccr01.midwest.rr.com [65.29.46.138] 0/ 100 = 0% | 5 14ms 0/ 100 = 0% 0/ 100 = 0% ae-6-0.cr0.chi10.tbone.rr.com [66.109.6.204] 0/ 100 = 0% | 6 14ms 0/ 100 = 0% 0/ 100 = 0% ae0.pr1.chi10.tbone.rr.com [107.14.17.192] 0/ 100 = 0% | 7 15ms 0/ 100 = 0% 0/ 100 = 0% 216.1.94.65 1/ 100 = 1% | 8 33ms 1/ 100 = 1% 0/ 100 = 0% 207.88.15.90.ptr.us.xo.net [207.88.15.90] 12/ 100 = 12% | 9 68ms 13/ 100 = 13% 0/ 100 = 0% 206.111.2.90.ptr.us.xo.net [206.111.2.90] 0/ 100 = 0% | 10 --- 100/ 100 =100% 87/ 100 = 87% cr1.cgcil.ip.att.net [12.122.133.34] 0/ 100 = 0% | 11 --- 100/ 100 =100% 87/ 100 = 87% cr2.dvmco.ip.att.net [12.122.31.85] 0/ 100 = 0% | 12 --- 100/ 100 =100% 87/ 100 = 87% cr1.slkut.ip.att.net [12.122.30.25] 0/ 100 = 0% | 13 --- 100/ 100 =100% 87/ 100 = 87% cr2.la2ca.ip.att.net [12.122.30.30] 0/ 100 = 0% | 14 --- 100/ 100 =100% 87/ 100 = 87% gar20.la2ca.ip.att.net [12.122.128.181] 0/ 100 = 0% | 15 --- 100/ 100 =100% 87/ 100 = 87% 12.122.251.190 0/ 100 = 0% | 16 --- 100/ 100 =100% 87/ 100 = 87% mdf001c7613r0002.lax1.attens.net [206.16.68.54] 0/ 100 = 0% | 17 113ms 13/ 100 = 13% 0/ 100 = 0% 12.129.209.68 Trace complete. | ||
 | Latency / Lag issues (Midwest)(16) | March-10-2014 8:06 PM PDT (9 years ago) |
| Hey all, We've started the following sticky thread in order to gather more information about this issue: Increased Latency/Lag - 3/10 In order to keep all information related to this issue in one thread, I'll be locking this thread now. ______________________________________________________ I'm available Monday through Friday from 11AM to 8PM Pacific Time Support Contact Information Got some feedback? | ||
