world not loading in fast enough

[ZerotheFang.5890]

so LA when i loaded in loaded slowly amnoon for story nope see NPCs and plants and building walls no land or map terrain. its not a graphic thing and i am not lagging cause i checked.

[Ashantara.8731]

That's a routing issue with GW2. I contacted support on behalf of this issue, still no response.

 

It is the only online game (or online application in general) I run that has more "timed out" hops and packet losses when you do a traceroute than actually functional ones. The routing (i.e., the path taken to connect to their servers) is awful, and I want to know why.

 

P.S. It is 100% certain that my provider is not at fault as (a) they spent the past three weeks looking into this and re-assured me it wasn't an issue on their end, and (b) any other online application/game has clean traceroute and ping results (i.e., connects perfectly) when I monitor them with only a few hops needed to connect to their server and no packet losses.

[ZerotheFang.5890]

well considering all the disconnects today with living world eh it always happens around big patch times.

[SlippyCheeze.5483]

> @"Ashantara.8731" said:

> That's a routing issue with GW2. I contacted support on behalf of this issue, still no response.

>

> It is the only online game (or online application in general) I run that has more "timed out" hops and packet losses when you do a traceroute than actually functional ones. The routing (i.e., the path taken to connect to their servers) is awful, and I want to know why.

 

They have a bunch of routers on the common path, including within AWS, that do not respond to diagnostic packets at all. (Most cloud providers have similar policies, FWIW.)

 

When you are looking at these, does the packet loss or latency stay high on all subsequent hops, or does it go back down to a "normal" value? The former is the sure sign that this is just a router not responding to diagnostics, but passing traffic through just fine.

[Ashantara.8731]

"AWS"? "FWIW"? Sorry, I am not a native speaker, so you got me at a loss here. ;)

 

Here is an example of a traceroute I did (and I did many over the course of a week for diagnostic reasons with my provider, also netstat etc.):

 

-----------------------------------------

 

tracert 35.156.132.82

 

Tracing route to ec2-35-156-132-82.eu-central-1.compute.amazonaws.com [35.156.132.82] over a maximum of 30 hops:

 

1 2 ms 1 ms 1 ms IP removed for privacy reasons

2 14 ms 14 ms 12 ms IP removed for privacy reasons, but quick, clean hop

3 28 ms 16 ms 30 ms at-vie05d-rc1-ae11-0.aorta.net [iP removed for privacy reasons, but quick, clean hop]

4 13 ms 14 ms 12 ms at-vie15a-rd1-ae39-0.aorta.net [iP removed for privacy reasons, but quick, clean hop]

5 17 ms 18 ms 16 ms at-vie05b-ri3-ae12-0.aorta.net [iP removed for privacy reasons, but quick, clean hop]

6 14 ms 12 ms 11 ms 52.95.219.164

7 29 ms 31 ms 34 ms 52.93.38.52

8 47 ms 32 ms 33 ms 52.93.38.61

9 30 ms 28 ms 27 ms 54.239.44.47

10 48 ms 26 ms 26 ms 52.93.128.141

11 * * * Request timed out.

12 * * * Request timed out.

13 43 ms 65 ms 27 ms 52.93.111.31

14 28 ms 29 ms 29 ms 52.93.111.16

15 63 ms 29 ms 31 ms 54.239.107.27

16 29 ms 29 ms 33 ms 52.93.23.122

17 * * * Request timed out.

18 * * * Request timed out.

19 * * * Request timed out.

20 * * * Request timed out.

21 * * * Request timed out.

22 * * * Request timed out.

23 * * * Request timed out.

24 * * * Request timed out.

25 * * * Request timed out.

26 * * * Request timed out.

27 * * * Request timed out.

28 * * * Request timed out.

29 * * * Request timed out.

30 * * * Request timed out.

 

Trace complete.

 

-----------------------------------------

 

I think it was you who recommended PingPlotter to me for better display of % packet loss etc., and the results were _not good_.

[Healix.5819]

> @"Ashantara.8731" said:

> Here is an example of a traceroute I did (and I did many over the course of a week for diagnostic reasons with my provider, also netstat etc.):

 

Pings are not guaranteed to be responded to and can be entirely ignored or even delayed. A lot of Amazon's nodes simply ignore them, hence the timeouts. It doesn't actually mean anything, nor does spots of packet loss. You can have half the nodes dropping packets for example, but none of that matters if the final hops aren't dropping any. Unfortunately the GW2 instances don't respond to pings, so the best you can do is use PingPlotter to see how the connection fares up to that point.

 

If you actually want to ping the EU servers and get a response, try 54.93.162.162.

[MrFayth.3546]

> @"Ashantara.8731" said:

> "AWS"? "FWIW"? Sorry, I am not a native speaker, so you got me at a loss here. ;)

 

AWS=Amazon something something, I'm guessing since sort of recently Gw2 moved to amazon servers. and

 

FWIW= For what it's worth.