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 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:
http://forums.wow-europe.com/thread.html?topicId=11155642760&sid=1

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 Cache, Interface and WTF 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.

Steps for Windows XP:
(click on the following article for Vista & Mac OS X steps:
http://eu.blizzard.com/support/article.xml?articleId=18888)

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:

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.

Tsitara -- The problem you are experience seems to begining between the 3rd and 4th hops on your traceroute, there is a large rise in latency between these hops, and it likely the latnecy is leading into the 4th hop from the 3rd.

1 1 ms 1 ms 1 ms 192.168.1.1
2 31 ms 30 ms 29 ms bbras-llu-kln-03L0.forthnet.gr [194.219.231.35]
3 30 ms 31 ms 31 ms core-kln-01-Gi6-0-0.forthnet.gr [62.1.37.129]
4 141 ms 140 ms 140 ms 212.162.9.141
5 137 ms 173 ms * ae-2-79.edge4.Frankfurt1.Level3.net [4.68.23.76]
6 129 ms 135 ms 137 ms telia-level3.frankfurt1.level3.net [4.68.63.122]
7 136 ms 133 ms 134 ms ffm-bb2-link.telia.net [80.91.251.125]
8 267 ms 148 ms 363 ms prs-bb2-link.telia.net [80.91.248.61]
9 141 ms 181 ms 204 ms prs-b1-link.telia.net [80.91.250.249]
10 101 ms 101 ms 101 ms prs-tc-i1-link-telia.net [80.91.250.30]


This is something you should raise with your provider as the its start outside of our providers network, and quite early in your trace route. The likely hood is that this is a peering issue.

Irishtrad --


1 116 ms 130 ms 109 ms 172.16.42.1
2 98 ms 119 ms 109 ms 172.16.42.2
3 138 ms 129 ms 109 ms 172.16.252.162
4 107 ms 119 ms 99 ms ge-1-1-0-213.dub10.ip4.tinet.net [213.200.67.13]
5 138 ms 169 ms 109 ms xe-1-0-0.lon20.ip4.tinet.net [89.149.186.81]
6 117 ms 109 ms 109 ms 213.200.78.238
7 108 ms 108 ms 109 ms ldn-bb1-link.telia.net [80.91.251.166]
8 117 ms 129 ms 130 ms hbg-bb1-link.telia.net [80.91.254.216]
9 189 ms 169 ms 139 ms s-bb1-link.telia.net [80.91.249.9]
10 138 ms 149 ms 169 ms s-b1-link.telia.net [80.91.249.71]
11 148 ms 149 ms 159 ms s-hdn-i3-link.telia.net [80.91.251.245]
12 * * * Request timed out.

Actually I would look closer at home for the what could be the cause of your latency your getting 100ms from the first hop onwards , which for a Broadband connection is too high, you might want to review the configuration of your network, resetting the router/modem nay help

The timeout on hop 12 is perfectly normal, this means that further attempts to trace into our provider network are blocked, you have effectively successfully traced to the realm location you are playing on.

Tsitara -- The issue is leading into that hop from your providers network, Level 3 are one of our providers, they are however are not our peering partner, this is the peering partner your provider is using to route traffic into Telias network.

I can report it on, however this is a matter you should raise with your provider.