Jun 29, 2010, 08:26 PM
Since about Monday June 28, the lag for many players on 2fort regular has been pretty unbearable. There are frequent dropped packets and more infrequent long spikes of packetloss.
This is my most recent tracert taken at 8:21 CDT June 29.
Tracing route to 208.43.8.175-static.reverse.softlayer.com [208.43.8.175]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms 192.168.1.1
2 22 ms 10 ms 9 ms 74-222-208-1.dyn.everestkc.net [74.222.208.1]
3 19 ms 8 ms 8 ms 64-126-2-113.static.everestkc.net [64.126.2.113]
4 8 ms 10 ms 8 ms 64-126-2-5.static.everestkc.net [64.126.2.5]
5 8 ms 19 ms 9 ms 64-126-2-14.static.everestkc.net [64.126.2.14]
6 9 ms 10 ms 9 ms te-4-2.car1.KansasCity1.Level3.net [4.53.32.33]
7 17 ms 18 ms 31 ms ae-5-5.ebr2.Dallas1.Level3.net [4.69.135.230]
8 1307 ms 18 ms 18 ms ae-3-80.edge3.Dallas1.Level3.net [4.69.145.136]
9 20 ms 27 ms 20 ms te2-1.cer01.dal01.dallas-datacenter.com [4.71.19
8.18]
10 23 ms 18 ms 20 ms po1.fcr03.dal01.networklayer.com [66.228.118.186
]
11 19 ms 19 ms 18 ms 208.43.8.175-static.reverse.softlayer.com [208.4
3.8.175]
Here is a summary from a ping 100.
Ping statistics for 208.43.8.175:
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 17ms, Maximum = 783ms, Average = 27ms
Even though you see a huge spike in both, neither of these is atypical for me. Generally play is decent with the occasional short lag spike. Since Monday though, lots of regulars have been complaining that the lag makes the game unplayable.
This is my most recent tracert taken at 8:21 CDT June 29.
Tracing route to 208.43.8.175-static.reverse.softlayer.com [208.43.8.175]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms 192.168.1.1
2 22 ms 10 ms 9 ms 74-222-208-1.dyn.everestkc.net [74.222.208.1]
3 19 ms 8 ms 8 ms 64-126-2-113.static.everestkc.net [64.126.2.113]
4 8 ms 10 ms 8 ms 64-126-2-5.static.everestkc.net [64.126.2.5]
5 8 ms 19 ms 9 ms 64-126-2-14.static.everestkc.net [64.126.2.14]
6 9 ms 10 ms 9 ms te-4-2.car1.KansasCity1.Level3.net [4.53.32.33]
7 17 ms 18 ms 31 ms ae-5-5.ebr2.Dallas1.Level3.net [4.69.135.230]
8 1307 ms 18 ms 18 ms ae-3-80.edge3.Dallas1.Level3.net [4.69.145.136]
9 20 ms 27 ms 20 ms te2-1.cer01.dal01.dallas-datacenter.com [4.71.19
8.18]
10 23 ms 18 ms 20 ms po1.fcr03.dal01.networklayer.com [66.228.118.186
]
11 19 ms 19 ms 18 ms 208.43.8.175-static.reverse.softlayer.com [208.4
3.8.175]
Here is a summary from a ping 100.
Ping statistics for 208.43.8.175:
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 17ms, Maximum = 783ms, Average = 27ms
Even though you see a huge spike in both, neither of these is atypical for me. Generally play is decent with the occasional short lag spike. Since Monday though, lots of regulars have been complaining that the lag makes the game unplayable.