Lag? (in General)

Is it just me or is there unbearable lag for you guys? I have tried using both FF and IE. I don't have lag for any other sites.

Not alone, i got Lag! Bad lag!

A bit here.

I thought lately the game had been running REALLY fast.

Seems to be ok now, but occasionally every (20) fights or so I have, it takes awhile for the battle-log to load but not as bad as it was yesterday.

Working very fast at this end; including my home machine, which was running slow for a while.

ok change that I got lag again :'(

6 AM, its exp time, everyones fighting now! lol.

This maybe ignorant but really, how much can a text based game lag?

FF and use the script? i seem to fight at a much slower pace with the GM script

this is getting annoying now! cant even burn BA...i think the problem is AOL. Me, FP and Gandalf all have it and are experiencing Bad lag....It sucks!!

Faster than ever here. ;)

grr damn you johnnywas!

Lucky You! :) you may have time to burn all your BA before XP time ends....i have 3 hours to burn 300+ BA and the future isn't looking bright.

Me been lagging for 2days. Grrr

My Side Bar Isnt loading!!!!

Can anyone explain why only me Spawn and finger Print is getting lag... may not just be us 3... but rest seem to be fine.

Any suggestions please.

The only reason me and spawn could think of is that AOL has some sort of issue with carnage blender, as no other site has given us any issues.

Could someone else who uses AOL tell us if they have a problem too please?

The major problem for me now is the sidebar. It took me 6 minutes to load when I got back in, I lost 6 ba because of it. I'm not really bothered about the ba part but thought I would tell you anyway.

More likely is that CB has a problem with AOL.

CB's working great for me.

Ditch AOL. Get something else. Hehe

Have not had lag in a long time now, ever since the new server came on-line.

now i am lagging a bit, =/

Grrr... Having problems with fighting.

Getting the "don't fight more than once" warning, which took ages (of surfing the forums) to go away before I could fight again, now I've got the 10 minutes lock out. :(

/me feels great that he is having no lag :)

carnage is running abnormally FAST for me too.. strange thing tho!

WOo girlfriends internet has no lag!

Rock 'n' Roll

Lucky You!!

On a friends comp. He also has AOL.

He Also is lagging like hell :(

But i usually use FF at home, so that shouldn't be a problem.

I've lost like 500 BA due to this. So annoying

Yeah I missed exp time and some money time last night, I may ask my mum to change ISP.

Ahh! i thought this would pass? i cant stand the lag anymore :'(

Servers back still lagging on. AoL FF IE. :((((

I don't see any server performance-related lag.

Possibly the colo link has issues w/ some routes. If so, I don't think there's much I can do.

O.O i don't believe it...its got a lil better :) woo! not completely back to normal but it don't take 2 hours to burn 160 BA!!

*Dances*

ok it got a lil worse after i posted before >.< but 160 BA in 20mins....my record for the past few days. Woo

Same here, I can live with this sort of lag. Shame I don't know what Jon means. Hopefully it's just a temporary AOL problem.

This is the trace route.... . Still lagging and posting the results. 1 21 ms 19 ms 21 ms rt-lostd17.dial.aol.com [195.93.23.113]
2 * * * Request timed out.
3 22 ms 20 ms 20 ms accessl2-los-ae3.router.aol.com [172.17.169.60]
4 22 ms 22 ms 23 ms pop1-log-S4-1-0.atdn.net [66.185.145.205]
5 21 ms 22 ms 27 ms Level3.atdn.net [66.185.145.202]
6 34 ms 21 ms 33 ms ae-32-56.ebr2.London1.Level3.net [4.68.116.190]
7 93 ms 90 ms 90 ms ae-4.ebr1.New York1.Level3.net [4.69.132.109]
8 98 ms 91 ms 91 ms ae-91-91.csw4.New York1.Level3.net [4.69.134.78]
9 97 ms 105 ms 103 ms ae-94-94.ebr4.New York1.Level3.net [4.69.134.125]
10 98 ms 97 ms 104 ms ae-3.ebr4.Washington1.Level3.net [4.69.132.93]
11 100 ms 111 ms 107 ms ae-64-64.csw1.Washington1.Level3.net [4.69.134.1 78]
12 96 ms 108 ms 108 ms ae-61-61.ebr1.Washington1.Level3.net [4.69.134.1 29]
13 114 ms 111 ms 121 ms ae-2.ebr3.Atlanta2.Level3.net [4.69.132.85]
14 118 ms 115 ms 117 ms ae-78.ebr2.Atlanta2.Level3.net [4.69.134.53]
15 122 ms 124 ms 124 ms ae-4-4.car2.Miami1.Level3.net [4.69.133.9]
16 124 ms 123 ms 122 ms ae-24-24.car4.Miami1.Level3.net [4.69.133.26]
17 127 ms 125 ms 122 ms 4.68.110.246
18 124 ms 125 ms 123 ms miamfllr2m6-so-1-0-0.ip.epik.net [216.22.67.193]
19 125 ms * 126 ms miamfllrh07-custbr-opens ystems.ip.epik.net [216. 22.64.94]
20 257 ms 127 ms 231 ms ge2-edge.mia.infolink.com [64.251.0.67]
21 * * 127 ms 69.60.124.245

2 * * * Request timed out.

is your problem.

Sounds pretty reasonable. 120ms latency, and most of it happens at the most logical place: when crossing the atlantic.
The packet loss at the last hop is a bit to worry about. Can you run a mtr for a little bit longer than just those 3 attempts tracert does?

drudge: nope. That's not a problem. It's not a router's task to respond to ping requests addressed to itself.

WinMTR statistics

                        Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
               ----------------------------------|------|------|------|------|------|------|
                  rt-lostd17.dial.aol.com -    0 |  110 |  110 |   15 |   50 | 1860 |   15 |
                            195.93.17.126 -   85 |  110 |   17 |   15 |   25 |   47 |   32 |
                            172.17.169.60 -   20 |  110 |   88 |   15 |   32 |  672 |   16 |
                 pop1-log-S4-1-0.atdn.net -    0 |  110 |  110 |   15 |   43 | 1562 |   15 |
                           66.185.145.202 -    4 |  110 |  106 |   15 |   48 | 1516 |   31 |
                             4.68.116.190 -    0 |  110 |  110 |   15 |   47 | 1422 |   32 |
                             4.69.132.109 -    0 |  110 |  110 |   78 |  112 | 1391 |  110 |
                              4.69.134.78 -    0 |  110 |  110 |   78 |  113 | 1297 |   94 |
                             4.69.134.125 -    0 |  110 |  110 |   78 |  110 | 1250 |   93 |
                              4.69.132.93 -    0 |  110 |  110 |   93 |  114 | 1172 |  110 |
                             4.69.134.178 -    0 |  110 |  110 |   93 |  116 | 1062 |   93 |
                             4.69.134.129 -    0 |  110 |  110 |   93 |  119 |  953 |   94 |
                              4.69.132.85 -   15 |  109 |   93 |  109 |  130 |  328 |  172 |
                              4.69.134.53 -    5 |  109 |  104 |  109 |  126 |  329 |  109 |
                               4.69.133.9 -    2 |  109 |  107 |  110 |  147 |  437 |  125 |
                              4.69.133.26 -    1 |  109 |  108 |  110 |  144 |  344 |  125 |
                             4.68.110.246 -    1 |  109 |  108 |  125 |  139 |  297 |  125 |
                            216.22.67.193 -    0 |  108 |  108 |  109 |  135 |  219 |  125 |
                             216.22.64.94 -   41 |  108 |   64 |  125 |  139 |  204 |  141 |
                              64.251.0.67 -   45 |  108 |   60 |  125 |  134 |  157 |  125 |

The packet loss in the first few hops is not a problem (for you). Yes, those routers probably are overworked, but they still perform their primary task (getting packets *through* them) very fine. Latency is also not the cause of your lag. The big problem lies in the last few hops. Either the link between 216.22.67.246 and 216.22.64.94 is problematic, or more likely the latter router. Both machines are from the ISP epik.net, Florida. This is one of the ISPs CB's ISP is connected to. My link to CB happens to go through another ISP, cogentco.com, and that one is running fine.

With a 45% packet loss, up to 45% of the packets you send to and receive from the CB server will need to be sent again, more than doubling the time it takes for the packet to arrive. But, this replacement packet also has a 45% chance of getting lost, causing a 3rd copy of the packet to be sent. Each time this happens, it takes your computer and the CB server also some time to figure out that indeed a packet was lost. So this will result in horrible performance, especially if you realize that a packet is max. 1500 bytes large, so most webpages and images are sent in multiple packets, each with a large chance of getting lost.

if that first column is supposed to be % of packet loss...85% is a lot of packet loss *cough* aol proxy *cough*

Drudge: there's nothing wrong with such a packet loss for that router. Even if it lost 100% of packets addressed *to* it, that's fine, if all packets sent *through* it are unaffected.
OK, it may make things harder to diagnose, but it's simply not a router's job.

i see... i guess then blame epik cause i dont go through them and idont lag, lol.

I go through cogentco and I have no problems with lag.

Yes www.epik.net is down for me.

I happen to be experiencing severe lag from my part of the world. When is this going to be fixed (if it's a problem with the server)?