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

Last verified September 27, 2026 · rebuilt about every 30 minutes

Is the TypeSafe API down right now?

As of September 27, 2026, the typesafe AI API responds in 111 ms p50 (edge, time-to-first-byte) from US (Central) — its fastest measured region — with 100% uptime. Slowest is Europe (Germany) at 284 ms p50.

Was typesafe down in the last 3 days?

No. All 74 probes from 4 region(s) reached the typesafe API in the last 72 hours.

Earlier days with TypeSafe incidents: Sep 24 (status page) · Sep 23 (status page) · Sep 21 (status page)

Show this live in your README: — embed code

What TypeSafe’s own status page reported

Nothing. TypeSafe’s status page lists no incident in the last 72 hours (checked Sep 27, 14:17 UTC).

Is typesafe getting faster or slower?

hourly p50 latencyall probes succeededsome probes failedhalf or more failedno data

One panel per region: the line is the hourly p50 edge latency (shared scale, ms), the strips beneath it are the outcome of that hour’s host probes and, below them, of the real requests to jev-1.13.0. Hover any hour for the numbers. Flat is good; a rising line means the endpoint is slowing down from that origin, a gap means no probe succeeded in that hour.

How fast is the typesafe API from each region?

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

How does typesafe compare to other providers?

• typesafe vs openai latency
• typesafe vs anthropic latency
• typesafe vs google latency
• typesafe vs mistral latency
• typesafe vs deepseek latency
• typesafe vs xai latency
• typesafe vs groq latency
• typesafe vs cerebras latency
• typesafe vs sambanova latency
• typesafe vs together latency
• typesafe vs fireworks latency
• typesafe vs openrouter latency