Skip to content

Sell One Share for 610,000 Yen. He Typed 610,000 Shares for 1 Yen.

A Mizuho trader inverted a price and a quantity. The order was for 41 times the entire company's shares. Then the system would not let him cancel it.

Episode 83 minute read

Two numbers, swapped

On December 8, 2005, a freshly listed recruitment company called J-Com began trading on the Tokyo Stock Exchange. A trader at Mizuho Securities intended to place a sell order for a client: one share at 610,000 yen. Through a keying error, the price and quantity were inverted, and the order that went out was to sell 610,000 shares at 1 yen each. The magnitude of the mistake is hard to overstate: J-Com had only about 14,500 shares in existence. The erroneous order was to sell roughly 41 times the entire company, at a fraction of a percent of the correct price.

The cancel that would not cancel

A single mistyped order should be a small story, because every trading operation has a cancel button. The trader realized the error within moments and attempted to cancel. This is where a keying mistake became a systemic failure. The Tokyo Stock Exchange's trading system contained a defect: under the specific conditions of this order, the cancellation instructions did not take effect. Mizuho reportedly attempted to cancel multiple times, and the system did not process the cancellations as intended. The order stayed live in the market, filling against eager buyers who had spotted shares priced at 1 yen. The exchange later acknowledged that a flaw in its systems had prevented the cancellation from working correctly.

Because far more shares were sold than existed, the settlement itself became impossible in the ordinary way, and the exchange and clearing organization had to devise a special cash settlement to unwind the tangle. Mizuho's losses ran to roughly 40 billion yen, on the order of 300 to 340 million dollars at the time. Mizuho sued the Tokyo Stock Exchange, and Japanese courts ultimately apportioned responsibility between the two: the trader's error was real, but the exchange's system defect, which frustrated the cancellation, was found to bear substantial responsibility. The episode also contributed to the resignation of the TSE's president the following year after a separate systems failure, and it accelerated a long modernization of the exchange's trading platform.

What it teaches

The J-Com incident is remembered as a "fat finger" story, but its enduring lesson is about the two layers of defense that failed in sequence. The first layer is input validation. An order to sell 41 times a company's outstanding shares, at a price 99.9998 percent below the intended one, is not a plausible trade; it is a detectable impossibility. Systems that move money at speed should refuse or challenge orders that violate basic sanity constraints, and the cheapest place to catch an error is before it enters the market. The second layer is the cancel path, and this is the subtler lesson. Every operator's mental safety net is the belief that a mistake can be undone, and that belief is only as real as the cancellation logic under the exact conditions of the error. A cancel button that works in testing but fails on the pathological order is worse than no cancel button, because it converts a caught mistake into an uncatchable one while the operator watches. The order was human. The disaster was the machine's refusal to let the human take it back.

Sources

6 sources

Every figure in this article traces to one of the following: the same record the episode cites.

  1. Share trade of J-COM Co., Ltd.

    Mizuho Financial Group, Inc. (archived by the Internet Archive)2005

  2. Consolidated Financial Information for the Third Quarter of Fiscal 2005

    Mizuho Financial Group, Inc. (archived by the Internet Archive)2006

01Zof Console

Eine Oberfläche für Körperhaltung, Operationen und alles, was als nächstes Aufmerksamkeit erfordert.

Das authentifizierte Zuhause, das Engineering-, QA- und SRE-Teams jeden Tag öffnen: Qualitätshaltung, laufende Abläufe, Abdeckung nach Modul und was als Nächstes Aufmerksamkeit braucht.

OPERATIVE KPIs

  • Läufe
  • Deckung
  • Risiko

Lebe in jeder Umgebung, in die du versendest.

ARBEITSRÜCKEN

  • Spezifikationen
  • Tests
  • Zeitpläne

Von der Spezifikation bis zur geplanten Regression.

GELÄNDER

  • RBAC
  • SSO
  • Audit

Jede Handlung, die einem namentlich genannten Menschen zuzuschreiben ist.

LIVE/console
Zof AI Home Command Center zeigt 12 Läufe mit 94 % Erfolg, 3 offene kritische Probleme, 84 % Abdeckung, vier Modul-Rückverfolgbarkeitsbalken, die Spezifikationspipeline, bevorstehende Zeitpläne und empfohlene nächste Aktionen mit einer Seitenleiste für aktive Läufe.
Startseite · Checkout-Service · Inszenierung · Live vom Produkt erfasst.
He Typed 610,000 Shares for 1 Yen | Zof AI