CWKPQ Glitched?

Describe the problem. Be as specific as possible!:
On stage four(with the stirges and flames) two times my guild has activated all five of the sigils and the portal to the next stage did not open. Can anyone else confirm this?

 Images of problem

None

Maybe they activated a fake sigil or two.

Does this exclude the "fake" sigils?

Maybe they activated a fake sigil or two.

Does this exclude the "fake" sigils?

Yes we activated the real ones. It said Archer, Mage, Warrior, Pirate, and Theif sigils have been activated.

I like to point out that in the second run, my aran didn't receive the message saying "Warrior sigil has been activated", even though the blue circle thingy on the sigil turned when I activated and my guild-mates did in fact see the message, but not me.

I thought this was about another problem. On friday, up to 75% of my group got d\cd in cwkpq. 8\12 d\cd after bosses died - game froze then we d\cd, not all at once but one after another. The second run 6\12 started d\cing 5 seconds after we entered the PQ.

I sent a ticket about it. Took their answering machines two days to tell me they are too busy to answer.

I thought this was about another problem. On friday, up to 75% of my group got d\cd in cwkpq. 8\12 d\cd after bosses died - game froze then we d\cd, not all at once but one after another. The second run 6\12 started d\cing 5 seconds after we entered the PQ.

I sent a ticket about it. Took their answering machines two days to tell me they are too busy to answer.

You know, I have noticed alot of dcing in cwkpq lately.

Our thief dc'ed in first stage first run, and our paladin dc'ed in the fourth stage second run. Not to mention in our run before that, our warriors dc'ed at the same time in third stage as well.

I thought this was about another problem. On friday, up to 75% of my group got d\cd in cwkpq. 8\12 d\cd after bosses died - game froze then we d\cd, not all at once but one after another. The second run 6\12 started d\cing 5 seconds after we entered the PQ.

I sent a ticket about it. Took their answering machines two days to tell me they are too busy to answer.

Have you experienced this since this last server check, or since v97