Tracert information. Need everyones help that is having lag or connection issues please.

Wreaken · April 2014

Ok, so after having multiple issues over the past week or so and bugging my ISP to death and beyond to the point they have insured me that the issue is not on my end OR theirs or anything to do with Australia's network infrastructure (at the current moment), I have decided to dig deeper and start performing tracert checks and IP location checks for the drop outs I am receiving that is 99% of the time, the reason a lot of people have issues connecting, staying connected or lag in game during gameplay.

So to perform a tracert check it is simple, I will do a walk through so everyone can chime in on their bottle necked areas, it is then up to ZOS to get in contact with these companies to rectify these issues.

*NOTE* - Be warned that the first IP address is either your systems IP address or the IP address of your router. Also, the name of your computer will be in the cmd prompt also, so if you do not want this information known, delete it.

First we need some IP addresses to check, easy enough.
http://www.iplocationtools.com/198.20.200.55.html
http://www.iplocationtools.com/198.20.200.167.html

These two ip addresses are ZOS game servers.

Step 1: Performing a Tracert https://www.serverintellect.com/support/techfaq/tracert/
Click your windows button or go to Run >
type in:
CMD which will open up a dos prompt window >
type in:
pathping 198.20.200.167 and let it run until it either completes or finds a location that is unreacheable. We will go over what to do with an unreachable destination later.
Do another check, type in:
pathping 198.20.200.55 and do the same as above.

It will take a few mins to complete. Do not stress and start clicking stuff, go make a coffee, put the washing on and come back and check it.

Step 2: What to do if you have an unreached destination? http://www.iplocationtools.com
So from here, you need to work out who owns that hubs destination, which thanks to the wide world of the internet, is public knowledge. Go to http://www.iplocationtools.com and do a search for the IP address you cannot reach.

Step 3: Now what do I do?
Capture a screen shot of your tracert with the destination that is unreachable and a link to the website I linked above with the correct IP address company that ZOS needs to contact and attach them to your post here. I will start it off as an example.

C:\Users\*******>tracert -d 198.20.200.167

Tracing route to 198.20.200.167 over a maximum of 30 hops

1 2 ms <1 ms <1 ms *.*.*.*
2 37 ms 35 ms 36 ms 150.101.0.207
3 35 ms 63 ms 35 ms 150.101.33.184
4 96 ms 96 ms 121 ms 150.101.33.32
5 242 ms 242 ms 242 ms 203.16.213.65
6 243 ms 244 ms 243 ms 206.223.123.36
7 275 ms 275 ms 273 ms 64.129.234.190
8 * * 66.195.111.98 reports: Destination net unreachable.

Trace complete.

C:\Users\*******>tracert -d 198.20.200.55

Tracing route to 198.20.200.55 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms *.*.*.*
2 36 ms 35 ms 35 ms 150.101.0.207
3 35 ms 46 ms 35 ms 150.101.33.184
4 89 ms 132 ms 89 ms 150.101.33.32
5 243 ms 242 ms 242 ms 203.16.213.65
6 245 ms 243 ms 242 ms 206.223.123.36
7 281 ms 281 ms 282 ms 64.129.234.190
8 * * 66.195.111.98 reports: Destination net unreachable.

Trace complete.

The destination that I am currently having issues with is:
http://www.iplocationtools.com/66.195.111.98.html

Now, I am not sure what that hub is, but as you can see, my tracert is not reaching my selected IP destination correctly and therefore, this hub is the beginning of my issues.

Now, ZOS, can you please have your network team contact this company, have them rectify this issue please so that I can further investigate this issue for any more hubs that are dropping me out.

I urge everyone and anyone who is having issues to perform this check so we can give ZOS feedback and information on what they need to correct this issue.

ZOS, if you cannot rectify this issue, you need to start allowing people to connect using proxies or tunnelling services. It is the only way I can see some people getting around these issues.

cisadanepajsuxrwb17_ESO · April 2014

I used the trial version of lowerping/battleping. The results? It's very sketchy. On a good day, I can actually play in Cyrodiil with less than a second lag (or at least it feels like it). BUT on bad days, like what happened after the easter patch, I havent even been able to PvE let alone cyrodiil. Zone/say chats are bonkers late by almost 1 minute while guild chat is instant. I can move around but I know I dont really move because no one else is moving

And I've tried pretty much everything there is to try. Tracert doesnt give much info other tahn what I already knew.

ArconSeptim · April 2014

WE are having issued in EU so IM not ssuprised for Oceania. They need to relocate the servers as close as possible for their players!

Wreaken · April 2014

cisadanepajsuxrwb17_ESO wrote: »

I used the trial version of lowerping/battleping. The results? It's very sketchy. On a good day, I can actually play in Cyrodiil with less than a second lag (or at least it feels like it). BUT on bad days, like what happened after the easter patch, I havent even been able to PvE let alone cyrodiil. Zone/say chats are bonkers late by almost 1 minute while guild chat is instant. I can move around but I know I dont really move because no one else is moving

And I've tried pretty much everything there is to try. Tracert doesnt give much info other tahn what I already knew.

You need to show the unreachable destinations or ZOS can't help without it.

Wreaken · April 2014

ArconSeptim wrote: »

WE are having issued in EU so IM not ssuprised for Oceania. They need to relocate the servers as close as possible for their players!

Run the tracerts, give us information, whining doesn't help anymore and people need to understand that ZOS can't check every individuals connection to test this, it is up to the players to do a little bit of reconnaissance work to help them find out where this issues are, it is just the nature of the beast.

So show us the tracerts. Other wise I have to ask people, nicely, to please don't post in this thread unless you have the above information to assist in this.

cisadanepajsuxrwb17_ESO · April 2014

Wreaken wrote: »

You need to show the unreachable destinations or ZOS can't help without it.

Umm how I did my tracert was to an IP that I looked up via Windows Resource Monitor for eso.exe when I am already in-game (not during char select screen) so this shd be the IP i am pinging to, right? And of course as per the usual case, the last 4 hops are rtoed on purpose. They dont allow outsiders to ping directly to their servers.

Besides, if you dont have any rto along the way, what can zos actually do?

Wreaken · April 2014

cisadanepajsuxrwb17_ESO wrote: »

Wreaken wrote: »

You need to show the unreachable destinations or ZOS can't help without it.

Umm how I did my tracert was to an IP that I looked up via Windows Resource Monitor for eso.exe when I am already in-game (not during char select screen) so this shd be the IP i am pinging to, right? And of course as per the usual case, the last 4 hops are rtoed on purpose. They dont allow outsiders to ping directly to their servers.

Besides, if you dont have any rto along the way, what can zos actually do?

Char select and in game have nothing to do with anything, it is the same server.

How about you post the information please so we can see the last four hops, are they Zenimax servers? Have you checked them? Who owns them? you should be able to see right up to the IP address you are pinging, however, that is the one that should be unreachable that's if they don't allow pinging, which most servers do when they are less then 1kb.

If you are making it all the way to Zenimax servers, then the issue is on your end unfortunately or somewhere in between.

Kalston · April 2014

Winmtr (free) is far better than tracert because you can leave it running (it's not just one ping at a specific time), so better post WinMTR screens/logs instead. Leave it running, play, then take a look.

Also, for your information, a node not responding in a tracert or WinMTR DOES NOT indicate a problem at all - some nodes are simply setup to not respond to ping requests (that is the case with ESO servers btw, you cannot ping them directly - you can only use WinMTR or Ressource Monitor to check your latency, but with very limited accuracy)

Wreaken · April 2014

louisrabierb16_ESO wrote: »

Winmtr (free) is far better than tracert because you can leave it running (it's not just one ping at a specific time), so better post WinMTR screens/logs instead. Leave it running, play, then take a look.

Also, for your information, a node not responding in a tracert or WinMTR DOES NOT indicate a problem at all - some nodes are simply setup to not respond to ping requests (that is the case with ESO servers btw, you cannot ping them directly - you can only use WinMTR or Ressource Monitor to check your latency, but with very limited accuracy)

We have used this same process of fault finding in previous beta tests and the devs assisted with it, so I can't imagine why all of a sudden, this wouldn't work.

Secondly, if the node is declining ping requests, a simple phone call from their net coding team will resolve that too allow traffic or ping requests through the pipe to the requested IP address. At the same time, they can have them follow a few quick checks which takes 5 mins to rectify to make 100% sure that node is not a bottle neck.

I can almost guarantee with 99.999% certainty, that no matter how many times I do a tracert OR WinMTR test, that my connection will not make it past that destination until it is resolved.

BaKaNoOB · April 2014

Try this
http://technet.microsoft.com/en-us/sysinternals/bb897437.aspx
it is use-full to see ESO server ip , and anything network related

Kalston · April 2014

BaKaNoOB wrote: »

Try this
http://technet.microsoft.com/en-us/sysinternals/bb897437.aspx
it is use-full to see ESO server ip , and anything network related

Win7/8 ressource monitor does that out of the box.

Wreaken wrote: »

We have used this same process of fault finding in previous beta tests and the devs assisted with it, so I can't imagine why all of a sudden, this wouldn't work.

Secondly, if the node is declining ping requests, a simple phone call from their net coding team will resolve that too allow traffic or ping requests through the pipe to the requested IP address. At the same time, they can have them follow a few quick checks which takes 5 mins to rectify to make 100% sure that node is not a bottle neck.

I can almost guarantee with 99.999% certainty, that no matter how many times I do a tracert OR WinMTR test, that my connection will not make it past that destination until it is resolved.

I am not saying it "doesn't work", I am saying that WinMTR is much better and gives much more valuable information (it is the equivalent of ping -t and tracert combined).For example doing a simple ping is worthless because it is just 4 round trips, doing a ping -t for 1h is 3600 round trips - much more potential to show issues, much better data and most importantly you can gather that data while actually playing. Do you get my point now?

And I am pretty sure they made the node decline pings for a reason (it has never been ping-able to my knowledge), which is their choice (can be a security measure) and not actually a "problem". I can't reach that destination either (no one can) but the game still works fine network wise for me and many other people. The destination is reachable, it just does not accept ping requests. Now if you can't log in at all then yeah, that would indicate a problem reaching that destination.

Just to be clear, I only mean to help you and them - I'm not denying your issues or anything.

wrlifeboil · April 2014

Wreaken wrote: »

ArconSeptim wrote: »

WE are having issued in EU so IM not ssuprised for Oceania. They need to relocate the servers as close as possible for their players!

Run the tracerts, give us information, whining doesn't help anymore and people need to understand that ZOS can't check every individuals connection to test this, it is up to the players to do a little bit of reconnaissance work to help them find out where this issues are, it is just the nature of the beast.

So show us the tracerts. Other wise I have to ask people, nicely, to please don't post in this thread unless you have the above information to assist in this.

If ZOS is like Blizzard, they'll only have a say in the routing after it reaches its own network which means AT&T.

Wreaken · April 2014

louisrabierb16_ESO wrote: »

Wreaken wrote: »

We have used this same process of fault finding in previous beta tests and the devs assisted with it, so I can't imagine why all of a sudden, this wouldn't work.

Secondly, if the node is declining ping requests, a simple phone call from their net coding team will resolve that too allow traffic or ping requests through the pipe to the requested IP address. At the same time, they can have them follow a few quick checks which takes 5 mins to rectify to make 100% sure that node is not a bottle neck.

I can almost guarantee with 99.999% certainty, that no matter how many times I do a tracert OR WinMTR test, that my connection will not make it past that destination until it is resolved.

I am not saying it "doesn't work", I am saying that WinMTR is much better and gives much more valuable information (it is the equivalent of ping -t and tracert combined).For example doing a simple ping is worthless because it is just 4 round trips, doing a ping -t for 1h is 3600 round trips - much more potential to show issues, much better data and most importantly you can gather that data while actually playing. Do you get my point now?

And I am pretty sure they made the node decline pings for a reason (it has never been ping-able to my knowledge), which is their choice (can be a security measure) and not actually a "problem". I can't reach that destination either (no one can) but the game still works fine network wise for me and many other people. The destination is reachable, it just does not accept ping requests. Now if you can't log in at all then yeah, that would indicate a problem reaching that destination.

Just to be clear, I only mean to help you and them - I'm not denying your issues or anything.

The distance between the server in question and the game servers themselves is almost 1400 miles or 2253 kilometres.

Server 66.195.111.98 is not the final hop.

One person is saying the final four hops for them is non-reachable, for me, living in Australia I have a total of 8 hops with the final not being reachable, now I can tell you for a fact that for me to make it to the East coast of the USA which is Cockeysville, I would need at least 16 - 20 hops.

Now unless they are masking their IP addresses to look like they are in Cockeysville but are really in Dallas, then I have no idea why they would do that.

Oh also, this node could be creating packet loss but still allowing a connection. For some people that packet loss might be enough to stop them from connecting or getting constantly disconnected all the way through to lagging in game.

An unreachable node could be a multitude of issues, which is why we need to report every node that is not reachable and ZOS networking team follow it up.

The more information the better.

Tristis Oris · April 2014

it would be great if it was the initiative of ZOS, in case of their willingness and ability to influence the routing of their uplinks. It is not always possible, and by home providers at all impossible.
For example my routing break here
http://www.whois.com/whois/12.250.61.22

Wreaken · April 2014

Miss edit....sigh

Viperoz · April 2014

This is my trace-route tonight during the lag period.
Tracing route to 198.20.200.167 over a maximum of 30 hops

5 183 ms 181 ms 182 ms 203.134.2.138
6 183 ms 181 ms 202 ms 173.241.128.13
7 194 ms 193 ms 202 ms 77.67.78.94
8 242 ms 241 ms 244 ms 12.122.86.202
9 245 ms 243 ms 241 ms 12.122.31.133
10 241 ms 242 ms 243 ms 12.122.28.177
11 238 ms 238 ms 239 ms 12.122.138.25
12 12.250.61.26 reports: Destination net unreachable.

Trace complete.

tracert -d 198.20.200.55

Tracing route to 198.20.200.55 over a maximum of 30 hops

5 182 ms 182 ms 181 ms 203.134.2.138
6 182 ms 182 ms 181 ms 173.241.128.13
7 279 ms 194 ms 193 ms 77.67.78.94
8 242 ms 241 ms 240 ms 12.122.86.202
9 240 ms 239 ms 239 ms 12.122.31.133
10 241 ms 241 ms 241 ms 12.122.28.177
11 320 ms 270 ms 328 ms 12.122.138.25
12 * * * Request timed out.
13 * * * Request timed out.
14 12.250.61.22 reports: Destination net unreachable.

Wreaken · April 2014

Excellent Viperoz and thank you very much, as you can see, it is not the same IP address that people are having issues with and they never will unless they route through that same path, you are also having issues with hops 12 and 13.

Tristis Oris · April 2014

edit

wrlifeboil · April 2014

Viperoz wrote: »

This is my trace-route tonight during the lag period.
Tracing route to 198.20.200.167 over a maximum of 30 hops

5 183 ms 181 ms 182 ms 203.134.2.138
6 183 ms 181 ms 202 ms 173.241.128.13
7 194 ms 193 ms 202 ms 77.67.78.94
8 242 ms 241 ms 244 ms 12.122.86.202
9 245 ms 243 ms 241 ms 12.122.31.133
10 241 ms 242 ms 243 ms 12.122.28.177
11 238 ms 238 ms 239 ms 12.122.138.25
12 12.250.61.26 reports: Destination net unreachable.

Trace complete.

tracert -d 198.20.200.55

Tracing route to 198.20.200.55 over a maximum of 30 hops

5 182 ms 182 ms 181 ms 203.134.2.138
6 182 ms 182 ms 181 ms 173.241.128.13
7 279 ms 194 ms 193 ms 77.67.78.94
8 242 ms 241 ms 240 ms 12.122.86.202
9 240 ms 239 ms 239 ms 12.122.31.133
10 241 ms 241 ms 241 ms 12.122.28.177
11 320 ms 270 ms 328 ms 12.122.138.25
12 * * * Request timed out.
13 * * * Request timed out.
14 12.250.61.22 reports: Destination net unreachable.

Just curious, try a traceroute to AT&T on the West Coast at 192.205.36.9.

wrlifeboil · April 2014

Wreaken wrote: »

Excellent Viperoz and thank you very much, as you can see, it is not the same IP address that people are having issues with and they never will unless they route through that same path, you are also having issues with hops 12 and 13.

ggr3.dlxtx.ip.att.net [12.122.138.25] is where the traceroute correctly ends.

patrikblb16_ESO · April 2014

A tracert shows nothing than your connection to various routers.
When your ISP tells you that it is not on their end or your end then it means it is some ISP on the way from your and ESO server. Your ISP is probably routing with other random crappy ISP's and somewhere on the other ISP's network there is a problem. There is nothing in the world you can do about it, it is your ISP that use the cheapest routing table possible. If they were to use one of the big Tier 1 carriers instead you wouldnt have packetloss like you do now.

So to sum it up, it is your ISP's fault no matter how much they want to twist and bend it to make it look like it would be someone else fault.

Viperoz · April 2014

wrlifeboil wrote: »

Viperoz wrote: »

This is my trace-route tonight during the lag period.
Tracing route to 198.20.200.167 over a maximum of 30 hops

5 183 ms 181 ms 182 ms 203.134.2.138
6 183 ms 181 ms 202 ms 173.241.128.13
7 194 ms 193 ms 202 ms 77.67.78.94
8 242 ms 241 ms 244 ms 12.122.86.202
9 245 ms 243 ms 241 ms 12.122.31.133
10 241 ms 242 ms 243 ms 12.122.28.177
11 238 ms 238 ms 239 ms 12.122.138.25
12 12.250.61.26 reports: Destination net unreachable.

Trace complete.

tracert -d 198.20.200.55

Tracing route to 198.20.200.55 over a maximum of 30 hops

5 182 ms 182 ms 181 ms 203.134.2.138
6 182 ms 182 ms 181 ms 173.241.128.13
7 279 ms 194 ms 193 ms 77.67.78.94
8 242 ms 241 ms 240 ms 12.122.86.202
9 240 ms 239 ms 239 ms 12.122.31.133
10 241 ms 241 ms 241 ms 12.122.28.177
11 320 ms 270 ms 328 ms 12.122.138.25
12 * * * Request timed out.
13 * * * Request timed out.
14 12.250.61.22 reports: Destination net unreachable.

Just curious, try a traceroute to AT&T on the West Coast at 192.205.36.9.

Times out at jump 7 173.241.128.13

chizarira39rwb17_ESO · April 2014

I am currently working with ZOS using their game consultant report and with my ISP using the info from that report to run my tracert - after running the tracert tomorrow morning when I can actually log in and play and sending the results to my ISP for comparison, I should hopefully have some answers in the next day or so. I have been very lucky to find an awesome CS person at ZOS, she has been outstanding

Wreaken · April 2014

patrikblb16_ESO wrote: »

A tracert shows nothing than your connection to various routers.
When your ISP tells you that it is not on their end or your end then it means it is some ISP on the way from your and ESO server. Your ISP is probably routing with other random crappy ISP's and somewhere on the other ISP's network there is a problem. There is nothing in the world you can do about it, it is your ISP that use the cheapest routing table possible. If they were to use one of the big Tier 1 carriers instead you wouldnt have packetloss like you do now.

So to sum it up, it is your ISP's fault no matter how much they want to twist and bend it to make it look like it would be someone else fault.

Our packet loss is happening in the states, which means if you live in the states, you will be experiencing it too.

I am running some further tests also.

Wreaken · April 2014

chizarira39rwb17_ESO wrote: »

I am currently working with ZOS using their game consultant report and with my ISP using the info from that report to run my tracert - after running the tracert tomorrow morning when I can actually log in and play and sending the results to my ISP for comparison, I should hopefully have some answers in the next day or so. I have been very lucky to find an awesome CS person at ZOS, she has been outstanding

Awesome job and great news chiz.

wrlifeboil · April 2014

Viperoz wrote: »

wrlifeboil wrote: »

Viperoz wrote: »

This is my trace-route tonight during the lag period.
Tracing route to 198.20.200.167 over a maximum of 30 hops

5 183 ms 181 ms 182 ms 203.134.2.138
6 183 ms 181 ms 202 ms 173.241.128.13
7 194 ms 193 ms 202 ms 77.67.78.94
8 242 ms 241 ms 244 ms 12.122.86.202
9 245 ms 243 ms 241 ms 12.122.31.133
10 241 ms 242 ms 243 ms 12.122.28.177
11 238 ms 238 ms 239 ms 12.122.138.25
12 12.250.61.26 reports: Destination net unreachable.

Trace complete.

tracert -d 198.20.200.55

Tracing route to 198.20.200.55 over a maximum of 30 hops

5 182 ms 182 ms 181 ms 203.134.2.138
6 182 ms 182 ms 181 ms 173.241.128.13
7 279 ms 194 ms 193 ms 77.67.78.94
8 242 ms 241 ms 240 ms 12.122.86.202
9 240 ms 239 ms 239 ms 12.122.31.133
10 241 ms 241 ms 241 ms 12.122.28.177
11 320 ms 270 ms 328 ms 12.122.138.25
12 * * * Request timed out.
13 * * * Request timed out.
14 12.250.61.22 reports: Destination net unreachable.

Just curious, try a traceroute to AT&T on the West Coast at 192.205.36.9.

Times out at jump 7 173.241.128.13

You are going to have to beg/plead with your ISP to change its routing tables as the poster above wrote. I've forgotten the specifics about how Aussies got their best pings to WoW's Los Angeles server years ago but one routing went through Washington state. I know it is or was possible to get into AT&T's network through Hawaii (which is very reliable if you live in Hawaii) to play WoW but never heard of Aussies being routed that way.

chizarira39rwb17_ESO · April 2014

The only thing I cant figure out is why I am only affected after 3pm my time, I can play perfectly fine prior to that - this is why I am thinking it is something to do with my ISP. I am hoping that I might get a result that might actually be of use to other players with this problem - here's hoping

malice_s · April 2014

I am with Iprimus and on the NBN.
These are the results i got

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\>cd\windows\system32
C:\Windows\System32>tracert -d 198.20.200.167
Tracing route to 198.20.200.167 over a maximum of 30 hops

1 1 ms 1 ms <1 ms 192.168.2.1
2 3 ms 3 ms 3 ms 203.134.4.40
3 4 ms 4 ms 3 ms 203.134.72.50
4 140 ms 141 ms 141 ms 203.134.2.138
5 140 ms 140 ms 154 ms 173.241.128.13
6 154 ms 172 ms 153 ms 77.67.78.94
7 200 ms 198 ms 199 ms 12.122.86.202
8 203 ms 198 ms 199 ms 12.122.31.133
9 203 ms 202 ms 202 ms 12.122.28.177
10 219 ms 198 ms 198 ms 12.122.138.25
11 * * * Request timed out.
12 * * * Request timed out.
13 * * ** reports: Destination net unreachable.
Trace complete.

C:\Windows\System32>tracert -d 198.20.200.55
Tracing route to 198.20.200.55 over a maximum of 30 hops

1 1 ms <1 ms <1 ms 192.168.2.1
2 3 ms 3 ms 8 ms 203.134.4.40
3 6 ms 4 ms 4 ms 203.134.72.50
4 141 ms 216 ms 140 ms 203.134.2.138
5 140 ms 140 ms 140 ms 173.241.128.13
6 153 ms 152 ms 152 ms 77.67.78.94
7 198 ms 196 ms 196 ms 12.122.86.202
8 198 ms 199 ms 198 ms 12.122.31.133
9 208 ms 202 ms 201 ms 12.122.28.177
10 200 ms 198 ms 198 ms 12.122.138.25
11 ** reports: Destination net unreachable.
Trace complete.

C:\Windows\System32>

12.122.138.25 = Location UNITED STATES, TEXAS, DALLAS, Connection AT&T WORLDNET SERVICES

Wreaken · April 2014

wrlifeboil wrote: »

Viperoz wrote: »

wrlifeboil wrote: »

Viperoz wrote: »

This is my trace-route tonight during the lag period.
Tracing route to 198.20.200.167 over a maximum of 30 hops

5 183 ms 181 ms 182 ms 203.134.2.138
6 183 ms 181 ms 202 ms 173.241.128.13
7 194 ms 193 ms 202 ms 77.67.78.94
8 242 ms 241 ms 244 ms 12.122.86.202
9 245 ms 243 ms 241 ms 12.122.31.133
10 241 ms 242 ms 243 ms 12.122.28.177
11 238 ms 238 ms 239 ms 12.122.138.25
12 12.250.61.26 reports: Destination net unreachable.

Trace complete.

tracert -d 198.20.200.55

Tracing route to 198.20.200.55 over a maximum of 30 hops

5 182 ms 182 ms 181 ms 203.134.2.138
6 182 ms 182 ms 181 ms 173.241.128.13
7 279 ms 194 ms 193 ms 77.67.78.94
8 242 ms 241 ms 240 ms 12.122.86.202
9 240 ms 239 ms 239 ms 12.122.31.133
10 241 ms 241 ms 241 ms 12.122.28.177
11 320 ms 270 ms 328 ms 12.122.138.25
12 * * * Request timed out.
13 * * * Request timed out.
14 12.250.61.22 reports: Destination net unreachable.

Just curious, try a traceroute to AT&T on the West Coast at 192.205.36.9.

Times out at jump 7 173.241.128.13

You are going to have to beg/plead with your ISP to change its routing tables as the poster above wrote. I've forgotten the specifics about how Aussies got their best pings to WoW's Los Angeles server years ago but one routing went through Washington state. I know it is or was possible to get into AT&T's network through Hawaii (which is very reliable if you live in Hawaii) to play WoW but never heard of Aussies being routed that way.

Not correct, at all.

Netcoding can dictate where it pulls from, aside from many other things that it does, for example. The way that lag is "prevented" is that it is hidden. Information that does not exist yet (it happened in Australia, but you won't know for ~100+ miliseconds, because its traveling at only the speed of light to your computer) is simply made up. Thats right, you make up the information, and your computer will play with the made up information.

In ~100 milliseconds, the information of your opponent will appear. Its a bit slow, but it should be enough to synchronize things just a little bit.

So really, a good "netcode" predicts what your opponent will do, and then displays it to you with reasonable accuracy. It can be cubic splines (in a FPS) or something similar... but at the end of the day, your netcode will have to make up information if your players want "low lag" in these conditions.

It is possible that maybe the netcoding of the game needs some fine tuning or optimizing.

That being said, ZOS has the power to talk to the companies and convey with them on how to resolve the issue with the ports at the node to allow free flow through, and it would be in ZOS's best interest to do so and not just for Australian users, EU and USA players will benefit from it also.

Cauthorn · April 2014

Similar result as you @wreaken

Tracing route to 198.20.200.167 over a maximum of 30 hops

1 1 ms <1 ms <1 ms 192.168.0.1
2 25 ms 24 ms 24 ms 203.23.236.9
3 25 ms 28 ms 43 ms 203.23.236.45
4 26 ms 26 ms 24 ms 59.154.10.17
5 174 ms 178 ms 176 ms 203.208.174.49
6 248 ms 172 ms 175 ms 203.208.171.118
7 175 ms 173 ms 177 ms 66.192.252.45
8 213 ms 214 ms 214 ms 64.129.234.190
9 * * 66.195.111.98 reports: Destination net unreachable.

Tracing route to 198.20.200.55 over a maximum of 30 hops

1 1 ms <1 ms <1 ms 192.168.0.1
2 23 ms 23 ms 24 ms 203.23.236.9
3 24 ms 25 ms 24 ms 203.23.236.45
4 25 ms 221 ms 42 ms 59.154.10.17
5 176 ms 204 ms 175 ms 203.208.174.49
6 176 ms 174 ms 175 ms 203.208.171.146
7 173 ms 174 ms 173 ms 66.192.252.45
8 212 ms 212 ms 215 ms 64.129.234.190
9 * * * Request timed out.
10 66.195.111.98 reports: Destination net unreachable.

chizarira39rwb17_ESO · April 2014

Where did you get the IP address that you are using from?