Skip to Content
logologo
AI Incident Database
Open TwitterOpen RSS FeedOpen FacebookOpen LinkedInOpen GitHub
Open Menu
Discover
Submit
  • Welcome to the AIID
  • Discover Incidents
  • Spatial View
  • Table View
  • List view
  • Entities
  • Taxonomies
  • Submit Incident Reports
  • Submission Leaderboard
  • Blog
  • AI News Digest
  • Risk Checklists
  • Random Incident
  • Sign Up
Collapse
Discover
Submit
  • Welcome to the AIID
  • Discover Incidents
  • Spatial View
  • Table View
  • List view
  • Entities
  • Taxonomies
  • Submit Incident Reports
  • Submission Leaderboard
  • Blog
  • AI News Digest
  • Risk Checklists
  • Random Incident
  • Sign Up
Collapse

Report 411

Associated Incidents

Incident 2830 Report
2010 Market Flash Crash

Loading...
The 2010 Flash Crash: What Caused It and How to Prevent the Next One
aol.com · 2010

Fragmentation among stock exchanges . In 1987, when we had the crash that took 22.6% off the Dow, trading execution was much slower and more concentrated. Back then, 90% of stock trading occurred on the New York Stock Exchange (NYSE). In 2004, Regulation NMS changed all that -- encouraging the emergence of new electronic exchanges like BATS and DirectEdge. By 2010, a mere 15% to 17% of all NYSE trades were controlled by the NYSE (the new electronic exchanges controlled the rest).

. In 1987, when we had the crash that took 22.6% off the Dow, trading execution was much slower and more concentrated. Back then, 90% of stock trading occurred on the New York Stock Exchange (NYSE). In 2004, Regulation NMS changed all that -- encouraging the emergence of new electronic exchanges like BATS and DirectEdge. By 2010, a mere 15% to 17% of all NYSE trades were controlled by the NYSE (the new electronic exchanges controlled the rest). Different ways of trading with exchanges that go into so-called slow mode . These new exchanges had different ways of handling big ups and downs in the market. The NYSE preserved a way to put people in charge -- and take control away from the computers -- in the event of a big percent change in a stock's price. Putting a person in charge of trading a stock was called slow-mode. Some of the new electronic exchanges had rules that caused them to stop trading with exchanges that went into slow mode. This led different exchanges to quote very different prices for a specific stock.

. These new exchanges had different ways of handling big ups and downs in the market. The NYSE preserved a way to put people in charge -- and take control away from the computers -- in the event of a big percent change in a stock's price. Putting a person in charge of trading a stock was called slow-mode. Some of the new electronic exchanges had rules that caused them to stop trading with exchanges that went into slow mode. This led different exchanges to quote very different prices for a specific stock. Inconsistent rules for handling bad price information. These different prices caused some market participants to lose confidence in the price information they were getting from the markets. And these participants' computers were programmed to shut down and stop trading in the event that they received bad or mis-information.

Agree on a standard definition of an erroneous trade . As noted above, not all participants agree on what constitutes an erroneous trade. Some would argue that if there is no demand for a stock at $40 and the only way to execute the sale is to cut the price to six cents, that's fine. Others would call that an erroneous trade. iShares believes that all exchanges must agree on a standard definition to stop the next flash crash. And they must then agree on how to cancel and communicate such an erroneous trade.

. As noted above, not all participants agree on what constitutes an erroneous trade. Some would argue that if there is no demand for a stock at $40 and the only way to execute the sale is to cut the price to six cents, that's fine. Others would call that an erroneous trade. iShares believes that all exchanges must agree on a standard definition to stop the next flash crash. And they must then agree on how to cancel and communicate such an erroneous trade. Create standard ways for exchanges to deal with an exchange that goes into slow mode . During the flash crash, some electronic exchanges refused to deal with an exchange that decided to go into slow mode. Instead, they went on to trade with other exchanges that continued to operate in regular mode. iShares believes that all exchanges need to have standard rules for ignoring what Clements called "a pool of liquidity," such as the NYSE or any other exchange that goes into slow mode.

. During the flash crash, some electronic exchanges refused to deal with an exchange that decided to go into slow mode. Instead, they went on to trade with other exchanges that continued to operate in regular mode. iShares believes that all exchanges need to have standard rules for ignoring what Clements called "a pool of liquidity," such as the NYSE or any other exchange that goes into slow mode. Boost transparency of market makers' obligations and incentives. Finally,iShares wants the SEC to define the obligations of so-called Designated Market Makers (DMMs), such as the people on the NYSE who seek to create an orderly market in stocks like Accenture. Specifically, iShares wants to make it clear that DMMs have an obligation to keep a stock's price from collapsing and create incentives for them to step in and buy when there are no other buyers to keep the price from collapsing.

Remember the flash crash? That was the 20 minutes on May 6, 2010 when the Dow lost almost 1,000 points before partially recovering. Most investors have forgotten about it. But not iShares, the Blackrock ( BLK ) subsidiary that accounts for 50% of trading in exchange-traded funds (ETFs). iShares

Read the Source

Research

  • Defining an “AI Incident”
  • Defining an “AI Incident Response”
  • Database Roadmap
  • Related Work
  • Download Complete Database

Project and Community

  • About
  • Contact and Follow
  • Apps and Summaries
  • Editor’s Guide

Incidents

  • All Incidents in List Form
  • Flagged Incidents
  • Submission Queue
  • Classifications View
  • Taxonomies

2024 - AI Incident Database

  • Terms of use
  • Privacy Policy
  • Open twitterOpen githubOpen rssOpen facebookOpen linkedin
  • e1b50cd