West Coast Down

Genghiskhan - Heavens Tear

Can you guys ever NOT **** something up?

Maybe you need to finally admit your servers are in need of some upgrades or something, because there has been NOTHING but issues the past 6 months.

And now we have a daylight maint, followed by this downtime BS during a 3x exp 2x drops event? Yeah, great, if this event is not extended due to this, it is an absolute oversight by your company, this event came as the result of a charity fund raising event, do the right thing here.

opkossy

Can you pony up something showing it's not.. ya know... just you BEFORE you start throwing around the accusations?

Because I'm currently connected to a West Coast server just fine and none of my traceroutes are showing any problems whatsoever. Doesn't help that the vast VAST majority of times people are going own PWE's throats about this, it's not actually them at fault. Sure they do have problems at times, but half the time you folks without a clue what you're talking about are too busy pointing fingers to even do some basic research first.

Genghiskhan - Heavens Tear

Actually I finally got in, talked to several people in my faction who had the same issues

Took me 14 attempts to get in and stay in on my main, 9 on my alt.

Talking to two friends on skype who still can't get in

So no, you twit, it's not just me. It is a widespread issue.

Oh look, 5 person warsong squad, 4 of them already complaining about lag. pings between 3 and 4 thousand.

Friend online talking about how they can't even open an npc to sell drops due to the lag

Wanna tell me more how it's just me?

opkossy

An example of something useful that can help to determine and solve problems:

tracert pwigc4.perfectworld.com

Tracing route to pwigc4.perfectworld.com [66.151.133.70]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms
2 34 ms 28 ms 16 ms
3 8 ms 9 ms 9 ms
4 15 ms 11 ms 11 ms
5 24 ms 23 ms 23 ms be-33661-cr01.56marietta.ga.ibone.comcast.net [6
8.86.95.41]
6 21 ms 22 ms 20 ms c-eth-0-2-0-pe05.56marietta.ga.ibone.comcast.net
[68.86.86.82]
7 23 ms 21 ms 21 ms cogent.iad01.atlas.cogentco.com [75.149.228.26]

8 79 ms 80 ms 79 ms xe-11-3-0.sjc10.ip4.gtt.net [89.149.182.69]
9 85 ms 84 ms 87 ms internap-gw.ip4.gtt.net [77.67.70.26]
10 92 ms 83 ms 91 ms border2.t8-1-bbnet2.sje004.pnap.net [66.151.144.
80]
11 95 ms 82 ms 83 ms perfectworld-10.border2.sje004.pnap.net [64.95.1
43.190]
12 82 ms 83 ms 83 ms 66.151.133.70

Trace complete.

An example of something useless that's full of ignorant accusations with zero useful information and that doesn't help anyone:
This topic.




Wanna try again? Maybe with details and useful information? Your first post's already been proven as false seeing as the servers aren't down, so you aren't doing yourself any favors so far.

Genghiskhan - Heavens Tear

you are clueless. Just go away.

3 tracerts just to appease you. They connect in 14, 14, 15 hops. with the last 3-4 hops each taking 150-200 ms, and the first few taking under 10.

Just poked a couple friends via skype to check their results, SAME thing.

opkossy

Genghiskhan - Heavens Tear wrote: »

you are clueless. Just go away.

"Irony. *ding*"
-CinemaSins

3 tracerts just to appease you. They connect in 14, 14, 15 hops. with the last 3-4 hops each taking 150-200 ms, and the first few taking under 10.

Just poked a couple friends via skype to check their results, SAME thing.

Congratulations. You took step 1 and ran the traceroute. Care to take step 2 and share it with the rest of the class so that where you're running into a problem can be identified and we can work towards solving said issue?

Considering we both ran traceroutes to the same server with such evidently different results, that means the problem is either local, or with something you guys are running into that I'm not. Were it entirely the servers like you're claiming, we'd all have the type of result you have.