02/05/2008 - Latency Report Submission Thread
by Gelmkar | 02/05/2008 11:25:52 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: 25/04/08 | Latency 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. [ Post edited by Gelmkar ] 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 Gelmkar | 05/05/2008 16:49:49 Hadaal -- Try running a traceoute to 213.248.123.83, without including the port number that is why you are getting an error when trying to perform a trace to your realm. |
| by Igrumu | 07/05/2008 12:54:21 Hello all, Thanks for the continued trace posts, all valid information posted has been forwarded to our networking team for investigation. We're aware that some players - particularly from Eastern Europe - are having connection issues, this has been reported. I've made comments below on some threads, if there's no comment on your trace it doesn't mean its gone ignored, it simply means that there is no obvious issue with your trace or the issue is caused by factors outside of Technical Supports control. The role of Technical Support is limited when dealing with latency, however the information in your posts has been sent to our networking team who will do all they can to alleviate the connection issues reported. I'd strongly recommend the following posters speak to their provider regarding their trace, particularly the highlighted hops: -- Kyklop 5 23 ms 25 ms 25 ms fr-par02a-rd2-pos-2-0.aorta.net [213.46.160.218] 6 97 ms 99 ms 98 ms us-nyc01b-rd1-pos-12-0.aorta.net [213.46.160.242] -- Tumyp 5 46 ms 46 ms 46 ms 193.232.249.76 6 93 ms 93 ms 93 ms if-7-0.core2.FR1-Frankfurt.teleglobe.net [80.231.65.13] -- Rulic 6 102 ms 101 ms 97 ms ae-12-53.car2.Frankfurt1.Level3.net [4.68.118.80] 7 954 ms 1907 ms 195 ms telia-level3-te.Frankfurt1.Level3.net [4.68.111.102] -- Jonar 3 73 ms 71 ms 70 ms byar-car2-ge0-1-4.rt-comm.ru [195.161.158.17] 4 172 ms 142 ms 139 ms 195.161.47.70 -- Romero 7 83 ms 82 ms 82 ms J7-1-GR-325.ge-0-0-0-7.peterstar.net [84.204.188.37] 8 134 ms 132 ms 134 ms J10-1-GR-LND.ge-1-1-0-7.peterstar.net [84.204.188.13] -- Ilae 5 49 ms * * z.war-ru2.do.war-r4.tpnet.pl [213.25.5.5] 6 * * * UpynĄ limit czasu ľĄdania. 7 271 ms * * ffm-bb1-link.telia.net [80.91.251.215] -- Kosandr 7 71 ms 71 ms 70 ms J7-1-GR-325.ge-0-0-0-7.peterstar.net [84.204.188.37] 8 123 ms 121 ms 121 ms J10-1-GR-LND.ge-1-1-0-7.peterstar.net [84.204.188.13] -- Mertvel 4 31 ms 31 ms 31 ms 79.126.124.29 5 * 124 ms 124 ms 79.126.125.238 -- Moxnaty 5 76 ms 77 ms 76 ms 193.232.249.76 6 116 ms 115 ms 119 ms if-7-0.core2.FR1-Frankfurt.teleglobe.net [80.231.65.13] -- Skvacha 6 93 ms 77 ms 77 ms J10-1-GR-B57.so-1-3-0-0.peterstar.net [84.204.190.77] 7 124 ms 108 ms 93 ms spb-81-211-100-189.sovintel.ru [81.211.100.189] -- Kasyak 7 64 ms 63 ms 62 ms J7-1-GR-325.ge-0-0-0-7.peterstar.net [84.204.188.37] 8 112 ms 112 ms 113 ms J10-1-GR-LND.ge-1-1-0-7.peterstar.net [84.204.188.13] -- Greenbeast 1 681 ms 479 ms 479 ms 10.32.33.18 2 475 ms 519 ms 479 ms 10.32.16.98 3 576 ms 759 ms 599 ms 10.1.141.204 -- Groundar 8 82 ms 84 ms 80 ms 62.189.84.225 9 232 ms 283 ms 272 ms so-4-0-0.xr1.lnd9.alter.net [158.43.150.157] -- Polaras 6 56 ms 55 ms 57 ms 195.229.1.178 7 140 ms 141 ms 140 ms pal9-etisalat-3-ae.pal.seabone.net [195.22.197.181] -- Rhindani 2 127 ms 34 ms 40 ms zagreb2-ge-0-0-0-1.amis.net [194.146.109.1] 3 270 ms 335 ms 347 ms 194.146.109.242 -- Erissin 5 13 ms 13 ms 12 ms tec-KDC1-FT-TEC-C5-G603.fastteleco.net [78.159.161.9] 6 524 ms 500 ms 503 ms 80.81.64.133 -- Dexious 4 29 ms 23 ms * gig4-0-0-cr02-otenet.ath.OTEGlobe.net [62.75.3.5] 5 107 ms 107 ms 107 ms pos7-0-0-cr02.lon.OTEGlobe.net [62.75.4.66] -- Howlin 6 42 ms 41 ms 41 ms 195.229.1.169 7 375 ms 376 ms 362 ms pal9-etisalat-5-ae.pal.seabone.net [213.144.181.45] The following three posters have a peering issue, please speak to your provider so the issue can be tackled from both sides: -- Feleye 5 * * 12 ms ge-2-0-0.war-r4.tpnet.pl [194.204.175.226] 6 * * 239 ms war-b3-pos2-0-0.telia.net [213.248.79.17] -- Badurg 6 30 ms 28 ms 29 ms ffm-b6-link.telia.net [80.91.251.161] 7 96 ms 95 ms 93 ms te-4-3.car2.Frankfurt1.Level3.net [4.68.111.101] -- Hadaal 6 55 ms 29 ms 44 ms 212.200.227.234 7 140 ms 138 ms 154 ms bpt-b2-link.telia.net [213.248.96.157] There follows some comments for a few other posters: -- Coldrazor Your trace times out at every step, try conencting with a wire and seeing if the results improve. -- Dawnee Your issue appears to be caused locally, check your firewall/router and try speaking to your provider: 1 95 ms 99 ms 99 ms speedtouch.lan [10.0.0.1] -- Fuggah I'm not sure where you are tracing to, to run a trace to your realm please use the following IP: 80.239.179.43. -- Strahd Try disconnecting your router for 10-15 minutes to obtain a new IP address, this can often help with disconnection issues when using a Home Hub. You may also like to try connecting with a wire to see if the issue persists. -- Ligeia Please update your post with a trace to your realm, instructions can be found at the beginning of this thread. |
| by Igrumu | 08/05/2008 11:17:47 Morning all, All information posted since my last reply has been forwarded in this morning's forum report. -- Pkz It looks like your latency may be caused at a peering step. Please contact our provider regarding the highlighted steps so the issue can be tackled from both sides: 7 59 ms 55 ms 54 ms Vlan12.icore1.FR1-Frankfurt.teleglobe.net [80.231.65.6] 8 129 ms 132 ms 127 ms ffm-b3-link.telia.net [213.248.69.37] 8 81 ms 113 ms 90 ms Vlan14.icore1.FR1-Frankfurt.teleglobe.net [80.231.64.1] 9 184 ms 181 ms 183 ms ffm-b3-link.telia.net [213.248.69.37] -- Jussio You have high latency straight at hop 1, check your local network and router: 1 88 ms 99 ms 99 ms dsldevice.lan [192.168.1.254] Also, try speaking to your provider regarding hops 4 and 5: 4 48 ms 52 ms 50 ms megaleng-intern.peer.btc.net.bw [168.167.253.4] 5 230 ms 228 ms 233 ms megaleng-int.london_distri.net.bw [168.167.254.129] -- Psyclops Please check your immediate network and router, you have high latency at hop 1: 1 84 ms 93 ms 99 ms speedtouch.lan [10.0.0.1] -- Efsane Try speaking to your provider regarding the highlighted peering hops: 6 uls_t1_1-gyt_t1_1.ttnet.net.tr (212.156.118.38) 14.416 ms 14.398 ms 18.895 ms 7 * * * 8 ldn-b4-link.telia.net (213.248.100.253) 176.825 ms 176.614 ms 176.622 ms -- Bandi You have a large increase in latency between hops 4 and 5, please contact your provider concerning the highlighted hops: 4 * 32 ms 19 ms 213.242.71.50 5 146 ms 206 ms 211 ms 213.242.71.49 -- Ox You'd expect some latency given your location but you may wish to speak to your provider concerning the highlighted hops, particularly 9 and 10: 7 68 ms 67 ms 66 ms 84-235-120-33.igw.com.sa [84.235.120.33] 8 136 ms 129 ms 134 ms pal9-saudi-telecom-devoteam-5-sa.pal.seabone.net [195.22.197.117] 9 180 ms 182 ms 182 ms decix-fra1-racc2.fra.seabone.net [195.22.211.221] 10 285 ms 281 ms 278 ms telia-1-se-decix.fra.seabone.net [195.22.211.110] -- Rosana Your latency begins at a peering step, contact your provider regarding the highlighted hops so the issue can be checked from both sides: 6 33 ms 39 ms 35 kyk15.kyk25.transtelecom.net [217.150.52.106] 7 152 ms 159 ms 149 ms adm-b1-link.telia.net [213.248.78.73] |
| by Igrumu | 09/05/2008 11:25:11 Hello, This Latency Report Submission thread has now been closed, and all Trace Routes have been forwarded to the Networking Team for further analysis. The new Latency Report Submission thread can be found here: 09/05/08 | Latency Submission Thread |
News
Spam
Hot: View Nethaera's Comments on Class Balancing in Patch 2.4
Most Viewed 
Recent Blizzard Announcements
