A PoP (Point of Presence) is a CoinAPI ingestion site, located in major financial data centers (e.g., NY4, LD4, TY8), where exchange market data is first received, timestamped, and normalized. Each PoP maintains persistent, real-time connectivity to supported exchanges and assigns the time_coinapi timestamp to every event. PoPs ensure ultra-low-latency ingestion, high availability, and accurate microstructure sequencing across all datasets.
A PoP is a dedicated CoinAPI infrastructure node - typically colocated in global financial hubs - responsible for:
Every event ingested at a PoP is labeled with:
id_site_coinapi – the PoP’s UUIDtime_coinapi – the exact moment the PoP received the updateThese identifiers make data lineage transparent and verifiable.
PoPs exist to give traders and developers:
Events enter CoinAPI’s infrastructure from the nearest PoP, reducing the physical distance between exchange → ingestion.
time_coinapi reflects the real arrival time of each update, which is crucial for:
If a PoP experiences network issues, CoinAPI automatically reroutes ingestion through another available PoP without data loss.
Because every event is tied to a PoP UUID and ingest timestamp, researchers can reproduce market conditions precisely from a regional vantage point.
CoinAPI maintains PoPs in major low-latency financial colocation facilities, including (examples):
Additional PoPs across North America, Europe, and APAC provide:
PoP locations are not published publicly for security reasons, but CoinAPI provides UUID→location mappings on request for:
time_coinapi)id_site_coinapi)Because PoPs are region-specific, the PoP that receives the data influences the measured latency profile.
Comparing time_exchange and time_coinapi reveals real-world latency and exchange performance.
Replay historical events as they were seen from a particular PoP.
Detect PoP failover or routing shifts by examining changes in id_site_coinapi.
Model strategy performance using true arrival times rather than synthetic timestamps.
Provide ingest-level data lineage for regulated use cases.
id_site_coinapiEach PoP is associated with one stable UUID.
The UUID never changes and always maps to the same ingestion site.
This enables:
If needed, CoinAPI can export a mapping from the UUID to the PoP’s physical location.
id_site_coinapi UUID.time_coinapi is assigned at the PoP the moment an update arrives.