# Developer Q&A: Monitoring global API latency with chronark

DevFeed: [Developer Q&A: Monitoring global API latency with chronark](<https://devfeed.tech/articles/developer-q-a-monitoring-global-api-latency-with-chronark-18474.md>)

Original publisher: [Read original article](<https://www.tinybird.co/blog/dev-qa-global-api-latency-chronark>)

Author: Tinybird

Published: 2023-03-30T00:00:00Z

Content type: article

Language: en

Sources: [Tinybird](<https://devfeed.tech/sources/tinybird.md>)

Topics: [Latency](<https://devfeed.tech/topics/latency.md>), [API](<https://devfeed.tech/topics/api.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [developer](<https://devfeed.tech/tags/developer.md>), [i-built-this](<https://devfeed.tech/tags/i-built-this.md>), [latency](<https://devfeed.tech/tags/latency.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>)

## AI overview

A developer Q&A about Chronark's architecture for monitoring global API latency, including a stated goal of keeping latency below 50 milliseconds.

## Source excerpt

Chronark needed global latency under 50ms. Most said it was impossible. Here's the architecture that proved them wrong.