What is the friendli API's uptime?

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

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

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

Is the friendli API down right now?

Reachable from all 4 regions

Last successful probe Oct 22, 01:46 UTC · every 5 minutes from 4 region(s)

There was an outage: on Oct 21, 00:55 UTC, host probes failed from 3 of 4 regions simultaneously for at least 6 minutes. friendli’s own API host answered with an HTTP 502, so the failure was on their side by their own server’s account. Measured from outside friendli’s own network, independently of its status page; full log: measured AI API incidents.

Real requests: not measured for friendli — 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.

friendli publishes no machine-readable status page, so there is nothing to cross-check against.

As of October 22, 2026, the friendli AI API responds in 167 ms p50 (edge, time-to-first-byte) from US (Central) — its fastest measured region — with 100% uptime. Slowest is Europe (Germany) at 398 ms p50.

Endpoint response (TTFB), 24 h

167 ms

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

Uptime, 24 h

100%

1,152 probes across 4 region(s)

Failed probes, 72 h

of 3,459 · Europe (Germany), US (Central), South America (São Paulo)

Reported by friendli, 72 h

—

no machine-readable status page

Was friendli down in the last 3 days?

Yes. 1 outage(s) could be attributed to friendli in the last 72 hours: probes failed from two or more regions at once while no other provider was failing.

Oct 21, 00:55 UTCOutage — 3 of 4 regions (Europe (Germany), South America (São Paulo), US (Central)) · at least 6 minutes · 6 failed probe(s) · http 502; http 503

Earlier days with friendli incidents: Oct 21 (1 outage) · Oct 4 (1 outage) · Sep 30 (2 outages) · Sep 8 (1 outage) · Sep 1 (1 outage) · Aug 25 (1 outage) · Aug 5 (6 outages) · Aug 4 (12 outages)

Show this live in your README: — embed code

What friendli’s own status page reported

friendli publishes no machine-readable status page, so there is nothing to set against the measurements above.

Is friendli getting faster or slower?

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): 2 failed / 864 endpoint probesUS (Central): 2 failed / 862 endpoint probesAsia (Tokyo): 0 failed / 862 endpoint probesSouth America (São Paulo): 2 failed / 862 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 friendli 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)	278 ms	464 ms	100%
Europe (Germany)	398 ms	800 ms	100%
South America (São Paulo)	272 ms	380 ms	100%
US (Central)	167 ms	246 ms	100%

Measured from US (Central), friendli responds in 167 ms; from Europe (Germany) the same API takes 398 ms — 2.4× 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 friendli’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 friendli’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 friendli’s own reports are shown next to the measurements rather than folded into them.