I got this result of raw transaction check
An outpoint is already spent [(109508977, 1), (109625375, 0), (109405785, 1), (109620108, 6), (109622069, 0), (109620194, 0), (109601345, 1), (109624787, 0)]
What does it mean? Paid or not? or problem?
That's the main issue with the broken withdrawals at the moment. Gox's system is double-spending (or attempting to). The outpoints are not being collected and used correctly by their system, so your transfer gets stuck. Normally, it would simply re-broadcast with a fresh set of outputs a few hours later -- but, that isn't happening either.
Their "support" on IRC is claiming that they still don't know what is causing the issue. It could be a problem with their code, or it could be the result of a dust-related DDOS attack (which is what they claimed in November when the same thing happened).
Nobody knows (except maybe them) how/why their system is broken, so we'll just have to wait and see.
AFAIK, they are manually pushing through the broken TX one at a time, and at a snail's pace. Some people have been waiting more than 6 days for theirs to rebroadcast, and the broken TX are piling up much faster than they are able to process manually...
