 | Trying to sort out lag. Pathping/Traceroute(1) | Category: Technical SupportApril-2-2014 4:03 PM PDT (9 years ago)  |
| You tech guys understand this way better than I do. This is the usual case of super lag coming from a comcast user. Game is literally unplayable. Tracing route to 12.129.209.68 over a maximum of 30 hops 0 Ivalice-PC [192.168.1.6] 1 192.168.1.1 2 96.120.14.101 3 te-8-2-ur02.yubacity.ca.ccal.comcast.net [68.85.104.29] 4 68.87.221.1 5 he-1-1-0-0-11-cr01.losangeles.ca.ibone.comcast.net [68.86.95.37] 6 pos-0-3-0-0-pe01.600wseventh.ca.ibone.comcast.net [68.86.87.210] 7 192.205.37.25 8 cr2.la2ca.ip.att.net [12.122.129.98] 9 gar29.la2ca.ip.att.net [12.122.129.241] 10 12-122-254-234.attens.net [12.122.254.234] 11 mdf001c7613r0003-gig-12-1.lax1.attens.net [12.129.193.254] 12 12.129.209.68 Computing statistics for 300 seconds... Source to Here This Node/Link Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address 0 Ivalice-PC [192.168.1.6] 0/ 100 = 0% | 1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1 0/ 100 = 0% | 2 8ms 0/ 100 = 0% 0/ 100 = 0% 96.120.14.101 0/ 100 = 0% | 3 9ms 0/ 100 = 0% 0/ 100 = 0% te-8-2-ur02.yubacity.ca.ccal.comcast.net [68.85.104.29] 0/ 100 = 0% | 4 20ms 0/ 100 = 0% 0/ 100 = 0% 68.87.221.1 0/ 100 = 0% | 5 25ms 0/ 100 = 0% 0/ 100 = 0% he-1-1-0-0-11-cr01.losangeles.ca.ibone.comcast.net [68.86.95.37] 4/ 100 = 4% | 6 1139ms 10/ 100 = 10% 6/ 100 = 6% pos-0-3-0-0-pe01.600wseventh.ca.ibone.comcast.net [68.86.87.210] 0/ 100 = 0% | 7 1143ms 15/ 100 = 15% 11/ 100 = 11% 192.205.37.25 0/ 100 = 0% | 8 --- 100/ 100 =100% 96/ 100 = 96% cr2.la2ca.ip.att.net [12.122.129.98] 0/ 100 = 0% | 9 --- 100/ 100 =100% 96/ 100 = 96% gar29.la2ca.ip.att.net [12.122.129.241] 0/ 100 = 0% | 10 --- 100/ 100 =100% 96/ 100 = 96% 12-122-254-234.attens.net [12.122.254.234] 0/ 100 = 0% | 11 --- 100/ 100 =100% 96/ 100 = 96% mdf001c7613r0003-gig-12-1.lax1.attens.net [12.129.193.254] 0/ 100 = 0% | 12 753ms 4/ 100 = 4% 0/ 100 = 0% 12.129.209.68 Trace complete. Tracing route to 12.129.209.68 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms 192.168.1.1 2 7 ms 7 ms 7 ms 96.120.14.101 3 8 ms 7 ms 7 ms te-8-2-ur02.yubacity.ca.ccal.comcast.net [68.85.104.29] 4 14 ms 15 ms 15 ms 68.87.221.1 5 23 ms 25 ms 23 ms 68.86.89.57 6 1117 ms 1179 ms 1161 ms pos-0-3-0-0-pe01.600wseventh.ca.ibone.comcast.net [68.86.87.210] 7 1138 ms 1111 ms 1155 ms 192.205.37.25 8 933 ms 932 ms 938 ms cr2.la2ca.ip.att.net [12.122.129.98] 9 * 1405 ms * gar29.la2ca.ip.att.net [12.122.129.241] 10 1157 ms 1132 ms 1187 ms 12-122-254-234.attens.net [12.122.254.234] 11 923 ms 924 ms 915 ms mdf001c7613r0003-gig-12-1.lax1.attens.net [12.129.193.254] 12 887 ms 833 ms 859 ms 12.129.209.68 Trace complete. | ||
 | Trying to sort out lag. Pathping/Traceroute(2) | April-2-2014 7:11 PM PDT (9 years ago) |
| KyNoel, Thanks for providing your tracert and pathping. I looked them over and it looks like the issue may be on Comcast's end. I actually saw some other reports on a 3rd party site showing that Comcast users in CA are experiencing some connection issues. Comcast outage map Computing statistics for 300 seconds... Source to Here This Node/Link Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address 0 Ivalice-PC [192.168.1.6] 0/ 100 = 0% | 1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1 0/ 100 = 0% | 2 8ms 0/ 100 = 0% 0/ 100 = 0% 96.120.14.101 0/ 100 = 0% | 3 9ms 0/ 100 = 0% 0/ 100 = 0% te-8-2-ur02.yubacity.ca.ccal.comcast.net [68.85.104.29] 0/ 100 = 0% | 4 20ms 0/ 100 = 0% 0/ 100 = 0% 68.87.221.1 0/ 100 = 0% | 5 25ms 0/ 100 = 0% 0/ 100 = 0% he-1-1-0-0-11-cr01.losangeles.ca.ibone.comcast.net [68.86.95.37] 4/ 100 = 4% | 6 1139ms 10/ 100 = 10% 6/ 100 = 6% pos-0-3-0-0-pe01.600wseventh.ca.ibone.comcast.net [68.86.87.210] 0/ 100 = 0% | 7 1143ms 15/ 100 = 15% 11/ 100 = 11% 192.205.37.25 The pathping shows that the link between hops 5 and 6 is losing 4% data. Both of those hops are part of Comcast's network. Then, hop 6 shows a huge latency jump and it's also losing 10% data. Tracing route to 12.129.209.68 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms 192.168.1.1 2 7 ms 7 ms 7 ms 96.120.14.101 3 8 ms 7 ms 7 ms te-8-2-ur02.yubacity.ca.ccal.comcast.net [68.85.104.29] 4 14 ms 15 ms 15 ms 68.87.221.1 5 23 ms 25 ms 23 ms 68.86.89.57 6 1117 ms 1179 ms 1161 ms pos-0-3-0-0-pe01.600wseventh.ca.ibone.comcast.net [68.86.87.210] 7 1138 ms 1111 ms 1155 ms 192.205.37.25 8 933 ms 932 ms 938 ms cr2.la2ca.ip.att.net [12.122.129.98] 9 * 1405 ms * gar29.la2ca.ip.att.net [12.122.129.241] 10 1157 ms 1132 ms 1187 ms 12-122-254-234.attens.net [12.122.254.234] 11 923 ms 924 ms 915 ms mdf001c7613r0003-gig-12-1.lax1.attens.net [12.129.193.254] 12 887 ms 833 ms 859 ms 12.129.209.68 Trace complete. The tracert pretty much shows the same thing as the pathping. You can see the latency spiking in hop 6, which is most likely causing the the latency spikes that are showing up after that. For now, my best guess is that there may be some kind of congestion issue occurring when the connection reaches hop 6. I recommend contacting Comcast so that they can look into this further. ______________________________________________________ I'm available Monday through Friday from 11AM to 8PM Pacific Time Support Contact Information Got some feedback? | ||
| Trying to sort out lag. Pathping/Traceroute(4) | April-2-2014 7:24 PM PDT (9 years ago) |
| eighteesix, I'll check that thread and post a response in there. ______________________________________________________ I'm available Monday through Friday from 11AM to 8PM Pacific Time Support Contact Information Got some feedback? | ||
| Trying to sort out lag. Pathping/Traceroute(6) | April-3-2014 1:55 PM PDT (9 years ago) |
| KyNoel, You're welcome, and thank you for providing the update from Comcast. ______________________________________________________ I'm available Monday through Friday from 11AM to 8PM Pacific Time Support Contact Information Got some feedback? | ||
