 | Latency Issues(1) | Category: Technical SupportApril-10-2014 5:47 PM PDT (9 years ago)  |
| Tracing route to 12.129.209.68 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms 192.168.0.1 2 7 ms 7 ms 7 ms 142.254.196.61 3 15 ms 15 ms 16 ms cpe-024-031-209-138.sc.res.rr.com [24.31.209.138] 4 26 ms 34 ms 28 ms 24.93.64.16 5 37 ms 40 ms 37 ms 107.14.19.20 6 37 ms 37 ms 31 ms ae0.pr1.dca10.tbone.rr.com [107.14.17.200] 7 45 ms 32 ms 34 ms ix-17-0.tcore2.AEQ-Ashburn.as6453.net [216.6.87.149] 8 53 ms 50 ms 51 ms 192.205.34.245 9 105 ms 103 ms 103 ms cr2.wswdc.ip.att.net [12.122.134.186] 10 108 ms 108 ms 107 ms cr1.cgcil.ip.att.net [12.122.18.21] 11 106 ms 114 ms 116 ms cr2.dvmco.ip.att.net [12.122.31.85] 12 173 ms 137 ms 112 ms cr1.slkut.ip.att.net [12.122.30.25] 13 109 ms 106 ms 108 ms cr2.la2ca.ip.att.net [12.122.30.30] 14 104 ms 105 ms 102 ms gar20.la2ca.ip.att.net [12.122.128.181] 15 107 ms 105 ms 104 ms 12-122-254-234.attens.net [12.122.254.234] 16 104 ms 110 ms 103 ms mdf001c7613r0002.lax1.attens.net [206.16.68.54] 17 113 ms 109 ms 104 ms 12.129.209.68 Trace complete. | ||
 | Latency Issues(2) | April-10-2014 5:57 PM PDT (9 years ago) |
| djw78, Let's try running a pathping of your connection to see what that shows us. For the most accurate results, try running the pathping when the connection issue that you are experiencing is at its worst. Here's a support article that will help with that: Running A Pathping Test Once you have the pathping, go ahead and post it into your next reply. ***The pathping report is two parts. Once you get to where it says, "Computing statistics for X amount of seconds, you will want to wait about 10 minutes before the second part of the report is complete.*** ______________________________________________________ I'm available Monday through Friday from 11AM to 8PM Pacific Time Support Contact Information Got some feedback? | ||
| Latency Issues(7) | April-10-2014 7:26 PM PDT (9 years ago) |
| djw78 7 35ms 47/ 100 = 47% 47/ 100 = 47% ix-17-0.tcore2.AEQ-Ashburn.as6453.net [216.6.87.149] It looks like your connection is experiencing a 47% data loss when it reaches the server located at hop 7, which looks to be part of the TATA Communications network. TATA Communications is a peering partner being used by your ISP, so you will want to contact your ISP to have them look into this. ______________________________________________________ I'm available Monday through Friday from 11AM to 8PM Pacific Time Support Contact Information Got some feedback? | ||
| Latency Issues(8) | April-10-2014 7:31 PM PDT (9 years ago) |
| Luckyone, 3 11ms 1/ 100 = 1% 1/ 100 = 1% 68.85.251.17 0/ 100 = 0% | 4 12ms 1/ 100 = 1% 1/ 100 = 1% 68.85.244.57 0/ 100 = 0% | Your connection is losing 1% data when it reaches hops 3 and 4. Both of those hops are part of the Comcast network. You will want to contact your ISP about this. When contacting them, you will want to request to speak to a tier 3 tech representative since they should be more familiar with reading tracerts. ______________________________________________________ I'm available Monday through Friday from 11AM to 8PM Pacific Time Support Contact Information Got some feedback? | ||
| Latency Issues(9) | April-10-2014 7:33 PM PDT (9 years ago) |
| Orangeaccord, 7 39ms 50/ 100 = 50% 50/ 100 = 50% ix-17-0.tcore2.AEQ-Ashburn.as6453.net [216.6.87.149] Like the OP, your connection is also losing data when it reaches the server at hop 7, which is part of the TATA Communications network. You are going to want to contact your ISP so they can look further into this for you. ______________________________________________________ I'm available Monday through Friday from 11AM to 8PM Pacific Time Support Contact Information Got some feedback? | ||
| Latency Issues(11) | April-10-2014 7:54 PM PDT (9 years ago) |
3 10ms 37/ 100 = 37% 37/ 100 = 37% 69.63.242.121 7 28ms 0/ 100 = 0% 0/ 100 = 0% ae-4-90.edge3.NewYork1.Level3.net[4.69.155.209] 1/ 100 = 1% | It looks like the main issue with your connection starts at hop 3 where the connection is losing 37% data. That hop is part of the Rogers network, so contacting your ISP would be the best thing to do here. Also, the link between hop 7 and 8 is losing 1% data. That could be happening because of the earlier data loss, or it may be a separate issue, but it's also something that the ISP will need to look at. ______________________________________________________ I'm available Monday through Friday from 11AM to 8PM Pacific Time Support Contact Information Got some feedback? | ||
| Latency Issues(780) | April-24-2014 12:35 PM PDT (9 years ago) |
| Hey folks, Our network admins believe that they have found the cause of this latency issue. No more tracerts or pathpings are needed at the moment. For the time being, we ask that you please let us know if you are still experiencing high latency. ______________________________________________________ I'm available Monday through Friday from 11AM to 8PM Pacific Time Support Contact Information Got some feedback? | ||
| Latency Issues(783) | April-24-2014 1:04 PM PDT (9 years ago) |
| Spiderbite, When are they putting this fix in? It should already be in. Are you still seeing high latency? ______________________________________________________ I'm available Monday through Friday from 11AM to 8PM Pacific Time Support Contact Information Got some feedback? | ||
| Latency Issues(786) | April-24-2014 1:21 PM PDT (9 years ago) |
| Aharit, Let's try running a pathping of your connection to see what that shows us. For the most accurate results, try running the pathping when the connection issue that you are experiencing is at its worst. Here's a support article that will help with that: Running A Pathping Test Once you have the pathping, go ahead and post it into your next reply. ***The pathping report is two parts. Once you get to where it says, "Computing statistics for X amount of seconds, you will want to wait about 10 minutes before the second part of the report is complete.*** ______________________________________________________ I'm available Monday through Friday from 11AM to 8PM Pacific Time Support Contact Information Got some feedback? | ||
| Latency Issues(790) | April-24-2014 1:41 PM PDT (9 years ago) |
| Aurelius, I got the update a couple of hours ago, so I'm assuming the fix went in this morning. ______________________________________________________ I'm available Monday through Friday from 11AM to 8PM Pacific Time Support Contact Information Got some feedback? | ||
| Latency Issues(793) | April-24-2014 1:48 PM PDT (9 years ago) |
| Raine, I'm glad to see you aren't experiencing any of those issue anymore. Please let me know if anything changes. ______________________________________________________ I'm available Monday through Friday from 11AM to 8PM Pacific Time Support Contact Information Got some feedback? | ||
| Latency Issues(796) | April-24-2014 1:53 PM PDT (9 years ago) |
| hal8999, Can you post the entire pathping that shows that packet loss? ______________________________________________________ I'm available Monday through Friday from 11AM to 8PM Pacific Time Support Contact Information Got some feedback? | ||
| Latency Issues(800) | April-24-2014 2:15 PM PDT (9 years ago) |
| Ryzzen, The packet loss appears to have been occurring in our backbone, so our backbone provider ended up doing some rerouting on their end. ______________________________________________________ I'm available Monday through Friday from 11AM to 8PM Pacific Time Support Contact Information Got some feedback? | ||
| Latency Issues(812) | April-24-2014 2:55 PM PDT (9 years ago) |
| Draconum, 5 18ms 1/ 100 = 1% 1/ 100 = 1% 0.xe-7-1-0.BR1.IAD8.ALTER.NET [152.63.3.85] There is a 1% data loss occurring on hop 5, which appears to be a Verizon server. I recommend contacting your ISP to have them look what may be causing that. ______________________________________________________ I'm available Monday through Friday from 11AM to 8PM Pacific Time Support Contact Information Got some feedback? | ||
| Latency Issues(840) | April-24-2014 4:40 PM PDT (9 years ago) |
| Draconum, Your last pathping looks clean. I don't think your issue is related to the one in this thread. Please start a new thread and provide me with the link so I can assist you individually. ______________________________________________________ I'm available Monday through Friday from 11AM to 8PM Pacific Time Support Contact Information Got some feedback? | ||
| Latency Issues(842) | April-24-2014 4:46 PM PDT (9 years ago) |
| oranid, 8 97ms 1/ 100 = 1% 1/ 100 = 1% ae-9-9.ebr1.Chicago1.Level3.net [4.69.151.110] 0/ 100 = 0% | 10 87ms 2/ 100 = 2% 2/ 100 = 2% ae-105-3505.edge4.Chicago2.Level3.net [4.69.158.129] 0/ 100 = 0% | 11 125ms 1/ 100 = 1% 1/ 100 = 1% 192.205.37.149 It looks like your connection issue may be to some lost data packets occurring in hops 8 and 10. Those hops are part of the Level 3 network, which is a peering partner being used by your ISP. You will want to contact your ISP to have them look into this and possibly contact Level 3. ______________________________________________________ I'm available Monday through Friday from 11AM to 8PM Pacific Time Support Contact Information Got some feedback? | ||
| Latency Issues(852) | April-24-2014 6:41 PM PDT (9 years ago) |
| oranid, What do I ask them? Let them know that you were experiencing some increased latency when playing games, so you ran a pathping to the game server which shows data loss in the Level 3 network which is their peering partner. They will then most likely have to escalate the issue to Level 3. ______________________________________________________ I'm available Monday through Friday from 11AM to 8PM Pacific Time Support Contact Information Got some feedback? | ||
| Latency Issues(856) | April-24-2014 6:52 PM PDT (9 years ago) |
| KillerElite, 8 103ms 4/ 100 = 4% 4/ 100 = 4% ae-9-9.ebr1.Chicago1.Level3.net [4.69.151.110] 0/ 100 = 0% | 9 105ms 0/ 100 = 0% 0/ 100 = 0% ae-6-6.ebr1.Chicago2.Level3.net [4.69.140.190] 1/ 100 = 1% | 10 162ms 2/ 100 = 2% 1/ 100 = 1% ae-106-3506.edge4.Chicago2.Level3.net [4.69.158.133] 0/ 100 = 0% | It looks like Level 3 is experiencing some data loss before the connection reaches our backbone servers. You are going to want to contact your ISP to have them escalate this issue to their peering partner, Level 3 Networks. ______________________________________________________ I'm available Monday through Friday from 11AM to 8PM Pacific Time Support Contact Information Got some feedback? | ||
| Latency Issues(857) | April-24-2014 7:07 PM PDT (9 years ago) |
| jmack2424, 6 24ms 4/ 100 = 4% 4/ 100 = 4% 173-219-254-238-link.tex.sta.suddenlink.net [173.219.254.238] 0/ 100 = 0% | 7 81ms 0/ 100 = 0% 0/ 100 = 0% 173-219-243-35-link.sta.suddenlink.net [173.219.243.35] 0/ 100 = 0% | 8 81ms 0/ 100 = 0% 0/ 100 = 0% 173-219-243-23-link.sta.suddenlink.net [173.219.243.23] 0/ 100 = 0% | 9 90ms 0/ 100 = 0% 0/ 100 = 0% xe-8-1-2.bar2.Phoenix1.Level3.net[4.53.110.169] 0/ 100 = 0% | 10 129ms 1/ 100 = 1% 1/ 100 = 1% ae-4-4.ebr2.LosAngeles1.Level3.net [4.69.133.38] Your connection is experiencing some data loss in hop 6, which is part of the suddenlink network. Then there is some more data loss showing up in hop 10, and that is part of the Level 3 network. You are going to want to contact your ISP to have them look into this. ______________________________________________________ I'm available Monday through Friday from 11AM to 8PM Pacific Time Support Contact Information Got some feedback? | ||
| Latency Issues(858) | April-24-2014 7:12 PM PDT (9 years ago) |
| Anemous, 11 71ms 2/ 100 = 2% 2/ 100 = 2% 216.156.108.193.ptr.us.xo.net [216.156.108.193] It seems as though your connection is losing 2% data when it goes through the XO Communications server located on hop 11. You will need to contact your ISP so that they can escalate the issue to XO for further investigation. ______________________________________________________ I'm available Monday through Friday from 11AM to 8PM Pacific Time Support Contact Information Got some feedback? | ||
| Latency Issues(859) | April-24-2014 7:14 PM PDT (9 years ago) |
| Lorealin, Let's try running a pathping of your connection to see what that shows us. For the most accurate results, try running the pathping when the connection issue that you are experiencing is at its worst. Here's a support article that will help with that: Running A Pathping Test Once you have the pathping, go ahead and post it into your next reply. ***The pathping report is two parts. Once you get to where it says, "Computing statistics for X amount of seconds, you will want to wait about 10 minutes before the second part of the report is complete.*** ______________________________________________________ I'm available Monday through Friday from 11AM to 8PM Pacific Time Support Contact Information Got some feedback? | ||
| Latency Issues(860) | April-24-2014 7:15 PM PDT (9 years ago) |
| Still, Let's try running a pathping of your connection to see what that shows us. For the most accurate results, try running the pathping when the connection issue that you are experiencing is at its worst. Here's a support article that will help with that: Running A Pathping Test Once you have the pathping, go ahead and post it into your next reply. ***The pathping report is two parts. Once you get to where it says, "Computing statistics for X amount of seconds, you will want to wait about 10 minutes before the second part of the report is complete.*** ______________________________________________________ I'm available Monday through Friday from 11AM to 8PM Pacific Time Support Contact Information Got some feedback? | ||
| Latency Issues(866) | April-24-2014 7:37 PM PDT (9 years ago) |
| darkfury, The tracert looks fine. The only thing that might be of some concern is that your connection is going through XO communications to get to us, and I've already seen a few pathpings where XO seems to be losing some data packets. Unfortunately, that doesn't always show up in tracerts. ______________________________________________________ I'm available Monday through Friday from 11AM to 8PM Pacific Time Support Contact Information Got some feedback? | ||
| Latency Issues(922) | April-25-2014 12:38 PM PDT (9 years ago) |
| Aurelius, Yea, go ahead and post the most recent pathping you ran. ______________________________________________________ I'm available Monday through Friday from 11AM to 8PM Pacific Time Support Contact Information Got some feedback? | ||
| Latency Issues(924) | April-25-2014 12:42 PM PDT (9 years ago) |
| oranid, Ok, now this is weird, my lag is totally fine 6:41am EST at 90ms in game right now but I've noticed that it shoots up to 300+ during peak hours 5pm+ Your ISP might be throttling the connection during peak hours. Try running a pathping when the latency is good and run another when the latency is bad. Post your results so we can compare the two. ______________________________________________________ I'm available Monday through Friday from 11AM to 8PM Pacific Time Support Contact Information Got some feedback? | ||
| Latency Issues(925) | April-25-2014 12:43 PM PDT (9 years ago) |
| Treehealage, Let's try running a pathping of your connection to see what that shows us. For the most accurate results, try running the pathping when the connection issue that you are experiencing is at its worst. Here's a support article that will help with that: Running A Pathping Test Once you have the pathping, go ahead and post it into your next reply. ***The pathping report is two parts. Once you get to where it says, "Computing statistics for X amount of seconds, you will want to wait about 10 minutes before the second part of the report is complete.*** ______________________________________________________ I'm available Monday through Friday from 11AM to 8PM Pacific Time Support Contact Information Got some feedback? | ||
| Latency Issues(954) | April-25-2014 6:12 PM PDT (9 years ago) |
| Aurelius, Computing statistics for 400 seconds... Source to Here This Node/Link Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address 0 (redacted name)-PC.austin.rr.com [192.168.0.3] 0/ 100 = 0% | 1 61ms 0/ 100 = 0% 0/ 100 = 0% 192.168.0.1 0/ 100 = 0% | 2 74ms 1/ 100 = 1% 1/ 100 = 1% cpe-70-123-144-1.austin.res.rr.com [70.123.144.1] 0/ 100 = 0% | 3 72ms 0/ 100 = 0% 0/ 100 = 0% tge2-5.rdrktxaz01h.texas.rr.com [66.68.5.253] 0/ 100 = 0% | 4 60ms 0/ 100 = 0% 0/ 100 = 0% tge0-8-0-8.ausutxla01r.texas.rr.com [24.175.42.156] 1/ 100 = 1% | 5 59ms 2/ 100 = 2% 1/ 100 = 1% agg22.dllatxl301r.texas.rr.com [24.175.41.46] 0/ 100 = 0% | 6 67ms 1/ 100 = 1% 0/ 100 = 0% ae-8-0.cr0.dfw10.tbone.rr.com [66.109.6.52] 0/ 100 = 0% | 7 67ms 1/ 100 = 1% 0/ 100 = 0% ae1.pr1.dfw10.tbone.rr.com [107.14.17.234] 0/ 100 = 0% | 8 76ms 1/ 100 = 1% 0/ 100 = 0% 207.86.210.125 0/ 100 = 0% | 9 66ms 3/ 100 = 3% 2/ 100 = 2% 207.88.15.50.ptr.us.xo.net [207.88.15.50] 0/ 100 = There seems to be a good amount of data loss happening on your ISP's local network and some in the XO Communications network. You are going to want to contact your ISP to have them look into this. ______________________________________________________ I'm available Monday through Friday from 11AM to 8PM Pacific Time Support Contact Information Got some feedback? | ||
| Latency Issues(955) | April-25-2014 6:21 PM PDT (9 years ago) |
| Hey all, I think it's safe to say that the main issue that was causing latency has been resolved. Now, I know that some of you are still experiencing high latency or disconnects, but from the recent pathpings that I've seen, these issues appear to be unrelated to the main latency issue being covered in this thread. I noticed some possible issues with Comcast, XO Communications, Time Warner and Level 3 Networks. I've reported those issues to our network admins and they are forwarding that information to their counterparts at those companies. That will hopefully help expedite a solution on their end, but I still recommend that you contact your ISP so that they can escalate the issue on their end as well. Lastly, I will be locking this thread now, but if you do continue to experience high latency, please start your own thread so we can assist you individually. ______________________________________________________ I'm available Monday through Friday from 11AM to 8PM Pacific Time Support Contact Information Got some feedback? | ||
