Operational time and sessions
Hong Kong consumers may join local instrument calendars with global FX and digital-asset streams. Keep per-instrument session and holiday metadata so a local closure is not applied to continuously traded crypto markets.
Market data · deployment planning
Market Data for Brokers in Hong Kong
Plan a market-data deployment for Hong Kong around the actual source, hosting route, instrument calendars and consumer requirements.
Regional acceptance checks
Test a local holiday alongside an active global instrument, then verify the display of closed and current states. Establish the actual source and hosting route before agreeing any delivery-time objective.
Requirements to confirm
- Deployment city and hosting environment
- IANA zones: Asia/Hong_Kong and Europe/London
- 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 Hong Kong
| Operating location | Identify the actual hosting city and consumer location before selecting the delivery route. |
|---|---|
| Time zones | Asia/Hong_Kong. 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
Regional applications can combine local instruments with international feeds. Keep exchange holidays, session breaks and operational maintenance as separate calendar inputs.
What to test
- Confirm the actual hosting route and permitted consumers. Test the first update after each configured source session and ensure a closed instrument is not displayed as a live executable quote.
- Check that incident ownership covers the sessions your consumers use.
- Compare source event time with receive time rather than reporting an unexplained latency number.