Bitcoin Forum

Economy => Service Discussion => Topic started by: Fizzgig on August 09, 2012, 12:43:05 PM



Title: MtGox Sell Orders Lacking
Post by: Fizzgig on August 09, 2012, 12:43:05 PM
No one is selling bitcoin on MtGox, price explosion imminent or glitch? Is there a shortage of bitcoin?

Edit/Update: It was just a bug, nothing to see here, business as usual.


Title: Re: MtGox Sell Orders Lacking
Post by: Kluge on August 09, 2012, 12:48:59 PM
MtGox shows a high price of $1b, so I think it's safe to say there's been a serious bug exploit at Gox.


Title: Re: MtGox Sell Orders Lacking
Post by: BitcoinINV on August 09, 2012, 01:10:00 PM
Just incase anyone misses it lol
http://img684.imageshack.us/img684/8312/screenhunter03aug090908.jpg


Title: Re: MtGox Sell Orders Lacking
Post by: Mt.Gox_Support_Natalie on August 09, 2012, 02:56:27 PM
Hello,

Please find further explanation of this issue below.


Hello Mt.Gox Users,

Trading was unavailable for a short period of time today.  There were invalid trades taking place as well as trade orders that could not be cancelled.  Therefore we had to halt the trading engine and consequently, most ask orders were cancelled.

However, we have resolved this issue and trading has now resumed. Invalid trades have been cancelled and trade orders can now be cancelled. Users who have had their ask orders cancelled are kindly requested to place their orders again.

We apologize for the inconvenience caused and we will make every effort to prevent this from happening again in the future.  Thank you for your continued support to Mt.Gox.

UPDATE:  After investigating, we found out that the issue is likely due to an old piece of code in the trade engine that checks for bid/ask cross (i.e. negative spread). This piece of code would check for bids and asks differences, but did not make sure that both were in the same currency.

To prevent this bug issue from recurring, we have placed some extra checks to halt trading automatically should a similar issue happen again. Thank you once again for your kind understanding in this matter.

Source: https://support.mtgox.com/entries/21845378-resolved-outage-35046-trading-unavailable

We would like to apologize for the inconvenience caused and if your problem persists, please feel free to contact us at the Support Page.


Title: Re: MtGox Sell Orders Lacking
Post by: Drifter on August 09, 2012, 02:59:09 PM
Happy to hear it wasn't something more serious.


Title: Re: MtGox Sell Orders Lacking
Post by: bb113 on August 09, 2012, 03:04:37 PM
Code:
*Resolved* [OUTAGE-#35046 ] Trading Unavailable

Is this really the 35 thousandth outage? That would be 32 a day for the last 3 years. It just looks weird...


Title: Re: MtGox Sell Orders Lacking
Post by: Hawkix on August 09, 2012, 03:22:19 PM
Code:
*Resolved* [OUTAGE-#35046 ] Trading Unavailable

Is this really the 35 thousandth outage? That would be 32 a day for the last 3 years. It just looks weird...

No, I guess its just up to the MtGox quality standards.

Why the heck you simply do not rewrite the trading matching engine? Instead of silly "HALT" check.


Title: Re: MtGox Sell Orders Lacking
Post by: Mt.Gox_Support_Natalie on August 09, 2012, 03:31:01 PM
Code:
*Resolved* [OUTAGE-#35046 ] Trading Unavailable

Is this really the 35 thousandth outage? That would be 32 a day for the last 3 years. It just looks weird...

Hello,

Sorry for the confusion.  The number is the number of the ticket that was created in Zendesk for the Outage and not the 35046th Outage.  For every ticket that is submitted to us at Zendesk, there is a number for the Incident/Question attached to it. 


Title: Re: MtGox Sell Orders Lacking
Post by: Mt.Gox_Support_Natalie on August 09, 2012, 03:32:36 PM
Code:
*Resolved* [OUTAGE-#35046 ] Trading Unavailable

Is this really the 35 thousandth outage? That would be 32 a day for the last 3 years. It just looks weird...

No, I guess its just up to the MtGox quality standards.

Why the heck you simply do not rewrite the trading matching engine? Instead of silly "HALT" check.

Hello,

It appears that some new trade engine features that were rolled into production earlier today caused this bug to become possible. We have now found the exact cause and resolved this bug.
We now are 100% confident that today's problem was due to a technical glitch and we would like to assure that it was not caused by any malicious attempts.