M
Mystikal GIL
Guest
Hopefully we'll have some clarification by monday.
Okay, with all honesty. This lag is starting to p*ss me off.
I pay $13.00 a month for a 2D game with a dying community and a company like EA/Mythic can't even fix a server lag issue in less than eight days...? I rely on being able to PLAY Ultima Online in order to update my website, but the second I login I move like a horrible slideshow.
Fix this **** now. It's really, really starting to get aggravating. I don't play UO religiously since I have tons of other things like school, homework, work, etc., but not once have I logged in in the past week and been able to run five feet in less than 10 seconds on a broadband connection. How many traceroutes, pings, GM pages, support emails, support telephone calls, and staff members does it take to fix lag? We're talking lag here folks, not an irrecoverable server crash.
It seems obvious that all this began when they started preparing for mergers and transfers in Warhammer. (you know that game which is the new WoW killer after Age of Connan tanked) Unfortunatly EA dosn't care if this bothers or annoys you. Warhammer is their baby and momey maker right now. So, if they have to step on your toes, I don't think they really care.I Second this!
The game is worthless unless you can move and do things without being aggravated every 2 seconds.
Lets go EA Mythic, people are pissed!
LOL Obviously you play on siege for a reason, no? With a lag of 110 on lets say atlantic, or great lakes, playing a mage by the time you cast a second spell you are dead. You can studder with a dexxer because he swings automatically however a mage doesnt cast unless you push the button. On a dexxer all you notice is a skip in your step. For a mage there is a skip in your step and a lag in casting.Hrm I play siege from Denmark, I ping 110 normally. That is a fine ping even for pvp.
i dont know about you guys, but it has really cleared up this morning
Host Name IP Address Hop Ping Time Ping Avg % Loss Pkts r/s Ping best/worst
te1-4.ccr01.cph01.atlas.cogentco.com 149.6.136.29 4 18ms
te3-3.ccr01.ham01.atlas.cogentco.com 130.117.3.205 5 13ms
te2-4.ccr01.dus01.atlas.cogentco.com 130.117.48.141 6 19ms
te3-1.ccr02.ams03.atlas.cogentco.com 130.117.3.89 7 27ms
te2-1.ccr01.lon01.atlas.cogentco.com 130.117.1.170 8 34ms
te9-3.ccr01.jfk02.atlas.cogentco.com 66.28.4.41 9 140ms
te4-1.mpd02.dca01.atlas.cogentco.com 154.54.5.50 10 116ms
vl3492.mpd01.dca02.atlas.cogentco.com 66.28.4.86 11 113ms
te8-1.ccr01.iad01.atlas.cogentco.com 154.54.2.50 12 117ms
* Unknown Host * 192.205.35.105 13 110ms
tbr1.wswdc.ip.att.net 12.123.8.186 14 117ms
gar2.ascva.ip.att.net 12.122.113.9 15 115ms
* Unknown Host * 12.116.77.34 16 112ms
fert07-eqx-iad.ea.com 159.153.224.226 17 203ms
* Unknown Host * 159.153.233.47 18 204ms
Woman, not manMan its so brutal, I love getting ganked in slow motion
Tracing route to central-eu1.owo.com [159.153.156.138]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms DD-WRT [192.168.1.1]
2 11 ms 21 ms 10 ms 70.77.60.1
3 27 ms 17 ms 15 ms rd2cs-ge3-1.ok.shawcable.net [64.59.171.3]
4 20 ms 20 ms 21 ms rc1wh-ge6-0-0-1.vc.shawcable.net [66.163.77.206]
5 32 ms 32 ms 30 ms rc1so-pos11-0.cg.shawcable.net [66.163.76.9]
6 50 ms 46 ms 47 ms rc1nr-pos0-7-4-0.wp.shawcable.net [66.163.76.194
]
7 47 ms 73 ms 45 ms rc2sc-tge0-0-1-0.wp.shawcable.net [66.163.73.182
]
8 75 ms 72 ms 69 ms rc1sh-pos13-0.mt.shawcable.net [66.163.76.73]
9 83 ms 84 ms 86 ms rc1hu-pos1-0.ny.shawcable.net [66.163.76.14]
10 85 ms 83 ms 83 ms rd1ny-pos10-0.ny.shawcable.net [66.163.74.21]
11 160 ms 156 ms 159 ms 195.66.224.186
12 * * * Request timed out.
13 223 ms 207 ms 218 ms 62-244-180-54.cust.exponential-e.net [62.244.180
.54]
14 163 ms 163 ms 174 ms 80.69.16.174
15 170 ms 172 ms 169 ms fert01-ixe-lhr.ea.com [159.153.156.2]
16 155 ms 171 ms 155 ms 159.153.156.138
Trace complete.
Host Name IP Address Hop Ping Time Ping Avg % Loss Pkts r/s Ping best/worst
er-1-fe00.gsv.md.atlanticbb.net 207.255.176.1 4 10ms 22ms 1% 1173 / 1186 8ms / 314ms
ge-5-2-126.hsa2.Baltimore1.Level3.net 4.78.142.25 5 15ms 19ms 0% 1184 / 1186 10ms / 89ms
so-6-1-0.mp2.Baltimore1.Level3.net 4.68.112.73 6 14ms 24ms 0% 1184 / 1186 11ms / 164ms
ae-0-0.bbr2.Washington1.Level3.net 4.68.128.210 7 17ms 27ms 0% 1183 / 1186 12ms / 4922ms
ae-13-69.car3.Washington1.Level3.net 4.68.17.5 8 14ms 30ms 0% 1177 / 1186 12ms / 240ms
ELECTRONIC.car3.Washington1.Level3.net 4.79.169.74 9 19ms 26ms 0% 1180 / 1186 13ms / 5255ms
fert07-eqx-iad.ea.com 159.153.224.230 10 114ms 125ms 7% 1094 / 1186 111ms / 318ms
* Unknown Host * 159.153.233.35 11 117ms 120ms 7% 1099 / 1186 110ms / 451ms
I'm seeing a spike at 144.223.246.6 as well, but only in the 123ms range so I'm not missing the server heartbeat as often.It starts with 144.223.246.6, a sprintlink hub, and goes on to the ea hubs.
It's back worse than ever for me :X
It's obvious where the ping issues and packetloss is... EA needs to check thier hardware. I'll be shutting my last account down if it's not addressed & stabilized i'll be out. I can deal with the imbalances, bugs, and everything else, but what fun is it when you can't even walk around in the game and do something as simple as putting your suit back on without getting frusturated cause it takes two minutes...Code:Host Name IP Address Hop Ping Time Ping Avg % Loss Pkts r/s Ping best/worst er-1-fe00.gsv.md.atlanticbb.net 207.255.176.1 4 10ms 22ms 1% 1173 / 1186 8ms / 314ms ge-5-2-126.hsa2.Baltimore1.Level3.net 4.78.142.25 5 15ms 19ms 0% 1184 / 1186 10ms / 89ms so-6-1-0.mp2.Baltimore1.Level3.net 4.68.112.73 6 14ms 24ms 0% 1184 / 1186 11ms / 164ms ae-0-0.bbr2.Washington1.Level3.net 4.68.128.210 7 17ms 27ms 0% 1183 / 1186 12ms / 4922ms ae-13-69.car3.Washington1.Level3.net 4.68.17.5 8 14ms 30ms 0% 1177 / 1186 12ms / 240ms ELECTRONIC.car3.Washington1.Level3.net 4.79.169.74 9 19ms 26ms 0% 1180 / 1186 13ms / 5255ms fert07-eqx-iad.ea.com 159.153.224.230 10 114ms 125ms 7% 1094 / 1186 111ms / 318ms * Unknown Host * 159.153.233.35 11 117ms 120ms 7% 1099 / 1186 110ms / 451ms
Host Name IP Address Hop Ping Time Ping Avg % Loss Pkts r/s Ping best/worst
bb2-g3-2-0.bcvloh.sbcglobal.net 151.164.43.156 4 5ms 5ms 0% 52 / 52 4ms / 7ms
* Unknown Host * 12.83.63.137 5 21ms 20ms 0% 52 / 52 20ms / 24ms
asn3356-level3.eqnwnj.sbcglobal.net 151.164.89.250 6 21ms 22ms 0% 52 / 52 20ms / 79ms
ae-31-51.ebr1.Newark1.Level3.net 4.68.99.30 7 32ms 25ms 0% 52 / 52 21ms / 34ms
ae-1-100.ebr2.Newark1.Level3.net 4.69.132.22 8 26ms 26ms 0% 52 / 52 21ms / 34ms
ae-4.ebr3.Washington1.Level3.net 4.69.132.101 9 35ms 26ms 0% 52 / 52 23ms / 36ms
ae-83-83.csw3.Washington1.Level3.net 4.69.134.170 10 32ms 28ms 0% 52 / 52 24ms / 34ms
ae-33-89.car3.Washington1.Level3.net 4.68.17.133 11 24ms 32ms 0% 52 / 52 23ms / 194ms
ELECTRONIC.car3.Washington1.Level3.net 4.79.169.74 12 24ms 24ms 0% 52 / 52 23ms / 26ms
[b]fert07-eqx-iad.ea.com 159.153.224.230 13 122ms 121ms 9% 46 / 51 121ms / 123ms[/b]
* Unknown Host * 159.153.233.35 14 121ms 121ms 9% 46 / 51 121ms / 122ms
Yes.. or maybe the found a cure for dupisum.. and are now implamenting itMaybe they are doing physical maintenance on servers and that's why it is lagging again...maybe they are currently fixing it.
One can only hope![]()