Gox has let us understand they have run into problems related to overloading the computer systems at the second biggest bank in Japan
Do you have a reference for
computer systems? My impression is that all irregularities which make manual work for the bank is to blame. E.g. wrong names or other information on accounts, or other banks returning or refusing to process transfers, or requesting return of transfers. I'm surprised to hear it was the computer systems.
I'm fighting these issues right now and am in fact up rather than still snoozing to re-submit some information in an attempt to get a wire transfer queued. The rejection of my last attempt was rejected for use of the wrong name. Funny coincidence.
Yesterday there was an option for 'intl wire' and 'intl wire to US'. I choose the latter. It would not allow me input SWIFT info for lack of ABA. When I instead selected to input ABA and used the ABA my banker told me to use for wires, Mt. Gox's system resolved this to a bank name (a wing of Wells Fargo.) My 'withdraw method' was rejected because of this string it seems rather than my real name (which I am certain I DID use where it was clear that MY name was being requested.)
Today there is no longer a 'wire to US' option and I was able to add a SWIFT-based withdraw method. It is under 'verification' at the moment.
I am sure that there are plenty of mistakes made by users due to the complex nature of such efforts, and they slow things down, but I am also sure that the various UI's employed by Mt. Gox are under development and are in a state of flux, and that they have bugs, inconsistencies, and documentation deficiencies which also conspire to create delays.
So far in my experience with Mt. Gox's verification and wire withdraw framework I will say that human interaction has been more necessary than either of us would like, but has been admirably low latency especially considering the time-zone differences.