Operational time and sessions
London-based workflows often need to align FX activity with US sessions. Use separate IANA zones for operational schedules so the weeks when daylight-saving changes differ do not shift jobs unintentionally.
Market data · deployment planning
Market Data for Brokers in United Kingdom
Plan a market-data deployment for United Kingdom around the actual source, hosting route, instrument calendars and consumer requirements.
Regional acceptance checks
Test a London session transition and the handover to US coverage. Record the actual hosting and source locations before measuring network delay; a UK-focused page does not establish a UK data centre or exchange entitlement.
Requirements to confirm
- Deployment city and hosting environment
- IANA zones: Europe/London and America/New_York
- 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 Kingdom
| Operating location | Identify the actual hosting city and consumer location before selecting the delivery route. |
|---|---|
| Time zones | Europe/London. 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
London local time changes seasonally. Keep the original source event time in UTC and apply London time only where the operating workflow requires it.
What to test
- Test the weeks when UK and North American clock changes are not aligned. Document the source calendar rather than shifting every instrument session with the support team clock.
- Check that incident ownership covers the sessions your consumers use.
- Compare source event time with receive time rather than reporting an unexplained latency number.