llmlatency
Measured latency and uptime for AI inference APIs, as a small Python client for the open dataset published at llmlatency.dev.
Probes run every five minutes from four regions and are never routed through a gateway or an aggregator, so the numbers describe the providers themselves rather than a proxy in front of them.
- Network probe — DNS → TCP → TLS → time to first byte.
- Inference probe — time to first token on a real completion request.
These are different quantities, an order of magnitude apart, and this library never mixes them in one ranking.
What the data answers
Every question below has a page on llmlatency.dev, rebuilt automatically from the probes:
- Which AI API has the best uptime? — AI provider uptime comparison: observed availability of OpenAI, Anthropic, Google and 40+ other APIs from four regions, with the worst region shown next to the average.
- Is the OpenAI, Claude or Gemini API down right now? — live status per provider: OpenAI, Anthropic, Google Gemini.
- What failed, and when? — incident log. An outage is attributed to a provider only when it failed from two or more regions at once and no other provider was failing in the same minutes.
- Which LLM API has the lowest time to first token? — measured TTFT vs TTFB.
- When is a model retired, and what replaces it? — AI model deprecation calendar: OpenAI, Anthropic, Google, Mistral and Azure retirement dates, each row linked to the provider's own announcement.
- Fastest AI API from my region — Europe, US, Asia, South America.
Snapshot: 18 October 2026
Taken from those pages on that day. They change every few minutes; the links always show current figures.
- 46 providers probed from 4 regions, 52,897 probes in the preceding 24 hours.
- 33 of the 46 providers answered every probe from every region.
- Lowest measured time to first token: 440 ms (typesafe,
jev-1.13.0, from São Paulo). This is not a provider ranking — each provider answers on a different model, and model size drives TTFT more than the provider does. - Next retirement date: 2026-10-23 — 28 OpenAI models and fine-tunes, among
them
gpt-4,gpt-4-turbo,gpt-3.5-turbo,o1-2024-12-17andgpt-image-1.
Install
pip install llmlatency
No dependencies — standard library only.
Use it from Python
import llmlatency
llmlatency.regions()
# ['ap-tokyo', 'eu-hetzner', 'sa-east', 'us-central']
llmlatency.fastest("eu-hetzner")
# {'rank': 1, 'provider': 'nscale', 'p50_ms': 99, 'p95_ms': 203,
# 'uptime_pct': 100, 'samples': 289}
for row in llmlatency.ranking("us-central")[:3]:
print(row["rank"], row["provider"], row["p50_ms"], "ms")
llmlatency.provider("anthropic") # one provider across every region
llmlatency.generated_at() # snapshot timestamp, ISO-8601 UTC
Fetch once and pass the snapshot around if you make several queries:
data = llmlatency.fetch()
fast = {r: llmlatency.fastest(r, data=data) for r in llmlatency.regions(data)}
Use it from the shell
llmlatency fastest # fastest provider in every region
llmlatency ranking --region eu-hetzner --top 5
llmlatency provider openai
llmlatency fastest --probe inference --json
Data, methodology, licence
- Live rankings: https://llmlatency.dev
- Methodology: https://llmlatency.dev/methodology
- Machine-readable snapshot: https://llmlatency.dev/api/rankings.json
- Citable archive with a DOI: https://doi.org/10.5281/zenodo.21954788
- Daily snapshots in git: https://github.com/mazamaka/llm-latency-tracker
The dataset is CC-BY-4.0; this client library is MIT.
Limitations, stated up front. Vantage points are cloud data centres, not consumer networks, so absolute values are lower than an end user would see — the comparison between providers is the meaningful part. Provider coverage changes over time as APIs appear and shut down.
Metadata
Release files for llmlatency 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| llmlatency-0.1.1.tar.gz | 12.7 kB | Without provenance | Details for llmlatency-0.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| llmlatency-0.1.1-py3-none-any.whl | Python 3 | none | any | Details for llmlatency-0.1.1-py3-none-any.whl |
Total release size: 22.4 kB
Release files / llmlatency-0.1.1.tar.gz
| Download URL | llmlatency-0.1.1.tar.gz |
|---|---|
| Size | 12.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9c7c281060b730b095fe36b71e76060d9a728d9d7f5ba78c72dae841997f9764
|
|
BLAKE2b-256 checksum How to use checksums |
eb6eda61bea48bb9271dd4745452f5537273110b4a1b859bd22f9e7090c233e9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.13
|
Release files / llmlatency-0.1.1-py3-none-any.whl
| Download URL | llmlatency-0.1.1-py3-none-any.whl |
|---|---|
| Size | 9.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
04405f64ec0f802fb3b6924d626c6d031afe3ab547c4dd6ce368ca656c35e842
|
|
BLAKE2b-256 checksum How to use checksums |
e6d4bfaaddef8a1bc06061d91fbdff38a1911db9e003f773e2fa245db14c0e87
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.13
|
Security for llmlatency 0.1.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.