LLM Latency Tracker
Measured latency, time to first token and uptime for ~45 AI inference APIs, by region.
ماذا يمكنك أن تفعل مع LLM Latency Tracker؟
- 🌍 Regional measurements — compare provider response times and availability from distributed probe nodes.
- ⏱️ Two probe types — network time to first byte (TTFB) and optional inference time to first token (TTFT).
- 📈 Open dataset — daily rankings, historical snapshots and regional p50 / p95 statistics.
- 🤖 Agent access — JSON API, MCP, Markdown pages and an
llms.txtindex. - 🗓️ Model lifecycle — a deprecation calendar with links to provider announcements.
التثبيت
أضف هذا إلى إعدادات MCP في عميلك (Claude Desktop: claude_desktop_config.json، وCursor: .cursor/mcp.json، ويستخدم VS Code وغيره الصيغة نفسها «mcpServers»).
claude mcp add --transport http llm-latency-tracker 'https://llmlatency.dev/mcp'
{
"mcpServers": {
"llm-latency-tracker": {
"type": "http",
"url": "https://llmlatency.dev/mcp"
}
}
}
التوثيق
مأخوذ من ملف README للمشروع على GitHub ويُحدَّث أسبوعيًا. تفتح الروابط على GitHub.
📊 LLM Latency Tracker
Measure AI API latency and uptime across regions, and publish the results as open data.
🌐 Live rankings · JSON API · MCP endpoint
⚡ What it does
- 🌍 Regional measurements — compare provider response times and availability from distributed probe nodes.
- ⏱️ Two probe types — network time to first byte (TTFB) and optional inference time to first token (TTFT).
- 📈 Open dataset — daily rankings, historical snapshots and regional p50 / p95 statistics.
- 🤖 Agent access — JSON API, MCP, Markdown pages and an
llms.txtindex. - 🗓️ Model lifecycle — a deprecation calendar with links to provider announcements.
🔧 Built for measurement
- Python standard-library core for edge probes; provider keys are needed for inference probes.
- SQLite storage and regional aggregation, with remote nodes shipping measurements to a central node.
- Static publishing for the website and JSON datasets.
- CI checks for tests and linting; published snapshots include their measurement date.
Reading the results: edge TTFB measures network/API responsiveness, not model generation speed. Compare it separately from inference TTFT; results depend on region, probe type and time window.
🚀 Quick start
Use the public data without installing anything:
curl https://llmlatency.dev/api/rankings.json
Or run edge probes locally with Python 3.12+:
git clone https://github.com/mazamaka/llm-latency-tracker.git
cd llm-latency-tracker
REGION=local python3 run.py
python3 aggregate.py --region local
For a local stdio MCP server over the published API (stdlib only, no keys):
python3 mcp_server.py
Tools: get_ai_api_latency (provider leaderboard per region), get_provider_latency (one provider across regions), get_model_deprecations (model shutdown calendar), get_coding_agent_health (Claude Code / Codex speed and accuracy drift). All read-only.
Inference probes, API access & site generation → · Deployment →
🧪 Contributing
Add a provider, bring a new probe region, or improve the measurement code. See CONTRIBUTING.md for setup and checks.
Python · SQLite · JSON API · MCP · Cloudflare Pages
Code: MIT · Data: CC-BY-4.0, with attribution to llmlatency.dev.
📈 Latest daily snapshot
Daily snapshot — 2026-10-26
Measured latency across 46 AI inference providers in 4 regions. Method: distributed edge (DNS→TCP→TLS→TTFB) + inference (TTFT) probes, last 24h. License: CC-BY-4.0.
| Region | Fastest provider (p50) | p50 | p95 | Uptime |
|---|---|---|---|---|
| Asia (Tokyo) | fireworks | 24 ms | 99 ms | 100% |
| Europe (Germany) | openrouter | 98 ms | 201 ms | 100% |
| South America (São Paulo) | writer | 56 ms | 85 ms | 100% |
| US (Central) | fireworks | 28 ms | 77 ms | 100% |
- Full dataset:
data/rankings/2026-10-26.json(latest) - Citable archive (DOI):
10.5281/zenodo.23388429— daily aggregates, CC-BY-4.0 - Hugging Face dataset: https://huggingface.co/datasets/llmlatency/llm-latency-tracker
- Kaggle dataset: https://www.kaggle.com/datasets/llmlatency/llm-latency-tracker
- Archived in Software Heritage:
swh:1:snp:2778cbabd72a70a629ee35fbd5ac536d1ccb7a9a - Python client: https://pypi.org/project/llmlatency/
- Live rankings and methodology: https://llmlatency.dev
- Machine-readable API: https://llmlatency.dev/api/rankings.json
- Model deprecation calendar: https://llmlatency.dev/deprecations
Snapshot generated 2026-10-26T07:24:17Z — this table is regenerated daily.
الأسئلة الشائعة
ما هو LLM Latency Tracker؟
Measured latency, time to first token and uptime for ~45 AI inference APIs, by region.
كيف أثبّت LLM Latency Tracker؟
يعمل كخادم بعيد. في Claude Code: claude mcp add --transport http llm-latency-tracker 'https://llmlatency.dev/mcp'. وفي العملاء الآخرين، الصق إعداد JSON من هذه الصفحة في إعدادات MCP الخاصة بهم.
هل يحتاج LLM Latency Tracker إلى مفتاح API؟
لا يذكر إدراجه في السجل أي مفتاح أو سر إلزامي. قد تتطلب بعض الميزات حسابًا لدى الخدمة التي يتصل بها.
هل LLM Latency Tracker مفتوح المصدر؟
نعم. شيفرته متاحة على GitHub بترخيص MIT.
من يصون LLM Latency Tracker؟
ينشره mazamaka. يدرجه AI.tn لكنه لا يصونه ولا يوصي به.
من سجل MCP الرسمي. الإدراج ليس توصية: راجع شيفرة الخادم وصلاحياته قبل منحه الوصول إلى بياناتك.