| Increased Latency/Lag - 3/10(1) | Category: Technical SupportMarch-10-2014 7:45 PM PDT (9 years ago) ![]() | |
| Hey folks, We are aware that some of you have been experiencing increased latency/lag today. We are not sure at the moment if this is being caused by something on our end, or if it's related to a specific ISP or a specific peering partner that the connection is being routed through. I would like to get gather a little more information from those of you that are experiencing this issue so that we can have this looked into further. Please provide the following information when you get the chance: 1. Who is your Internet Service Provider? 2. What city and state are you playing from? 3. Pathping Here's a support article that will help with the Pathping: Running A Pathping Test ***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.*** Update: 3/12 @ 8:07pm PST XO posted on their Twitter saying that the XO Engineering teams have adjusted network traffic to route through Los Angeles and Dallas, instead of Chicago. They also mentioned that we should start seeing lower latency. Customers have posted new pathpings after this reroute took place and I have not seen any positive reports about the increased latency going away. Also, the pathpings still look like they are taking the same route as before. You guys may need to powercycle your connection to clear out any cached connection data. Here's a support article with steps on how to do that: Resetting Network Devices If that doesn't work try flushing the DNS. If the issue persists, you may need to post on the XO Twitter page to let them know the issue is not resolved. [Post edited one time, last edit by Dankorii at March-12-2014 8:14 PM PDT (9 years ago)] | ||
| Increased Latency/Lag - 3/10(75) | March-11-2014 1:15 PM PDT (9 years ago) ![]() | |
| Hey all, From what I have seen, this issue appears to be affecting mainly Time Warner and Charter customers that are going through ptr.us.xo.net and through AT&T in Chicago. I've escalated the issue so that it can be looked into from our end, but in the meantime, I also recommend that you contact your ISP so that they are aware of the issue, and so that they can possibly open a ticket to investigate the issue from their end as well. If you are not a Time Warner or Charter customer, I recommend starting your own thread so that we can assist you individually. ______________________________________________________ I'm available Monday through Friday from 11AM to 8PM Pacific Time Support Contact Information Got some feedback? | ||
| Increased Latency/Lag - 3/10(942) | March-17-2014 2:45 PM PDT (9 years ago) ![]() | |
| Hey all, It appears that this issue was marked as resolved, but because of some new reports that we've been seeing, the ticket has been reopened. If you are still experiencing latency issues, please go ahead and reply with the information requested in the first post of this thread. ______________________________________________________ I'm available Monday through Friday from 11AM to 8PM Pacific Time Support Contact Information Got some feedback? | ||
| Increased Latency/Lag - 3/10(953) | March-17-2014 6:57 PM PDT (9 years ago) ![]() | |
| Fredcari, Your pathping looks fine, and the connection doesn't appear to be taking the same path that most of the people in this thread were having issues with. I recommend starting your own thread so that we can help you troubleshoot individually. ______________________________________________________ I'm available Monday through Friday from 11AM to 8PM Pacific Time Support Contact Information Got some feedback? | ||
| Increased Latency/Lag - 3/10(955) | March-17-2014 7:02 PM PDT (9 years ago) ![]() | |
| Pondering, Tracing route to 12.129.209.68 over a maximum of 30 hops 1 * 1563 ms 14 ms 98.231.208.1 2 10 ms 11 ms 11 ms xe-0-3-0-32767-sur01.rockville.md.bad.comcast.net [68.85.139.129] 3 11 ms 11 ms 12 ms 68.86.204.185 4 17 ms 20 ms 33 ms he-3-4-0-0-10-cr01.newyork.ny.ibone.comcast.net[68.86.94.173] Your tracert is showing some lost data and a huge latency spike in hop 1. This usually indicates an issue within your home network, like the modem or router. If you haven't already, you should try powercycling the connection. If that doesn't help, you are going to want to contact your ISP for further assistance. Here's a support article with steps on how to do Power cycle and flush the DNS: Resetting Network Devices If that doesn't work try flushing the DNS. Let me know what happens. ______________________________________________________ I'm available Monday through Friday from 11AM to 8PM Pacific Time Support Contact Information Got some feedback? | ||
| Increased Latency/Lag - 3/10(958) | March-17-2014 7:12 PM PDT (9 years ago) ![]() | |
| bobkuna, Computing statistics for 425 seconds... Source to Here This Node/Link Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address 0 Lappy386.home [192.168.1.3] 0/ 100 = 0% | 1 6ms 0/ 100 = 0% 0/ 100 = 0% Wireless_Broadband_Router.home [192.168.1.1] 0/ 100 = 0% | 2 12ms 0/ 100 = 0% 0/ 100 = 0% L100.NWRKNJ-VFTTP-139.verizon-gni.net [74.102.58.1] 27/ 100 = 27% | 3 26ms 27/ 100 = 27% 0/ 100 = 0% G0-6-3-4.NWRKNJ-LCR-22.verizon-gni.net [130.81.146.72] 0/ 100 = 0% | 4 34ms 36/ 100 = 36% 9/ 100 = 9% so-6-1-0-0.NWRK-BB-RTR2.verizon-gni.net [130.81.199.16] 0/ 100 = 0% | 5 29ms 29/ 100 = 29% 2/ 100 = 2% 0.xe-1-1-1.BR2.NYC4.ALTER.NET [152.63.23.169] 0/ 100 = 0% | 6 31ms 27/ 100 = 27% 0/ 100 = 0% 192.205.34.49 9/ 100 = 9% | I'm seeing a 27% data loss in the link between hops 2 and 3. Then hop 3 loses 27%, hop loses 36%, and hop 5 loses 29%. The servers where that loss is occurring are all part of the Verizon network. You will want to contact your ISP to have them look into this issue further. ______________________________________________________ I'm available Monday through Friday from 11AM to 8PM Pacific Time Support Contact Information Got some feedback? | ||
| Increased Latency/Lag - 3/10(959) | March-17-2014 7:16 PM PDT (9 years ago) ![]() | |
| Chewy, Tracing route to 12.129.209.68 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms vlan1.phub.net.cable.rogers.com [192.168.0.1] 2 * * * Request timed out. 3 * 1916 ms 11 ms 209.148.244.1 4 * 2838 ms 10 ms 69.63.249.69 5 * 2919 ms 12 ms 24.156.144.121 6 * * * Request timed out. 7 * 3213 ms 26 ms tengigabitethernet6-2.ar8.nyc1.gblx.net [159.63.51.41] The issue here appears to be located within the Rogers Cable local network. Hops 3, 4, 5, and 7 are all losing data and are all experiencing huge latency jumps. You will want to contact them to have them look into this. ______________________________________________________ I'm available Monday through Friday from 11AM to 8PM Pacific Time Support Contact Information Got some feedback? | ||
| Increased Latency/Lag - 3/10(962) | March-17-2014 8:02 PM PDT (9 years ago) ![]() | |
| Xorpion, Why am I yielding results as far as my router? Your router's firewall might be blocking the pathping. If possible, try connecting directly to your modem so that you are bypassing the router, and then try the pathping again. If you get the same results, your ISP might not allow pathpings. ______________________________________________________ I'm available Monday through Friday from 11AM to 8PM Pacific Time Support Contact Information Got some feedback? | ||
| Increased Latency/Lag - 3/10(1193) | March-25-2014 1:09 PM PDT (9 years ago) ![]() | |
| FelixMak, 0 FelixMak-PC.hgcbroadband.com [223.18.150.158] 14/ 100 = 14% | 1 4ms 16/ 100 = 16% 2/ 100 = 2% 223.18.128.1 0/ 100 = 0% | 2 12ms 15/ 100 = 15% 1/ 100 = 1% 10.30.19.161 0/ 100 = 0% | 3 --- 100/ 100 =100% 86/ 100 = 86% 10.28.21.13 0/ 100 = 0% | 4 4ms 14/ 100 = 14% 0/ 100 = 0% 218.189.98.1 1/ 100 = 1% | 5 1ms 15/ 100 = 15% 0/ 100 = 0% 203.131.243.121 0/ 100 = 0% | 6 4ms 15/ 100 = 15% 0/ 100 = 0% ae-3.r22.tkokhk01.hk.bb.gin.ntt.net [129.250.6.232] 0/ 100 = 0% | 7 59ms 15/ 100 = 15% 0/ 100 = 0% ae-12.r22.osakjp02.jp.bb.gin.ntt.net [129.250.6.234] 0/ 100 = 0% | 8 61ms 15/ 100 = 15% 0/ 100 = 0% ae-8.r20.osakjp02.jp.bb.gin.ntt.net [129.250.6.189] 0/ 100 = 0% | 9 155ms 15/ 100 = 15% 0/ 100 = 0% ae-6.r21.snjsca04.us.bb.gin.ntt.net [129.250.2.130] 0/ 100 = 0% | 10 158ms 15/ 100 = 15% 0/ 100 = 0% ae-2.r07.snjsca04.us.bb.gin.ntt.net [129.250.5.57] 0/ 100 = 0% | 11 165ms 15/ 100 = 15% 0/ 100 = 0% ae-0.att.lsanca03.us.bb.gin.ntt.net [129.250.9.6] From hops 1 through 11, the connection is losing data is just about every hop. That will cause for the connection to be unstable by the time it reaches our servers, which then leads to increased latency and/or disconnects. The data loss is occurring outside of our network so you will want to contact your ISP to have them look into this for you. ______________________________________________________ I'm available Monday through Friday from 11AM to 8PM Pacific Time Support Contact Information Got some feedback? | ||
| Increased Latency/Lag - 3/10(1194) | March-25-2014 1:13 PM PDT (9 years ago) ![]() | |
| Dash, Short Version 0 M-HP [192.168.0.12] 0/ 100 = 0% | 1 4ms 0/ 100 = 0% 0/ 100 = 0% 192.168.0.1 0/ 100 = 0% | 2 33ms 0/ 100 = 0% 0/ 100 = 0% 168.95.221.234 0/ 100 = 0% | 3 35ms 0/ 100 = 0% 0/ 100 = 0% kh-crs12.router.hinet.net [220.128.25.210] 0/ 100 = 0% | 4 40ms 0/ 100 = 0% 0/ 100 = 0% TPDT-3012.hinet.net [220.128.2.114] 0/ 100 = 0% | 5 35ms 1/ 100 = 1% 1/ 100 = 1% hc-j4r1.router.hinet.net [220.128.7.69] 0/ 100 = 0% | 6 40ms 1/ 100 = 1% 1/ 100 = 1% 220-128-12-9.HINET-IP.hinet.net [220.128.12.9] 0/ 100 = 0% | 7 162ms 0/ 100 = 0% 0/ 100 = 0% r12-pa.us.hinet.net [211.72.108.221] 0/ 100 = 0% | Your connection is losing some data when it reaches hops 5 and 6. Those servers are outside of our network, so you will want to contact your ISP to have them look into this issue for you. ______________________________________________________ I'm available Monday through Friday from 11AM to 8PM Pacific Time Support Contact Information Got some feedback? | ||
| Increased Latency/Lag - 3/10(1195) | March-25-2014 1:22 PM PDT (9 years ago) ![]() | |
| edu, 0 EduPC [192.168.1.105] 0/ 100 = 0% | 1 2ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1 0/ 100 = 0% | 2 --- 100/ 100 =100% 100/ 100 =100% nrp23.macau.ctm.net [202.175.100.23] 0/ 100 = 0% | 3 --- 100/ 100 =100% 100/ 100 =100% z95l123.static.ctm.net [202.175.95.123] 0/ 100 = 0% | 4 --- 100/ 100 =100% 100/ 100 =100% tr1-192.macau.ctm.net [202.175.26.206] 0/ 100 = 0% | 5 --- 100/ 100 =100% 100/ 100 =100% z0l206.static.ctm.net [202.175.0.206] 0/ 100 = 0% | 6 69ms 0/ 100 = 0% 0/ 100 = 0% 203.131.246.229 0/ 100 = 0% | 7 54ms 41/ 100 = 41% 41/ 100 = 41% ae-5.r20.tkokhk01.hk.bb.gin.ntt.net [129.250.2.92] 0/ 100 = 0% | 8 74ms 1/ 100 = 1% 1/ 100 = 1% ae-0.r22.tkokhk01.hk.bb.gin.ntt.net [129.250.2.44] 0/ 100 = 0% | 9 140ms 1/ 100 = 1% 1/ 100 = 1% ae-12.r22.osakjp02.jp.bb.gin.ntt.net [129.250.6.234] 0/ 100 = 0% | 10 125ms 0/ 100 = 0% 0/ 100 = 0% ae-8.r20.osakjp02.jp.bb.gin.ntt.net [129.250.6.189] 0/ 100 = 0% | 11 257ms 0/ 100 = 0% 0/ 100 = 0% ae-8.r20.snjsca04.us.bb.gin.ntt.net [129.250.2.164] 1/ 100 = 1% | 12 247ms 2/ 100 = 2% 1/ 100 = 1% ae-1.r07.snjsca04.us.bb.gin.ntt.net [129.250.5.53] 0/ 100 = 0% | 13 226ms 1/ 100 = 1% 0/ 100 = 0% 192.205.37.57 27/ 100 = 27% | Your connection is losing 41% data when it reaches the server located at hop 7. Then it loses some more data in hops 8 and 9, and the link between hops 11 and 12 is also losing some data. These issues are all happening outside of our network. Please contact your ISP to have them look into this further. ______________________________________________________ I'm available Monday through Friday from 11AM to 8PM Pacific Time Support Contact Information Got some feedback? | ||
| Increased Latency/Lag - 3/10(1196) | March-25-2014 1:28 PM PDT (9 years ago) ![]() | |
| Hey all, The original issue that was being investigated in this thread is resolved. In order to avoid confusion with different connection issues all in one thread, this thread is now locked. If you are experiencing any increased latency, please feel free to start a new thread so that we can assist you. ______________________________________________________ I'm available Monday through Friday from 11AM to 8PM Pacific Time Support Contact Information Got some feedback? | ||
