Professional Documents
Culture Documents
Andrew Upward
Head of Market Structure
aupward@weedenco.com
203.861.7618
Note that IEX does re-price displayed orders that would lock or cross an away market upon entry, and
subsequently re-prices those orders so that they remain one tick less than the NBO (for buys) or one tick more
than the NBB (for sells). But this form of re-pricing is fundamentally different than IEXs re-pricing of hidden peg
orders. Also note that IEX offers non-pegged hidden limit orders that can only be modified or canceled by the
trader, and not by the exchange just like IEXs displayed orders.
To arrive at these distance-driven latencies, we simply converted the as the crow flies distance
between each pair of cities into time at the rate implied by IEXs speed bump (i.e. 350 microseconds per
38 miles). Depending on what kind of technology a firm is using, actual latencies could be higher or
lower than the ones weve come up with here.
As the diagram shows, the 368 s our agency broker has to wait before its order arrives at the IEX
matching engine, and the 368 s it has to wait before receiving market data from IEX, is not too
dissimilar from the latencies to and from the other big exchanges. If our broker is relying solely on feeds
from the Securities Information Processors (SIPs), it would receive IEX quote and trade updates
around the same time that it would receive updates from Bats via the SIPs (this isnt shown in the
diagram). All in all, speed bump notwithstanding, the experience of sending and modifying and canceling
displayed orders on IEX will feel very similar to the brokers experience at other exchanges.
Now lets consider an HFT firms perspective. If the firm is co-located in all three major data centers
Secaucus, Mahwah and Carteret it will have near-zero latency to all the major exchanges. There may
be scenarios or strategies for which consolidating data from the three locations is necessary, in which
case the Mahwah-to-Carteret latency (313 s using our speed bump-based conversion factor) would
serve as the firms minimum latency. Put differently, from the perspective of the firms Mahwah servers,
NYSE data will be real-time but Nasdaq and Bats data will always be slightly stale. From the perspective
of its Secaucus servers, Bats data will be real-time but NYSE and Nasdaq data will always be stale, and
from the perspective of its Carteret servers, Nasdaq data will be real-time but NYSE and Bats data will be
stale. And theres no way for the firm to have the best of all worlds, no way to patch together and see
all three feeds in real-time at the same time.
Regardless of whether the firms strategy relies on consolidated data, the latency from IEXs speed
bump could be problematic. Lets say that the HFT firm is offering stock at the same price on IEX, Nasdaq
and Bats, and its offer on Nasdaq gets lifted. Its next move is to try to raise the price of its offers on IEX
and Bats to avoid unwanted exposure. It routes a cancel/replace message to Bats in Secaucus from its
10
11
12
13
14
15
Figure 2.
These schematics are of course only representative, and are certainly not to scale. That said, we believe
that they convey an accurate understanding of the salient features of IEXs system architecture based on
the information IEX has provided in its marketing material and in its comment letters.
ADDING REAL VALUE TO IEXS HIDDEN PEG ORDERS
The speed bump is designed to prevent fast, opportunistic traders, whom well call high-frequency
traders or HFT firms for simplicity, from trading against IEX orders that are pegged to an outdated or
stale (or soon-to-be-stale) National Best Bid or Offer. Trading at stale prices represents a kind of
bait-and-switch for liquidity providers in the sense that the description of, for example, a primary peg
order type leads them to believe that theyll be capturing the entire bid-ask spread, when in fact they
may only capture part of it or in some cases none of it.
To understand how IEX protects hidden peg orders and bear in mind that all IEX peg orders are hidden
consider an HFT firm that sees that the National Best Bid (NBB) in a given stock has just ticked down.
If IEX had no speed bump, this firm might quickly route a sell order to IEX in the hopes of finding a
hidden primary peg buy order to sell to at the old NBB before IEX itself sees that theres a new NBB.
If such a buy order existed on IEX, and if the HFT firm got their sell order to IEX before the venue knew
to lower the price of its buy order, the trade would go off at the price of the old NBB. The HFT firm
would have established a short position (or closed out a long position) at a higher price, and IEXs hidden
peg buyer would have paid more for the stock than they bargained for. The following diagrams illustrate
how such a scenario, referred to as latency arbitrage, might unfold if indeed IEX did not have its speed
bump.
16
Weve brought in NYSEs data center in Mahwah, New Jersey to create a hypothetical two-exchange
market, and weve excluded the IEX POP and router as theyre not relevant in this scenario. At time zero,
NYSEs 12-cent bid is the NBB and IEX has a hidden buy order pegged to the NBB.
Figure 4.
Suddenly, at time t, a cancelation or trade on NYSE drops the NBB from 12 cents to 11 cents.
17
Almost instantaneously following the NBB change at time t, an HFT firm routes a 12-cent sell order to
IEX. Even though IEX is taking NYSEs proprietary data feed in this hypothetical example, the HFT firms
superior technology allows it to get its order to IEXs matching engine before the quote update message
arrives. IEX thinks that the NBB is still 12 cents, so it executes the sell order against its hidden peg buy
order at 12 cents. A fairer price from the buyers perspective might have been 11 cents, the true NBB at
the time of the execution.
Now lets take a look at how this scenario would have unfolded if IEXs speed bump was operational,
which of course is the case today.
Figure 6.
Notice that weve added points of presence in Secaucus for both IEX and NYSE, and that the HFT servers
that clustered around the IEX matching engine in our earlier hypothetical now cluster around the IEX
POP. At time zero, NYSEs 12-cent bid is the NBB and IEX has a hidden buy order pegged to the NBB.
18
By forcing the HFT firm co-located at NYSEs data center in Mahwah to route its sell order to IEX via its
speed bump in Secaucus, IEX ensures that the quote update coming directly from Mahwah arrives first.
As shown by the red S, the HFT firms sell order is still spinning around the coiled optical fiber when IEX
gets word from NYSE that the new NBB is 11 cents. In this scenario, because the HFT firm sent the order
with a 12-cent limit, and IEXs best bid is now 11 cents, no trade will take place on IEX.
Its worth noting that the speed bump also offers protection against slightly different strains of latency
arbitrage than the one weve diagrammed above. It prevents executions against hidden IEX orders
pegged to stale NBBO midpoint prices, and it prevents a trader who suspects that a price is about to
become stale from picking off a hidden order on IEX that is pegged to that price. The latter scenario is
probably better described as aggressive or opportunistic trading, but its still referred to by many
somewhat sloppily in our opinion as latency arbitrage.
19
Note that weve added the IEX router to the schematic (see green server icon). At time zero, both IEX
and NYSE are offering stock at 15 cents.
20
At time t, a routable 15-cent buy order for 5,000 shares arrives at the IEX matching engine and matches
against 3,000 shares on the IEX book, leaving a 2,000-share residual. Note that IEX was only showing
1,000 shares, but had 2,000 shares in hidden liquidity behind it.
Figure 11.
At time t, IEX immediately sends a trade message to the buyer whose servers are in Secaucus, and also
updates its market-data feed (m and d in the schematic). At the same time, it sees that NYSE is
offering 2,700 shares at 15 cents, so it instructs its router to route the 2,000-share residual there.
Although the instruction is given almost instantly at time t, the IEX router cant out-race the co-located
HFT firm that is reacting to the execution by routing a cancelation message to NYSE. It might be that the
HFT firm sold stock to the buyer in the 3,000-share transaction and doesnt want to risk selling more to
that buyer on NYSE, or it could be that the HFT firm is simply unnerved by the presence of what seems
like a large, aggressive buyer. In any event, by the time the IEX-routed buy order arrives at NYSE at time
21
At time zero, both IEX and NYSE are offering stock at 15 cents. Note that the speed bump is now in place
and that the HFT servers are now clustered around the IEX POP, which is the only point of entry for
order messages into the IEX matching engine (and the only point of exit for proprietary market data and
trade messages sent from Weehawken).
Figure 13.
At time t, a routable 15-cent buy order for 5,000 shares arrives at IEX and matches against 3,000 shares
on the IEX book, leaving a 2,000-share residual.
22
Still at time t, IEX immediately sends trade messages to the buyer and seller whose servers are in
Secaucus, and also updates its market-data feed. At the same time, it sees that NYSE is offering 2,700
shares at 15 cents, so it instructs its router to route the 2,000-share residual there. When the order is en
route to NYSE, no one but IEX itself knows that an execution has just taken place on IEX. The trade
messages and the proprietary data-feed updates are still traversing the speed bump en route to the
servers in the POP (m and d in the schematic), and the updates that IEX sends without delay to the
Trade Reporting Facility (not shown in the above diagram) wont be processed in time to alert the HFT
firms co-located in NYSEs Mahwah data center of the trade event. As a result, the buyer is able to buy
all 2,000 shares at NYSE at time t + 250 s, completing its 5,000-share parent order.
THE NEW ROUTING SCHEME WILL LIMIT MARKET SHARE
On February 29, IEX announced that it will change how it handles routable orders once it becomes an
exchange. Under the new scheme, once a routable order has traversed the speed bump, it will be sent
directly to the router not to the matching engine, which is where it is sent today. From there, the
router will look at the market data it is receiving from all thirteen exchanges and decide on a schedule
for the child orders it will send to IEX and away markets. In Figures 15-18 below, we illustrate how the
new system architecture will work in the same urgent liquidity demand scenario used in Figures 9-14.
23
As before, we have a simplified two-exchange market with 1,000 displayed shares offered at 15 cents on
IEX and 2,700 displayed shares offered at the same price on NYSE. Note that there is now a second
speed bump that sits between the IEX matching engine and the IEX router.
Figure 16.
At time t, a 5,000-share buy order with a 15-cent limit arrives at the IEX router. The IEX router sees
the shares offered on IEX and at NYSE. Knowing that it will take about 350 s for a child order to arrive
at the IEX matching engine and about 250 s for a child order to arrive at the NYSE matching engine, it
gives the IEX child order a head start.
24
At time t + 100 s, a child order is en route to the IEX matching engine via the speed bump (this is the
green B1), and the router releases the NYSE-bound child order (B2). Because the router only sees
3,700 displayed shares on NYSE and IEX, it has discretion over how to route the 1,300 shares that arent
spoken for. We assume that IEX will oversize both child orders 500 shares extra for the IEX child order
and 800 shares extra for the NYSE child order in the hopes of finding hidden liquidity.
Figure 18.
At time t + 350 s, both child orders arrive at their destinations. The buyer has purchased only 4,200
shares not enough to complete its 5,000-share order because hidden liquidity was found at IEX but
not at NYSE. At t + 700 s, the buyer will receive news of the execution on IEX, and 250 s later, at t +
950 s, the buyer will receive news of the execution on NYSE by way of IEX (these messages arent
shown in the diagram). Since it took 350 s to get the order to the router in the first place, users of IEXs
25
Disclosure: This publication is prepared by Weeden & Co.'s trading department, and not its research department. This publication is
for information purposes only and is based on information and data from sources considered to be reliable, but it is not guaranteed
as to accuracy and does not purport to be complete and are subject to change without notice. This publication is neither intended
nor should be considered as an offer or the solicitation of an offer to sell or buy any security or other financial product. Nothing
contained herein is intended to be, nor shall it be construed as, investment advice. Information contained herein provides
insufficient information upon which to base an investment decision. Any comments or statements made herein do not necessarily
reflect those of Weeden & Co. LP or its affiliates. 2016 Weeden & Co. LP.
26