Independent, measured latency & uptime for ~45 AI inference APIs, by region. JSON API + MCP server. Data CC-BY-4.0.
claude mcp add llm-latency-tracker -- python -m -r{
"mcpServers": {
"llm-latency-tracker": {
"command": "python",
"args": ["-m", "-r"],
"env": {
"BASE_URL": "<base_url>"
}
}
}
}BASE_URLResumen de MCP Servers
# LLM Latency Tracker
**Independent, provider-neutral latency & uptime for AI inference APIs — measured, not scraped.**
🌐 **Live: [llmlatency.dev](https://llmlatency.dev)** · 📊 [JSON API](https://llmlatency.dev/api/rankings.json) · 🤖 [MCP server](https://llmlatency.dev/mcp) · 🗓️ [Deprecation calendar](https://llmlatency.dev/deprecations)
   
Most "AI API latency" numbers come from the providers themselves, or from a benchmark run once and never updated. This project **measures** it continuously, from multiple regions, and publishes the result as an open dataset.
- **Edge latency** — full DNS → TCP → TLS → time-to-first-byte, measured with the Python standard library (no API key required).
- **Inference latency** — real time-to-first-token via a streaming request (optional, needs a provider key).
- **Uptime** — success rate per provider, per region.
- **Regions** — Europe (Germany), US (Central), Asia (Tokyo), South America (São Paulo). More welcome.
- **~45 providers** — OpenAI, Anthropic, Google, Mistral, DeepSeek, xAI, Groq, Together, Fireworks, Cerebras, OpenRouter, Perplexity, plus Chinese models (GLM/Zhipu, Kimi/Moonshot, Qwen, MiniMax) and many more.
- **Deprecation calendar** — upcoming model retirements + migration targets, verified from official provider docs.
The site is a self-updating static site (Cloudflare Pages). The value isn't the code — it's the continuously-accumulated, distributed measurement archive. The code is open so the methodology is transparent.
## For developers
```bash
# All regions, provider rankings for the last 24h — measured latency + uptime:
curl https://llmlatency.dev/api/rankings.json
```
- **JSON API:** [`/api/rankings.json`](https://llmlatency.dev/api/rankings.json) · **OpenAPI:** [`/openapi.json`](https://llmlatency.dev/openapi.json)
- **Any page as Markdown:** send `Accept: text/markdown` to any page URL, or append `.md`.
- **For LLM ingestion:** [`/llms.txt`](https://llmlatency.dev/llms.txt) (index) and [`/llms-full.txt`](https://llmlatency.dev/llms-full.txt) (full corpus).
- **License:** data is **CC-BY-4.0** — free to use with attribution.
## For AI agents
There's a real **MCP server** (Streamable HTTP) exposing a `get_ai_api_latency` tool backed by the live data:
```bash
curl -X POST https://llmlatency.dev/mcp \
-H 'Content-Type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call",
"params":{"name":"get_ai_api_latency","arguments":{"region":"eu-hetzner"}}}'
```
Also available: an [MCP Server Card](https://llmlatency.dev/.well-known/mcp/server-card.json) (`/.well-known/mcp/server-card.json`), a browser **WebMCP** tool, an [API catalog](https://llmlatency.dev/.well-known/api-catalog) (RFC 9727) and an [Agent Skills index](https://llmlatency.dev/.well-known/agent-skills/index.json). Regions: `eu-hetzner`, `us-central`, `ap-tokyo`, `sa-east` (omit for all).
## How it works
```
config.py — registry of providers + this node's REGION (env)
probe.py — network probe (DNS→TCP→TLS→TTFB, stdlib, no key) + inference probe (TTFT, needs key)
run.py — one probe cycle across all providers (run on a schedule)
db.py — SQLite time-series (the accumulated measurement archive)
aggregate.py — measurements → p50 / p95 / uptime rankings per region & provider
sitegen.py — rankings → static site (JSON API, OpenAPI, llms.txt, schema.org, MCP surface)
ingest.py — central endpoint that collects measurements from remote probe nodes
ship.py — probe node → central node shipper (watermark-based, never loses data on outage)
deprecations.py — model deprecation/migration calendar (only verified, sourced entries)
```
Each probe node runs with its own `REGION`, measures every provider, and writes to the time-series. For multi-region, remote nodes ship their measurements to a central node that aggregates and builds the site.
## Run it yourself (no keys needed)
```bash
git clone https://github.com/mazamaka/llm-latency-tracker
cd llm-latency-tracker
REGION=local python3 run.py # take edge-latency measurements
python3 aggregate.py --region local # see the ranking from this location
```
Runs on plain Python 3.12+ (standard library). `httpx` / `loguru` are optional.
**Inference probes (real TTFT):**
```bash
cp .env.example .env # add keys for the providers you want to measure
pip install -r requirements.txt
REGION=local python3 run.py
python3 aggregate.py --region local --type inference
```
**Build the site locally:**
```bash
BASE_URL=https://example.com python3 sitegen.py # → ./site/
python3 -m pytest -q # tests
```
See [`deploy/`](deploy/) for a container + a generic multi-region deployment guide.
## Contributing
Especially welcome:
- **New providers** — add a `Provider(...)` entry in [`config.py`](config.py) (host + public models endpoint is enough for edge probes).
- **New regions** — spin up a probe node in a new location and ship to a central node.
- **Fixes & tests** — CI runs `pytest` + `ruff` on every push.
See **[CONTRIBUTING.md](CONTRIBUTING.md)** for dev setup, how to add a provider/region, and PR guidelines. Please keep the project's principle: **measured, not scraped, and honest about the dataset's age.**
## License
- **Code:** [MIT](LICENSE)
- **Data** (rankings, API output): **CC-BY-4.0** — attribute [llmlatency.dev](https://llmlatency.dev).
Lo que la gente pregunta sobre llm-latency-tracker
¿Qué es mazamaka/llm-latency-tracker?
+
mazamaka/llm-latency-tracker es mcp servers para el ecosistema de Claude AI. Independent, measured latency & uptime for ~45 AI inference APIs, by region. JSON API + MCP server. Data CC-BY-4.0. Tiene 1 estrellas en GitHub y se actualizó por última vez today.
¿Cómo se instala llm-latency-tracker?
+
Puedes instalar llm-latency-tracker clonando el repositorio (https://github.com/mazamaka/llm-latency-tracker) o siguiendo las instrucciones del README en GitHub. ClaudeWave también te ofrece bloques de instalación rápida en esta misma página.
¿Es seguro usar mazamaka/llm-latency-tracker?
+
mazamaka/llm-latency-tracker aún no ha sido auditado por nuestro agente de seguridad. Revisa el repositorio original en GitHub antes de usarlo en producción.
¿Quién mantiene mazamaka/llm-latency-tracker?
+
mazamaka/llm-latency-tracker es mantenido por mazamaka. La última actividad registrada en GitHub es de today, con 0 issues abiertos.
¿Hay alternativas a llm-latency-tracker?
+
Sí. En ClaudeWave puedes explorar mcp servers similares en /categories/mcp, ordenados por popularidad o actividad reciente.
Despliega llm-latency-tracker en tu cloud
Lleva este repo a producción en minutos. Cada plataforma genera su propio entorno con variables de entorno editables.
¿Mantienes este repo? Añade un badge a tu README
Pega el badge en tu README de GitHub para mostrar que está auditado por ClaudeWave. Cada badge enlaza de vuelta a esta página y muestra el Trust Score actual.
[](https://claudewave.com/repo/mazamaka-llm-latency-tracker)<a href="https://claudewave.com/repo/mazamaka-llm-latency-tracker"><img src="https://claudewave.com/api/badge/mazamaka-llm-latency-tracker" alt="Featured on ClaudeWave: mazamaka/llm-latency-tracker" width="320" height="64" /></a>Más MCP Servers
Fair-code workflow automation platform with native AI capabilities. Combine visual building with custom code, self-host or cloud, 400+ integrations.
User-friendly AI Interface (Supports Ollama, OpenAI API, ...)
An open-source AI agent that brings the power of Gemini directly into your terminal.
The fastest path to AI-powered full stack observability, even for lean teams.
Real-time global intelligence dashboard. AI-powered news aggregation, geopolitical monitoring, and infrastructure tracking in a unified situational awareness interface
🕷️ An adaptive Web Scraping framework that handles everything from a single request to a full-scale crawl!