Operational time and sessions
US workflows can span Eastern and Central operating hours. Map the instrument calendar independently from the support team calendar, especially when index references, futures and broker CFDs appear on the same screen.
Market data · deployment planning
Market Data for Brokers in United States
Plan a market-data deployment for United States around the actual source, hosting route, instrument calendars and consumer requirements.
Regional acceptance checks
A New York morning process and a Chicago-based operations team may use different local scheduling conventions. Test daylight-saving transitions and persist UTC event timestamps; do not infer a regional latency target from the country name.
Requirements to confirm
- Deployment city and hosting environment
- IANA zones: America/New_York and America/Chicago
- Per-instrument holiday calendars
- Measured route and incident ownership
Bring the proposed instrument list, source documentation and consumer workflow to a technical discussion. The agreed integration specification defines coverage, fields, usage permissions and acceptance tests.
Integration brief
A practical deployment brief for the United States
| Operating location | Identify the actual hosting city and consumer location before selecting the delivery route. |
|---|---|
| Time zones | America/New_York, America/Chicago and America/Los_Angeles. Preserve source and archive timestamps in UTC. |
| Instrument calendar | Confirm the source calendar per instrument, including holidays and session breaks. |
| Acceptance evidence | Record the route, test window, clock synchronization and responsibilities for each layer. |
Separate location from instrument policy
A US deployment can span several operating zones. Keep the timezone of each consumer separate from the calendar of the instrument it displays.
What to test
- Test a New York consumer against the agreed source route, including a daylight-saving transition and a market holiday. A US-facing application does not by itself establish a US data-source location.
- Check that incident ownership covers the sessions your consumers use.
- Compare source event time with receive time rather than reporting an unexplained latency number.