Crashing on the New Servers

[unwitting1]

I find that I am crashing a ridiculous number of times since the move took place, and this is nothing like my machine's performance on the old servers. Nothing changed on my end, so what can I do to try and alleviate the problem, if anything?

[FunkySwerve]

Try doing a tracert and see where it stops. I'm having connection difficulties as well, at AMAZONCOM.edge1.Washington1.Level3.net (ip: 4.79.20.14)


C:\>tracert 174.129.216.110

Tracing route to ec2-174-129-216-110.compute-1.amazonaws.com [174.129.216.110]
over a maximum of 30 hops:

1 3 ms <1 ms 3 ms 192.168.2.1
2 7 ms 6 ms 5 ms c-71-226-112-1.hsd1.az.comcast.net [71.226.112.1
]
3 7 ms 5 ms 5 ms ge-1-1-ur01.snyder.az.pima.comcast.net [68.87.17
2.213]
4 6 ms 7 ms 7 ms te-9-2-ar01.pimaco.az.pima.comcast.net [68.87.17
2.17]
5 13 ms 13 ms 13 ms te-0-6-0-4-cr01.santateresa.tx.ibone.comcast.net
[68.86.91.33]
6 26 ms 25 ms 25 ms pos-1-8-0-0-cr01.losangeles.ca.ibone.comcast.net
[68.86.86.13]
7 26 ms 25 ms 25 ms xe-10-2-0.edge3.LosAngeles1.Level3.net [4.71.136
.5]
8 34 ms 33 ms 34 ms vlan79.csw2.LosAngeles1.Level3.net [4.68.20.126]

9 38 ms 35 ms 35 ms ae-73-73.ebr3.LosAngeles1.Level3.net [4.69.137.3
7]
10 96 ms 93 ms 104 ms ae-4.ebr4.Washington1.Level3.net [4.69.132.82]
11 98 ms 107 ms 92 ms ae-64-64.csw1.Washington1.Level3.net [4.69.134.1
78]
12 94 ms 92 ms 92 ms ae-1-69.edge1.Washington1.Level3.net [4.68.17.16
]
13 297 ms 219 ms 232 ms AMAZONCOM.edge1.Washington1.Level3.net [4.79.20.
14]
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 ^C
C:\>


Funky

[Acaos]

Could you give more details about the symptoms you are seeing? We're running the same server software and so on.

Acaos

[unwitting1]

Here's the trace route:

C:\>tracert 174.129.216.110

Tracing route to ec2-174-129-216-110.compute-1.amazonaws.com [174.129.216.110]
over a maximum of 30 hops:

1 * * * Request timed out.
2 5 ms 5 ms 5 ms 68.87.207.5
3 9 ms 7 ms 7 ms be-70-ar01.burien.wa.seattle.comcast.net [68.85.
240.101]
4 13 ms 11 ms 11 ms pos-0-6-0-0-cr01.portland.or.ibone.comcast.net [
68.86.90.221]
5 12 ms 11 ms 11 ms pos-0-0-0-0-cr01.seattle.wa.ibone.comcast.net [6
8.86.85.205]
6 10 ms 11 ms 11 ms te-3-2.car1.Seattle1.Level3.net [4.79.104.105]
7 24 ms 17 ms 18 ms ae-31-51.ebr1.Seattle1.Level3.net [4.68.105.30]

8 19 ms 17 ms 17 ms ae-1-100.ebr2.Seattle1.Level3.net [4.69.132.18]

9 45 ms 38 ms 40 ms ae-2.ebr2.Denver1.Level3.net [4.69.132.54]
10 63 ms 63 ms 63 ms ae-3.ebr1.Chicago2.Level3.net [4.69.132.62]
11 63 ms 63 ms 64 ms ae-1-100.ebr2.Chicago2.Level3.net [4.69.132.114]

12 94 ms 94 ms 94 ms ae-2-2.ebr2.Washington1.Level3.net [4.69.132.70]

13 111 ms 94 ms 103 ms ae-82-82.csw3.Washington1.Level3.net [4.69.134.1
54]
14 94 ms 93 ms 93 ms ae-3-89.edge1.Washington1.Level3.net [4.68.17.14
4]
15 93 ms 94 ms 95 ms AMAZONCOM.edge1.Washington1.Level3.net [4.79.20.
14]
16 * * * Request timed out.
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'm timing out at the same location as Funky.

As for additional details about the crashes, I'm not sure what kind of info you're looking for. They have been happening at any point, anywhere, whether I'm standing still or in combat...except for the third map of Minauros, for whatever reason and/or luck.


Edit: I tacked on the Min exception.

[Ommadawn]

Im also having problems. Here's a tracert:

C:\>tracert 174.129.216.110

Tracing route to ec2-174-129-216-110.compute-1.amazonaws.com [174.129.216.110]
over a maximum of 30 hops:

1 4 ms 3 ms 3 ms voyager.home [192.168.1.1]
2 33 ms 33 ms 34 ms bas503.cwt.esat.net [193.95.136.239]
3 36 ms 33 ms 35 ms vlan500.sw502.cwt.esat.net [193.95.136.125]
4 38 ms 32 ms 33 ms vlan54.sw002.cwt.esat.net [193.95.130.161]
5 37 ms 35 ms 35 ms ge2-0.br003.cwt.esat.net [193.95.129.23]
6 32 ms 33 ms 34 ms xe-0-1-0-104.dub20.ip.tiscali.net [213.200.67.25
3]
7 123 ms 123 ms 125 ms so-3-0-0.was11.ip.tiscali.net [213.200.80.126]
8 121 ms 120 ms 124 ms 77.67.108.34
9 123 ms 120 ms 122 ms 72.21.197.34
10 120 ms 191 ms 120 ms 72.21.197.33
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
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.

www.ip-adress.com/whois/72.21.197.33

72.21.197.33 is Amazon.com also

[FunkySwerve]

highergroundpoa.proboards.com/index.cgi?board=techsupport&action=display&thread=13840

Read my first post there, and what follows.

Funky

[bhao]

... since everybody is timing out at the same position (including me, and i haven't had any lag problems - quite the contrary) it seems pretty clear that amazon ec is not replying to traceroute requests.

this is actually not that uncommon, because it somewhat protects from subnet scans by obscuring the path of the data. not that it's really effective, but it keeps some of the rabble away, i guess.

i would suggest a ping to check for packet loss, but seems that the servers don't reply to those either - which is also good for the same reason.

i really don't think the traceroute timeouts there mean anything in terms of bad connectivity.

edit: gah! funky sort of beat me to it with his link there