exchange-connectivity

What this skill does

# Exchange Connectivity

## Purpose
Guide the design and management of connectivity to trading venues and market data sources. Covers FIX session management, market data feed architecture, exchange protocols, trading halts and circuit breakers, symbology and reference data, and connectivity resilience. Enables building or evaluating trading infrastructure that maintains reliable, low-latency connections to exchanges, ATS venues, and market data providers.

## Layer
11 — Trading Operations (Order Lifecycle & Execution)

## Direction
both

## When to Use
- Designing or evaluating connectivity architecture to one or more trading venues (exchanges, ATS, ECNs)
- Configuring or troubleshooting FIX sessions for order routing or drop-copy feeds
- Building or integrating market data infrastructure (consolidated feeds, direct feeds, vendor feeds)
- Implementing handling logic for trading halts, circuit breakers, and LULD bands in order management or execution systems
- Mapping symbology across venues and data sources (ticker, CUSIP, ISIN, SEDOL, FIGI)
- Planning co-location, proximity hosting, or extranets for low-latency connectivity
- Designing failover, redundancy, and disaster recovery for exchange connectivity
- Evaluating regulatory requirements for market access controls (Rule 15c3-5) or Reg SCI compliance
- Building session scheduling logic for pre-market, regular session, and post-market trading windows
- Addressing sequence number gaps, message recovery, or session reset scenarios in FIX
- Normalizing market data from heterogeneous sources into a unified internal representation
- Planning CAT (Consolidated Audit Trail) reporting infrastructure for order and execution events

## Core Concepts

### Venue Connectivity Architecture
Trading venues expose electronic interfaces through which broker-dealers, market makers, and institutional participants submit orders and receive execution reports. The connectivity architecture between a firm and its execution venues is a foundational component of trading infrastructure.

**Direct Market Access (DMA):** DMA allows a firm to send orders directly to an exchange's matching engine without intermediation by another broker's order management system. The firm maintains its own FIX session (or proprietary protocol connection) with the exchange and is responsible for pre-trade risk controls. DMA is used by broker-dealers with exchange memberships and by proprietary trading firms.

**Sponsored Access:** In a sponsored access arrangement, a non-member firm routes orders to an exchange through a sponsoring broker-dealer's market participant identifier (MPID). The sponsoring broker is responsible for pre-trade risk controls under SEC Rule 15c3-5 (the Market Access Rule). Sponsored access may be "filtered" (orders pass through the sponsor's risk checks before reaching the exchange) or "unfiltered" (orders bypass the sponsor's systems and go directly to the exchange, with the sponsor relying on exchange-level risk controls). The SEC effectively prohibited unfiltered sponsored access through Rule 15c3-5, which requires the broker-dealer providing market access to implement risk management controls and supervisory procedures that are reasonably designed to prevent the entry of erroneous orders.

**FIX Protocol Connectivity:** The Financial Information eXchange (FIX) protocol is the dominant standard for order routing and execution reporting in equities, options, fixed income, and foreign exchange markets. FIX is a tag-value message format (e.g., Tag 35=D for a New Order Single, Tag 35=8 for an Execution Report). Most U.S. equity exchanges accept FIX for order entry, and FIX is the standard interface for broker-to-broker and broker-to-buy-side connectivity. FIX versions in common use include FIX 4.2 (widely supported, still in use at many venues), FIX 4.4 (added support for multi-leg instruments, allocation instructions), and FIX 5.0/FIXT 1.1 (separated transport and application layers).

**Proprietary Exchange Protocols:** Several exchanges offer proprietary binary protocols that provide lower latency than FIX due to more compact message encoding and reduced parsing overhead:
- **OUCH** — Nasdaq's order entry protocol. Binary format, supports order submission, cancellation, and replacement. Commonly used by high-frequency and low-latency participants on Nasdaq and its affiliated venues.
- **ITCH** — Nasdaq's market data dissemination protocol. Provides a full order-by-order (Level 3) view of the Nasdaq order book, including every order add, modify, cancel, and execute event. ITCH is the basis for Nasdaq's TotalView data product.
- **PITCH** — Cboe's market data protocol for the BZX, BYX, EDGX, and EDGA exchanges. Like ITCH, PITCH provides order-by-order depth-of-book data.
- **Pillar** — NYSE's integrated trading technology platform, supporting both order entry and market data across NYSE, NYSE Arca, NYSE American, and NYSE National. Pillar uses binary protocols for gateway connectivity.
- **BOE (Binary Order Entry)** — Cboe's proprietary order entry protocol, offering lower-latency order submission than FIX on Cboe equity exchanges.

**Co-location and Proximity Hosting:** Exchanges offer co-location services that allow firms to place their trading servers in the same data center as the exchange's matching engine. Co-location minimizes network latency (measured in microseconds) by reducing the physical distance between the firm's server and the exchange. Proximity hosting refers to placing servers in a data center near (but not inside) the exchange's facility, offering somewhat higher latency than co-location but often at lower cost. Major U.S. exchange data centers include the NYSE data center in Mahwah, New Jersey and the Nasdaq data center in Carteret, New Jersey.

**Connectivity Providers and Extranets:** Financial extranets are private networks that connect market participants to multiple exchanges and trading venues through a single physical connection. Major extranets include:
- **TNS (Transaction Network Services)** — Provides managed connectivity to global exchanges and trading venues.
- **IPC (now part of Atos)** — Operates the Connexus Cloud financial extranet connecting trading firms to exchanges, market data providers, and service bureaus.
- **BSO (Boldon Smart Operations)** — Offers low-latency network infrastructure for financial markets.
- **Options Technology** — Provides connectivity and managed infrastructure for trading firms.
Extranets reduce the operational burden of maintaining individual point-to-point connections to each venue but introduce a shared network dependency.

**Redundancy and Failover:** Production exchange connectivity must include redundant paths. Standard practice includes: primary and backup FIX sessions to each venue (typically on separate physical network paths), primary and secondary network connections through different extranets or carriers, cross-connect redundancy within co-location facilities, and geographic redundancy where the firm maintains a disaster recovery site capable of resuming trading.

### FIX Session Management
The FIX protocol defines a session layer that handles connection establishment, message sequencing, heartbeating, and recovery. Correct session management is essential for reliable order flow.

**Session-Level Messages:**
- **Logon (MsgType=A):** Initiates a FIX session. Contains the SenderCompID, TargetCompID, and agreed heartbeat interval. The exchange or counterparty responds with its own Logon message to confirm the session. Some venues require encryption or authentication tokens in the Logon message.
- **Logout (MsgType=5):** Gracefully terminates a FIX session. Either side may initiate. A well-behaved implementation sends Logout and waits for the counterparty's Logout response before closing the TCP connection.
- **Heartbeat (MsgType=0):** Sent at the agreed interval (typically 30 seconds) when no other messages are being exchanged. Confirms the sess