Epic lag on servers starting with a 1

[Lan]

OK, some of you might remember that i posted previously about often being unable to play on 114 or 115 due to it lag/crashing upon loading.

Now that the servers have moved I noticed that the same now happens on servers beginning with a 1. I include the results of 4 traces which I have done, which all seem to end at the same place, with the exception that those servers starting with a 2 seem to play fine, while those with a 1 dont, at all. FYI servers with a 3 at the beginning also work ok.
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\John.JOHN-F71C633B31>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 20 ms 19 ms 22 ms 217.47.108.122
3 18 ms 16 ms 18 ms 217.47.109.161
4 21 ms 19 ms 21 ms 217.47.158.174
5 22 ms 19 ms 20 ms 212.140.206.13
6 21 ms 22 ms 19 ms 217.41.173.65
7 22 ms 20 ms 19 ms 217.41.173.138
8 19 ms 19 ms 19 ms 217.41.173.50
9 24 ms 21 ms 20 ms 213.123.108.241
10 21 ms 19 ms 20 ms londonc-access3-s19.ukcore.bt.net [194.72.2.153]

11 26 ms 26 ms 25 ms core2-pos0-1-5-0.ealing.ukcore.bt.net [62.6.204.
197]
12 26 ms 27 ms 27 ms transit1-gig9-0-0.ealing.ukcore.bt.net [194.72.9
.234]
13 27 ms * 25 ms t2c1-ge14-0-0.uk-eal.eu.bt.net [166.49.168.25]
14 102 ms 100 ms 101 ms t2c1-p4-0-0.us-ash.eu.bt.net [166.49.164.225]
15 117 ms 109 ms 108 ms 166-49-151-134.eu.bt.net [166.49.151.134]
16 * * * Request timed out.
17 108 ms 109 ms 109 ms dcp-edge-01.inet.qwest.net [205.171.251.70]
18 107 ms 108 ms 108 ms 65.120.84.2
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.

C:\Documents and Settings\John.JOHN-F71C633B31>tracert 174.129.216.111

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

1 * * * Request timed out.
2 21 ms 20 ms 22 ms 217.47.108.122
3 21 ms 23 ms 22 ms 217.47.108.161
4 22 ms 21 ms 22 ms 217.47.158.170
5 21 ms 20 ms 21 ms 212.140.206.9
6 24 ms 21 ms 24 ms 217.41.173.138
7 636 ms 21 ms 23 ms 217.41.173.58
8 * 27 ms 24 ms 217.47.108.114
9 22 ms 22 ms 23 ms core2-pos12-2.manchester.ukcore.bt.net [194.72.2
.109]
10 35 ms 34 ms 32 ms core2-pos0-1-5-0.ealing.ukcore.bt.net [62.6.204.
197]
11 36 ms 31 ms 29 ms transit1-gig9-0-0.ealing.ukcore.bt.net [194.72.9
.234]
12 30 ms 34 ms 32 ms t2c1-ge14-0-0.uk-eal.eu.bt.net [166.49.168.25]
13 127 ms 126 ms 127 ms t2c1-p5-0-0.us-ash.eu.bt.net [166.49.164.65]
14 120 ms 115 ms 113 ms 166-49-151-130.eu.bt.net [166.49.151.130]
15 * * * Request timed out.
16 121 ms 124 ms 130 ms dcp-edge-01.inet.qwest.net [205.171.251.74]
17 122 ms 126 ms 125 ms 72.165.161.250
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.

C:\Documents and Settings\John.JOHN-F71C633B31>tracert 174.129.216.211

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

1 * * * Request timed out.
2 23 ms 23 ms 23 ms 217.47.108.122
3 23 ms 24 ms 19 ms 217.47.108.161
4 24 ms 20 ms 19 ms 217.47.158.170
5 22 ms 22 ms 20 ms 212.140.206.9
6 22 ms 19 ms 20 ms 217.41.173.138
7 23 ms 25 ms 19 ms 217.41.173.42
8 26 ms 33 ms 26 ms 217.47.204.177
9 25 ms 22 ms 28 ms londonc-access2-s7.ukcore.bt.net [194.72.2.241]

10 27 ms 29 ms 30 ms 62.6.204.201
11 31 ms 32 ms 28 ms 62.6.200.110
12 28 ms 26 ms 28 ms 166.49.168.25
13 116 ms 116 ms 119 ms 166.49.164.65
14 114 ms 111 ms 109 ms 166.49.151.130
15 * * * Request timed out.
16 121 ms 119 ms 119 ms dcp-edge-01.inet.qwest.net [205.171.251.74]
17 123 ms 119 ms 119 ms 65.120.84.2
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.

C:\Documents and Settings\John.JOHN-F71C633B31>tracert 174.129.216.215

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

1 * * * Request timed out.
2 18 ms 23 ms 36 ms 217.47.108.122
3 19 ms 20 ms 20 ms 217.47.108.161
4 23 ms 23 ms 22 ms 217.47.158.170
5 19 ms 19 ms 19 ms 212.140.206.9
6 26 ms 23 ms 24 ms 217.41.173.138
7 1030 ms 23 ms 20 ms 217.41.173.50
8 26 ms 22 ms 22 ms 213.123.108.50
9 58 ms 35 ms 34 ms londonc-access3-s18.ukcore.bt.net [194.72.2.149]

10 33 ms 33 ms 36 ms core1-pos0-6-0-0.ealing.ukcore.bt.net [62.6.204.
201]
11 36 ms 34 ms 40 ms transit1-gig7-0-0.ealing.ukcore.bt.net [62.6.200
.106]
12 35 ms 36 ms 33 ms t2c1-ge14-0-0.uk-eal.eu.bt.net [166.49.168.25]
13 108 ms 107 ms 109 ms t2c1-p4-0-0.us-ash.eu.bt.net [166.49.164.225]
14 167 ms 106 ms 107 ms 166-49-151-130.eu.bt.net [166.49.151.130]
15 * * * Request timed out.
16 * 118 ms 115 ms dcp-edge-01.inet.qwest.net [205.171.251.74]
17 113 ms 109 ms 112 ms 65.120.84.2
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.

C:\Documents and Settings\John.JOHN-F71C633B31>

I am really hoping that someone can tell me what the problem is here?

[FunkySwerve]

Yomi suggested to me that amazon may be blocking ICMP packets, "which means once you get to amazon's edge, it will show nothing internally". I get the same results from tracerts on non-lagged servers. Working on doing a tracert from Amazon to you, now. Also, how long did the lag last?

Funky

[Lan]

Quick update: I have just successfully managed to enter the bank on 111 so looks like something is getting better!

[FunkySwerve]

[nwn@ip-10-250-7-182 ~]$ traceroute 217.47.108.122
traceroute to 217.47.108.122 (217.47.108.122), 30 hops max, 40 byte packets
1 ip-10-250-4-174.ec2.internal (10.250.4.174) 0.089 ms 0.105 ms 0.093 ms
2 ip-10-250-4-2.ec2.internal (10.250.4.2) 0.333 ms 0.357 ms 0.406 ms
3 ec2-75-101-160-96.compute-1.amazonaws.com (75.101.160.96) 0.553 ms 0.637 ms 0.699 ms
4 216.182.224.13 (216.182.224.13) 0.387 ms 0.451 ms 0.509 ms
5 216.182.224.19 (216.182.224.19) 103.166 ms 103.218 ms 103.276 ms
6 72.21.197.202 (72.21.197.202) 84.861 ms 0.752 ms 0.810 ms
7 216.182.232.76 (216.182.232.76) 1.172 ms 0.817 ms 1.007 ms
8 dcp-edge-01.inet.qwest.net (65.120.84.1) 1.000 ms 1.030 ms 1.184 ms
9 dcx-pcor-02.inet.qwest.net (205.171.251.73) 1.006 ms 1.154 ms 1.176 ms
10 dcp-brdr-03.inet.qwest.net (205.171.251.106) 1.141 ms 1.136 ms 1.114 ms
11 t2c1-ge1-1.us-ash.eu.bt.net (166.49.151.133) 1.143 ms t2c1-ge2-0.us-ash.eu.bt.net (166.49.151.129) 1.112 ms 0.778 ms
12 t2c1-p12-0-0.uk-eal.eu.bt.net (166.49.164.66) 83.193 ms 83.210 ms 83.181 ms
13 ss1.nl-ams.eu.bt.net (166.49.168.26) 83.384 ms 83.271 ms 83.263 ms
14 core1-te0-5-0-2.ealing.ukcore.bt.net (62.6.200.105) 92.181 ms 92.230 ms 92.225 ms
15 core1-pos9-1.manchester.ukcore.bt.net (62.6.204.202) 186.303 ms 186.308 ms *


Your ping is a little high, but not out of the park, for Europe. Def not the connection, at least not at the time I ran this trace.

Funky

[Lan]

Dammit! stuck in the bank now - issue not resolved

[Lan]

Hmm, lag still persisting, managed to get a party invite before it crashed this time.

One thing I will add if its any help, is that occasionally i can pick up an unprotected wireless network from one of the neighbours, when i use this i didnt get any problems with 114 or 115. Unfortunately i'm not picking up any signal tonight so i cant test if this would also work on the new servers.

[FunkySwerve]

Have you updated your drivers recently? Once I had a NIC driver update that gave me unplayable lag until I rolled it back. It sounds like it's a problem with your network or system.

Funky

[TJ]

also an update on the router firmware you use may help also, depending on how old it is. I used to have a NETGEAR RP614v2 that was a pain and whenever there was a moderate load on my home network (which has about 6-8 things on it at a time) such as a TV show download or such, it would crash and have to be reset. This was fixed when I updated the firmware though.

TJ

[Lan]

Well, its certainly odd, but I have just tried my Mrs's pc, she gets lag on 111 just the same. So I thought I would try another router, and low and behold lag has gone, and i have got into the Wyrm. So, it looks like a bad router setting on that router, I will investigate further and post back.

[Acaos]

Lag all over the world is something we track, by the way. Go to snm.hgweb.org and at the top, click on 'Graphs', then 'Machines' then 'Hub 1'. Down near the bottom you'll see a ping graph all over the world, like this:



(you're mostly interested in the 'Current' column)

For the curious:

• Africa - KIXP in Kenya
  
• Australia - Optus
  
• Brazil - PTT
  
• China - HKIX in Hong Kong
  
• EU East - AMS-IX in Amsterdam
  
• EU West - GBIX in the UK
  
• India - STPI
  
• Japan - WIDE in Tokyo
  
• Russia - Moscow
  
• US Central - Texas
  
• US East - Equinix DC
  
• US West - ISC in San Jose
  

If you see something is currently '999' that means there's 20% or more packet loss, or the ping is 1s or higher (in either case, that's a Bad Thing).

Acaos

[Lan]

Bah, trying to display that graph but cant seem to get images to work. Anyway, it all looks pretty close to what Acaos posted, except for the Africa line showing a current of 991. I don't know if this will make any difference.