I know this discussion is going pretty much nowhere since "lag" is such a simple word for something like a TCP/IP connection. Anyways, since noone even cared to post a traceroute I'll take the above quote which shows that in this particular instance the "cloud" has NOTHING to do with the high latency, as the latency already builds up on the route to the cloud. So the "lag" happens before you're even hit the EC2 service.
And saying EC2 just works for Netflix?? What do you base that claim on? For reference:
http://aws.amazon.com/game-hosting/
tl;dr
Probably routing problem, you can't fix it, UO devs cant fix it. Run a tracert and try to contact the hop that is causing lag is probably your best bet.
Oh and I ping 10ms, so I am _pretty_ sure it's not the server...
flame on!
I agree it's probably not the cloud itself but the route to it that's the problem. Although if EA wasn't using Amazon's cloud we wouldn't be using this piss-poor route to the cloud servers. So it's pretty much a problem caused by using the cloud...
Trace routes and these are actually really good today. All my problems come from TeliaSonera International where the route hops arounds Europe. Those are typically 80-100+ ms each.
SONOMA
4 8 ms 10 ms 11 ms rrcs-98-103-112-25.central.biz.rr.com [98.103.112.25]
5 15 ms 15 ms 15 ms be22.pltsohae01r.midwest.rr.com [65.189.179.128]
6 13 ms 15 ms 15 ms be25.clmkohpe01r.midwest.rr.com [65.29.1.28]
7 26 ms 27 ms 23 ms 107.14.19.60
8 24 ms 28 ms 26 ms ae-0-0.cr0.chi10.tbone.rr.com [66.109.6.20]
9 24 ms 23 ms 22 ms ae0.pr1.chi10.tbone.rr.com [107.14.17.192]
10 24 ms 55 ms 24 ms chi-bb1-link.telia.net [213.248.76.97]
11 86 ms 86 ms 84 ms sjo-bb1-link.telia.net [213.155.132.180]
12 85 ms 86 ms 86 ms a100row-ic-300117-sjo-bb1.c.telia.net [213.248.87.118]
13 86 ms 87 ms 87 ms 205.251.229.179
14 93 ms 92 ms 94 ms 205.251.229.233
15 93 ms 95 ms 93 ms ec2-54-241-130-239.us-west-1.compute.amazonaws.com [54.241.130.239]
Trace complete.
ATLANTIC
4 10 ms 9 ms 10 ms rrcs-98-103-112-25.central.biz.rr.com [98.103.112.25]
5 16 ms 15 ms 15 ms be22.pltsohae01r.midwest.rr.com [65.189.179.128]
6 17 ms 15 ms 16 ms be25.clmkohpe01r.midwest.rr.com [65.29.1.28]
7 25 ms 28 ms 27 ms ae-4-0.cr0.chi30.tbone.rr.com [66.109.6.68]
8 28 ms 27 ms 26 ms ae-0-0.cr0.chi10.tbone.rr.com [66.109.6.20]
9 24 ms 24 ms 24 ms ae0.pr1.chi10.tbone.rr.com [107.14.17.192]
10 26 ms 24 ms 25 ms chi-bb1-link.telia.net [213.248.76.97]
11 35 ms 35 ms 36 ms nyk-bb1-link.telia.net [213.155.131.240]
12 45 ms 54 ms 43 ms ash-bb3-link.telia.net [213.155.134.149]
13 66 ms 54 ms 85 ms ash-b1-link.telia.net [80.91.248.159]
14 36 ms 36 ms 36 ms vadata-ic-157232-ash-bb1.c.telia.net [62.115.9.66]
15 37 ms 47 ms 37 ms 72.21.220.55
16 51 ms 37 ms 37 ms 72.21.222.89
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 37 ms 37 ms 37 ms ec2-107-23-95-234.compute-1.amazonaws.com [107.23.95.234]
Trace complete.