Extreme Latency 11-21-13

[Whois]

I live in California USA...

Not sure where this is hosted as I don't do Whois on people, but I was having very bad lag since about 7pm tonight and finally couldn't even buff my toons or hail fairy because I was 2500-6k latency...

Then eventually my mouse would lock up on screen and id be dc'd

So I ran a speedtest on my wifi and my main line, Main line is 73mb/s, wifi is 19-28mb/s

I reset my pc many times even edited the host file again to revert back to emu login.. same issue...

Finally I ran a tracert to thehiddenforest.org... And everything seemed ok till line 16, 16 timed out, then 17 was fine, then 18-30 timed out.

Now I see where the issue was just after a paris hop, everything disconnected.

I just would like to know if anyone else had this issue tonight 11/21/13 at approx. 7:30 PST USA... Because it got extremely annoying and nothing on my end was changed except the updated patcher w spell file, and I was running fine with it for about 2 hrs.

Please if u can run your traecrt as well, Those that don't know how go into accessories and command prompt.

Once that brings up the msDos command prompt, simply type at the C prompt, tracert thehiddenforest.org, making sure there is space between tracert and server name, then push enter...

It should cycle through 30 or less hops, and pls make note of where if any timeout responses occur.

Thanks all, hoping others had same issue and report it.

[cbarrett]

It's not just you. Same issue here, cant hail any npcs or self buff.

[Lillu]

I'll reboot the server now, let's see if it fixes anything.

Unfortunately these issues are 99% unrelated to the server. It can be a DNS problem, cyber war over the Internet, temporary routing issues, anything really..

In very rare cases, if it's a server related issue, you wouldn't see players online: webtools/online.php

[Smoka]

Was weird this morning. 6 chars on, 4 were fine, 2 had 4k + pings. =)

[Whois]

Lillu I just got home from work and haven't checked yet, but speaking to a friend on phone he said he had same issue in South Dakota. At least I wasn't alone last night, thought yet another dang file of mine went corrupt.

This appeared to be a dns error from line 16 on. from 18-30 was all time outs. It fell apart just after a paris link.

Anyhow ty for rebooting and lets hope it worked!!!