Guild Wars 2

Tired of the default answer to questions of DC or lag being a der de der “is your hardware gewd?” … just announce that your set up has failed and you are not given enough money to care…at least when I pay monthly fees I know some kitten is working to fix it

It is not your systems, it is nor your servers… it is the datacenter.

Source: If it is game servers, everyone would have the same problem. But it is not the case, one do and some don’t depends where you live and connected from. Datacenter and ISP communication routing your connection packets has a lot to do from your location.

Just like going to work everyday, you’re in traffic. Take different highways. Some people get to work fast before you because they live where there are no traffics.

Zefrost.3425:

So… they should fix those data centers then, yes?

As far datacenter such as Level3 for example. Common senses, please.

From what I have seen in other posts here lately, it appears that Level 3 have been routing traffic in US thru Europe and back to USA again, this would cause some major lag on the way !

It definitely does not seem to be an issue on my end. I’ve reset firewall rules, disabled the firewall, disabled all AV, repaired the client, and none of them seem to have done anything to the problem. I’m now reinstalling the game.

Zefrost.3425:

So… they should fix those data centers then, yes?

Your ISP has 10x more ability to get this done than Anet……run a TraceRT to a laggy Anet server and submit a ticket to your local ISP (include the Tracert data).

It is not reasonable to expect Anet to monitor every possible routing issue into their servers from every possible ISP on the planet (even if they can detect a problem, they have no means to fix it).

If your connection issues in anyway look like they may be better or worse at certain times of the day, it may be your ISP is throttling your bandwidth and causing some issues. Very often the very mention of the term “throttling” to your ISPs Customer Service might miraculously clear up the issue.

I agree with the title (well, maybe it is Murphy).

been through this hundreds of times on these forums. You guys that think this falls on Arena Net just dont have a single clue to the matter.

Do as said above, TraceRT to any of the following addresses;

206.127.159.116
64.25.38.72

auth1.101.arenanetworks.com
64.25.38.72:6112 – connect succeeded
64.25.38.171:6112 – connect succeeded
64.25.38.172:6112 – connect succeeded
64.25.38.51:6112 – connect succeeded
64.25.38.54:6112 – connect succeeded

auth2.101.arenanetworks.com
206.127.146.73:80 – connect succeeded
206.127.146.74:80 – connect succeeded
206.127.159.77:80 – connect succeeded
206.127.159.107:80 – connect succeeded
206.127.159.108:80 – connect succeeded
206.127.159.109:80 – connect succeeded
206.127.146.73:6112 – connect succeeded
206.127.146.74:6112 – connect succeeded
206.127.159.77:6112 – connect succeeded
206.127.159.107:6112 – connect succeeded
206.127.159.108:6112 – connect succeeded
206.127.159.109:6112 – connect succeeded

auth1.101.arenanetworks.com
64.25.38.72:80 – connect succeeded
64.25.38.171:80 – connect succeeded
64.25.38.172:80 – connect succeeded
64.25.38.51:80 – connect succeeded
64.25.38.54:80 – connect succeeded

File1.ArenaNetworks.com
64.25.39.21:6112 – connect succeeded
64.25.39.21:80 – connect succeeded

Diag.ArenaNetworks.com
206.127.158.31:6112 – connect succeeded
64.25.39.21:6112 – connect succeeded
206.127.158.31:80 – connect succeeded
64.25.39.21:80 – connect succeeded

origincdn.101.arenanetworks.com
64.25.41.2:80 – connect succeeded

Then report that TraceRT to YOUR isp so they can open a ticket with their EDGE provider to narrow down the issue (Cut fiber, bad FPU on a router, over subscription) and get it fixed properly.

ANet doesn’t have Edge transport contracts with every backbone provider out there. That is the JOB of your localized ISPs to take care of.

I chaged ISP (Michigan) and connection started to fail:
Diag.ArenaNetworks.com
64.25.39.21:80 – connect succeeded
64.25.39.21:6112 – connect succeeded
206.127.158.31:6112 – connect failed <——
206.127.158.31:80 – connect failed <—-
I ran trace and found out that fault is on NC side. It runs thru 206.127.157.86 & 206.127.157.102 then chokes with multiple timeouts…
Is it app client bug ? Is the resolution – reload GW2 client?