What is the ai21 API's uptime?

Measured uptime for the ai21 API averages 99.8% across 4 region(s) over the last 24 hours.

Is the ai21 API down? Live status, latency & uptime by region

Last verified October 21, 2026 · rebuilt about every 30 minutes

Is the ai21 API down right now?

Reachable from all 4 regions

Last successful probe Oct 21, 20:16 UTC · every 5 minutes from 4 region(s) · status feed checked Oct 21, 20:17 UTC

2 isolated failure(s) in the last 72 hours, the most recent (host probes) visible from only one region (US (Central)). A single-region failure cannot be separated from a problem on that network path, so it is not called an outage. Measured from outside ai21’s own network, independently of its status page; full log: measured AI API incidents.

Real requests: not measured for ai21 — only the API host is probed here, so errors limited to specific models are invisible to these probes. That is exactly what a status page tends to report, hence the line below.

ai21’s status page lists no open incident (checked Oct 21, 20:17 UTC).

As of October 21, 2026, the ai21 AI API responds in 235 ms p50 (edge, time-to-first-byte) from US (Central) — its fastest measured region — with 99.7% uptime. Slowest is Europe (Germany) at 399 ms p50.

Endpoint response (TTFB), 24 h

235 ms

Typical (p50) from US (Central), the fastest region

Uptime, 24 h

99.8%

1,152 probes across 4 region(s)

Failed probes, 72 h

of 3,459 · Europe (Germany), US (Central)

Reported by ai21, 72 h

on status.ai21.com

Was ai21 down in the last 3 days?

No. 2 isolated single-region probe failure(s) were recorded, none of which meets the bar for an outage (two or more regions at once).

Oct 21, 17:30 UTCUS (Central) only — not an outage · under one 5-minute probe cycle · 1 failed probe(s) · [Errno 104] Connection reset by peer
Oct 21, 10:31 UTCEurope (Germany) only — not an outage · under one 5-minute probe cycle · 1 failed probe(s) · [Errno 101] Network is unreachable

Show this live in your README: — embed code

What ai21’s own status page reported

Nothing. ai21’s status page lists no incident in the last 72 hours (checked Oct 21, 20:17 UTC).

Is ai21 getting faster or slower?

Right now ai21 is slower than usual from US (Central): 339 ms against a three-day typical of 235 ms.

Endpoint response (TTFB) · milliseconds · lower is faster

Last 72 hours · UTC · newest time on the right · current hour is incomplete.

Each line shows a region’s typical response per hour (p50), using the same scale. A gap means no successful timed probe in that hour.

typical response per hour (p50)all probes succeededsome failed (under half)half or more failedno probes recorded

Probe counts by region

Europe (Germany): 1 failed / 858 endpoint probesUS (Central): 1 failed / 856 endpoint probesAsia (Tokyo): 0 failed / 856 endpoint probesSouth America (São Paulo): 0 failed / 856 endpoint probes

Chart details

The strip shows endpoint probe outcomes, not model-request success. Adjacent hours with all successes or no data are joined. Hover an hour for its recorded values.

Latest is the most recent hourly p50 with data. Median is the median of hourly p50 values over these 72 hours. The “slower than usual” label means latest is at least 25% above that median; it is a relative change, not a fixed speed rating.

How fast is the ai21 API from each region?

Endpoint response (TTFB) · last 24 hours · milliseconds (ms) · lower is faster.

How to read these metrics

Endpoint response (TTFB)Network connection and the first response byte, without model inference.

Typical · p5050% of successful timed samples finish within this time.

Slower · p9595% of successful timed samples finish within this time.

Region	Typical (p50 TTFB)	Slower (p95)	Uptime
Asia (Tokyo)	334 ms	465 ms	100%
Europe (Germany)	399 ms	599 ms	99.7%
South America (São Paulo)	328 ms	450 ms	100%
US (Central)	235 ms	376 ms	99.7%

Measured from US (Central), ai21 responds in 235 ms; from Europe (Germany) the same API takes 399 ms — 1.7× longer for an identical request. That difference is the network path, not the model, and it applies to every call you make.

What is actually being measured here?

A probe in each region opens a real connection to ai21’s own API host every five minutes and times DNS resolution, the TCP handshake, the TLS handshake and the first byte of the response. Nothing is routed through a gateway or aggregator, so these figures describe ai21’s infrastructure rather than a reseller’s. Uptime counts a probe as failed only when the service genuinely fails — a 401 from an unauthenticated probe means the endpoint answered correctly and is counted as up.

What this page does not tell you

These are edge latency numbers: the time before the model begins generating. They say nothing about answer quality, throughput, price, or how long a full completion takes — those depend on the model you call. Edge latency matters because it is unavoidable: it is paid on every request, before a single token exists, and no prompt engineering removes it. Where an API key is available, inference time-to-first-token is measured separately and shown on the region pages with the model named next to the figure. Likewise, an unauthenticated probe cannot see errors that hit only some models or some accounts — the kind a status page usually reports — which is why ai21’s own reports are shown next to the measurements rather than folded into them.