DarkStar.3620

They had the same bug a few months back, where loading screens took an insane amount of time for everyone who was using the /maploadinfo switch (or whatever it was called). Maybe they re-introduced that, just that it now affects everyone :-D

That was an IP for one of the old EU NCSoft servers, which was closed years ago. GW2 has been at Amazon since around PoF. The login servers are auth1.101.arenanetworks.com for NA and auth2.101.arenanetworks.com for EU, but note that they won't respond to pings. Interesting, so why does "gw2.exe -diag" then still try to connect to those? hmm...

Problem seems to be the connection to the authentication servers C:\>ping 206.127.159.108Pinging 206.127.159.108 with 32 bytes of data:Reply from 62.155.245.225: Destination net unreachable."Destination Net unreachable" sounds like a routing problem. The IP in question belongs to NCSoft's network (AS30588), which doesn't seem to (correctly) announce it, only the 64.x.x.x addresses. That's why my provider's network (DTAG) doesn't find the route to the target network which leads to the connection issues that people report. No idea how this still works with other providers, as it looks likely to be a problem on NCsoft's side. Maybe other providers still cache the old BGP routes for longer periods of time... Maybe someone else with more BGP experience can chime in here...