4 ms·
>The problem could have been caused by a strange hardware defect, a rare bug in a library, etc. Or competition, a disgruntled employee, etc. Just speculating b
by moonchrome 15y ago
>The problem could have been caused by a strange hardware defect, a rare bug in a library, etc.
Or competition, a disgruntled employee, etc. Just speculating but IMO it's a pretty big coincidence that it failed exactly when they did the IPO.
- bdr 15y agoYes, not to mention the two stocks it failed on.
- rabidsnail 15y agoTheir IPO might have caused a spike in trading volume on their exchange, which might have triggered the bug.
- apaprocki 15y agoCheck the graph: http://www.nanex.net/aqck/3079-2.jpg http://www.nanex.net/aqck/3079-2.jpg It happened in less than a second.
- jack12 15y agoThe NYTimes article says that the initial offering of BATS "would have been the first company to be listed as well as traded on the exchange", and the post mortem currently at the top of http://www.batstrading.com/alerts/ http://www.batstrading.com/alerts/ (no direct link that I can see) says that the A-BFZZZ shard "encountered a software bug related to IPO auctions". I read that to mean that this is the first time they've ever used their IPO-related code in production and it failed badly. So it sounds like it was the normal sort of bug, in their own code, and their own IPO directly triggered the bug.