Geographic locations and the Latency
We continuously expand our data centers, but currently, the API endpoints are located in:
- AWS us-east-1 - AWS eu-central-1 - AWS eu-west-1 - USA Chicago (AS7922, AS812, AS10796) - USA New York (AS7922, AS812, AS10796) - UK London (AS2856, AS13285, AS5089) - Poland Warsaw (AS174) - Asia Tokyo (AS17676, AS2516, AS4713)
Historical data delivered using the REST API (all /history and several /latest endpoints) and the flat files are generated in the separate process where we replay all the markets (seen from different locations) and create a single data feed prone to issues related to specific geographic areas like network issues etc.
Real-time data delivered using the REST (all /current and several /latest endpoints), WebSocket, and the FIX API originates from the specific site where the customer was connected. On the Enterprise Plan, it's possible to have direct access to the sites or set up AWS VPC Peering in that case latency between our infrastructure and the customer is below one millisecond. If the connection was established to the public endpoint, then it's routed using the GeoDNS to the closest site; latency then depends on the distance between the customer and the site where the connection was routed [~20ms].