09/05/08 | Latency Submission Thread
by Igrumu | 09/05/2008 11:23:51 Welcome to our new Latency Report Submission Thread. These allow us to track and report ongoing latency issues for further investigation. All the information provided in the last post has been forwarded to the our network team for any ongoing investigations You can still find the old sticky post here, though it has now been locked and un-stickied: 02/05/2008 - Latency Report Submission Thread  Please post the information below in this thread if you experience latency problems this week. NOTE: Only post the information that is requested in this thread, we will remove any posts that do not supply ALL the requested information, as well as any posts containing commentary etc.. The first step of any investigation is to make sure there that your internet security is correctly configured to work with World of Warcraft. The following article may offer some possible fixes: http://eu.blizzard.com/support/article.xml?articleId=19459 You can find more information regarding connectivity problems, and a better definition of latency and what to look for in a trace route, in our FAQ: http://eu.blizzard.com/support/article.xml?articleId=19677 Also make sure you are using NO add-ons, as these are not supported by Blizzard and some of them are known to cause latency problems. Locate your World of Warcraft installation folder and delete the WTF, Cache and Interface folders. If the high latency is still occurring, running a trace route can identify the source of the issue. The trace route program tests the connection from your computer to the target location you specify and every "hop" in between. Using this program you can determine at what location the data you are sending is running into a problem. We will need the information generated from the following commands: When you are playing the game, press Alt Tab, You may want to switch to windowed mode to make it easier to get back to the desktop. - Click the Start button and select the Run option from the menu - Type in cmd in the command text box then press Enter. - Type the following into the command window that appears: netstat -n -p tcp -b | more you will see a line like this one (depending on World Of Warcraft): TCP XXX.XX.XX.XX:XXXX YY.YYY.YYY.YY:3724 ESTABLISHED 4476 [WoW.exe] The IP address that is indicated by Xs is your IP address, this is not needed, so do not post this. The information that is important however is the one indicated by Y's on the example above, this is the IP address of the server you are playing on. Now we need some information on your connection, in the same command window, type in: tracert YY.YYY.YYY.YY > C:\tracert.txt A file will be created on your local drive (C:\) called tracert.txt which will contain the trace route information, this may take some time so do not close down the window once the trace is complete the > prompt will appear again. Please copy and paste the contents of the tracert file into this post along with the following information: - The Date and Time that you created the tracert file: - Your town and Country: - The hour and date when you experience the problems the most: - When did this problem start: - Realm played: - Internet Service Provider: - How fast is your internet connection? : - The in game latency bar reading - Modem model: - Network card model if one is used: - Router model (if used): - Firewall Software (if used): - Do you share your connection? - Connection used, (USB, Ethernet or Wifi): - Could you please try to create characters on Karazhan, Kor'gall and Spinebreaker to test if the latency persists on these realms? - Your characters location on the realm (which zone you are in) - Name of the instance (in the case that you are in an instance) - What exactly happens? (Make sure to describe this as well as you can): You are more than welcome to post more than one traceroute, just indicate the different times you are performing the traceroute as it could better identify any problems. Please note that in some cases we may be limited in the support we are able to offer. You may need to speak to your provider directly if the routing to your realm is inadequate. More information concerning how to read and understand your trace route can be found here: -- Additional connection information required from players experiencing latency on the Arena Tournament realms If you are playing on our Arena Tournament realms, please also add a back-trace to your post. The back-trace needs to be created using the computer and connection you are playing from. Instructions on how to create the back-trace can be found below: - Visit the following address: http://www.level3.com/LookingGlass/ - Click the Traceroute from Level 3 sites link - Set the Level 3 site to Dusseldorf, Germany and click Submit Attach the trace information displayed on the website to the end of your post. -- NOTE: Please only post all the information that is requested, this is very important as it helps us to compile a report that we can then forward onto our network team. We reserve the right to remove any posts that do not provide all the information requested, as well as any commentary that is not appropriate to the purpose of this thread. Blizzard Entertainment Europe Technical Support Contact info: http://www.wow-europe.com/en/support/technical.html Blizzard Support site: http://eu.blizzard.com/support |
by Igrumu | 09/05/2008 11:24:03 Our networking team are aware of and investigating the following connection issues: Sweden/Norway connectivity: Routing issues to Sweden. Cyclone Battlegroup connectivity: Cyclone Battlegroup problem... Again... Reckoning Battlegroup - Czech Republic, Hungary and other East European countries: Drak'Thul unplayable EVERY DAY from 6pm Misery Battlegroup - Bosnia and Herzegovina: Retrieving character list freeze, Tarren mill If you have not yet done so, we would also request that you contact your respective providers concerning your connection issue. |
| by Gelmkar | 12/05/2008 11:20:58 Shamandra, Arche, Shekilsiz – Looking over the traceroutes you have provided they all seems to show similar information Hop 3 of each of your traceroutes are either showing that your dropping packets or you have very high latency. I would recommend you contact your network provider and show them your traceroutes and ask if they could investigate the matter. Shamandra 1 2 ms 2 ms 1 ms 192.168.2.1 2 54 ms 53 ms 10 ms 78.167.208.1 3 * * * Request timed out. 4 9 ms 17 ms 16 ms uls_t1_1-uls_t2_2.ttnet.net.tr [212.156.121.9] 5 58 ms 12 ms 10 ms uls_ebgp-uls-t1_1.ttnet.net.tr [212.156.119.242] 6 79 ms 97 ms 126 ms 212.156.103.13 Arche 1 18 ms 22 ms 20 ms dsl78.186-52737.ttnet.net.tr [78.186.206.1] 2 27 ms 23 ms * dsl.dynamic21215622666.ttnet.net.tr [212.156.226.66] 3 1186 ms 1211 ms 1293 ms dsl.dynamic21215625293.ttnet.net.tr [212.156.252.93] 4 * * 12 ms izm_t1_1-izm_t2_1.ttnet.net.tr [212.156.120.5] 5 34 ms 23 ms 23 ms uls_t1_1-izm_t1_1.ttnet.net.tr [212.156.120.21] 6 32 ms 23 ms 35 ms uls_ebgp-uls-t1_1.ttnet.net.tr [212.156.119.242] 7 92 ms 95 ms 95 ms 212.156.103.13 Shekilsiz 1 <1 ms <1 ms <1 ms 192.168.1.1 2 * 29 ms 28 ms 78.178.128.1 3 327 ms 597 ms 303 ms 212.156.196.101 4 29 ms 27 ms 27 ms izm_t1_1-izm_t2_1.ttnet.net.tr [212.156.120.5] 5 39 ms 39 ms 39 ms uls_t1_1-izm_t1_1.ttnet.net.tr [212.156.120.21] 6 111 ms 41 ms 40 ms uls_ebgp-uls-t1_1.ttnet.net.tr [212.156.119.242] Ently – Looking over the traceroute that you have provided it would seem that you are dropping packets on the 3 and 4th hop of your trace. The 5th hop is showing quite high latency within in your providers network. I would suggestion you show this traceroute to your provider and ask if they could investigate thia matter with you. 1 <1 ms 1 ms 1 ms 10.0.0.138 2 10 ms 18 ms 10 ms bzq-82-80-129-1.dsl.bezeqint.net [82.80.129.1] 3 * 12 ms * bzq-179-164-81.static.bezeqint.net [212.179.164.81] 4 * * * Request timed out. 5 662 ms * 620 ms bzq-179-124-18.static.bezeqint.net [212.179.124.18] Jermaine – I know you do not want to hear this but you will need to discuss this matter with your provider , note that our realms are located in different locations, as shown in the traceroutes provided. Note that Blizzard have no control over the routing your provider uses , or the data carriers used to peer into our providers networks. 1 <1 ms <1 ms <1 ms . [192.168.2.1] 2 * * * Request timed out. 3 34 ms * * vlan35-k2.otenet.net [62.103.14.129] 4 33 ms 34 ms 32 ms 83.235.5.13 5 33 ms 34 ms 30 ms gig4-0-0-cr02-otenet.ath.oteglobe.net [62.75.3.5] 6 100 ms 100 ms 102 ms gig4-0-50-cr03.ath.OTEGlobe.net [62.75.4.14] 7 93 ms 96 ms 98 ms pos1-0-0-cr01.lon.OTEGlobe.net [62.75.4.74] The 2nd hop I would suspect is normal for your provider as its likely that they are limiting Ping requests on this hop, as it's likely a busy hop. However the 3rd hop appears to be dropping packets. The 6th hop is showing a high spike in latency . I would suggest you discuss this matter with your provider. |
News
Spam
Hot: View Nethaera's Comments on Class Balancing in Patch 2.4
Most Viewed 
Recent Blizzard Announcements
