TypeSafe AI status

Q: Is TypeSafe AI down right now?

TypeSafe AI does not publish a machine-readable status feed. This page shows the success rate LLM Gateway measured on real TypeSafe AI traffic over the last 24 hours and 90 days.

Q: How is TypeSafe AI uptime measured?

Uptime is the share of requests to TypeSafe AI through LLM Gateway that completed without a provider or gateway error. Invalid requests (4xx caused by the request) and traffic on customers' own provider keys are excluded.

Q: What happens to my requests when TypeSafe AI has an outage?

LLM Gateway routes new traffic away from degraded providers. The TypeSafe AI models on LLM Gateway are currently served only by TypeSafe AI, so they cannot fail over to another provider.

Q: How often does this page update?

Every five minutes. Measured uptime comes from LLM Gateway's hourly traffic rollups; the official status and incidents come from the provider's status page.

Is TypeSafe AI down? Live official status, incidents, and the uptime LLM Gateway measured on real TypeSafe AI traffic.

No official feed

Measured uptime

Success rate of TypeSafe AI requests through LLM Gateway, by UTC day.

Last 24 hours

99.99%

72,842 requests

Last 90 days

98.64%

7,433,165 requests

Aug 11: Not enough traffic to measure
Aug 12: Not enough traffic to measure
Aug 13: Not enough traffic to measure
Aug 14: Not enough traffic to measure
Aug 15: Not enough traffic to measure
Aug 16: Not enough traffic to measure
Aug 17: Not enough traffic to measure
Aug 18: Not enough traffic to measure
Aug 19: Not enough traffic to measure
Aug 20: Not enough traffic to measure
Aug 21: Not enough traffic to measure
Aug 22: Not enough traffic to measure
Aug 23: Not enough traffic to measure
Aug 24: Not enough traffic to measure
Aug 25: Not enough traffic to measure
Aug 26: Not enough traffic to measure
Aug 27: Not enough traffic to measure
Aug 28: Not enough traffic to measure
Aug 29: Not enough traffic to measure
Aug 30: Not enough traffic to measure
Aug 31: Not enough traffic to measure
Sep 1: Not enough traffic to measure
Sep 2: Not enough traffic to measure
Sep 3: Not enough traffic to measure
Sep 4: Not enough traffic to measure
Sep 5: Not enough traffic to measure
Sep 6: Not enough traffic to measure
Sep 7: Not enough traffic to measure
Sep 8: Not enough traffic to measure
Sep 9: Not enough traffic to measure
Sep 10: Not enough traffic to measure
Sep 11: Not enough traffic to measure
Sep 12: Not enough traffic to measure
Sep 13: Not enough traffic to measure
Sep 14: Not enough traffic to measure
Sep 15: Not enough traffic to measure
Sep 16: Not enough traffic to measure
Sep 17: Not enough traffic to measure
Sep 18: Not enough traffic to measure
Sep 19: Not enough traffic to measure
Sep 20: Not enough traffic to measure
Sep 21: Not enough traffic to measure
Sep 22: 99.97% uptime over 3,655 requests
Sep 23: 99.76% uptime over 844 requests
Sep 24: 100% uptime over 2,198 requests
Sep 25: 100% uptime over 2,420 requests
Sep 26: 99.63% uptime over 820 requests
Sep 27: 99.70% uptime over 3,007 requests
Sep 28: 99.40% uptime over 2,645 requests
Sep 29: 99.99% uptime over 158,817 requests
Sep 30: 100% uptime over 1,806,789 requests
Oct 1: 99.98% uptime over 714,350 requests
Oct 2: 99.95% uptime over 4,314 requests
Oct 3: 100% uptime over 134 requests
Oct 4: 100% uptime over 1,376 requests
Oct 5: 99.75% uptime over 5,242 requests
Oct 6: 99.99% uptime over 75,825 requests
Oct 7: 99.99% uptime over 45,923 requests
Oct 8: 99.83% uptime over 33,894 requests
Oct 9: 100% uptime over 922 requests
Oct 10: 100% uptime over 16,089 requests
Oct 11: 100% uptime over 26,806 requests
Oct 12: 100% uptime over 25,703 requests
Oct 13: 100% uptime over 111,725 requests
Oct 14: 100% uptime over 24,917 requests
Oct 15: 100% uptime over 11,686 requests
Oct 16: 100% uptime over 12,037 requests
Oct 17: 100% uptime over 18,393 requests
Oct 18: 100% uptime over 26,278 requests
Oct 19: 100% uptime over 17,733 requests
Oct 20: 99.99% uptime over 206,848 requests
Oct 21: 100% uptime over 172,843 requests
Oct 22: 99.99% uptime over 29,927 requests
Oct 23: 99.99% uptime over 24,902 requests
Oct 24: 100% uptime over 16,946 requests
Oct 25: 100% uptime over 22,021 requests
Oct 26: 100% uptime over 47,139 requests
Oct 27: 100% uptime over 37,090 requests
Oct 28: 100% uptime over 158,157 requests
Oct 29: 100% uptime over 82,586 requests
Oct 30: 99.85% uptime over 50,003 requests
Oct 31: 100% uptime over 39,336 requests
Nov 1: 86.23% uptime over 732,482 requests
Nov 2: 100% uptime over 41,792 requests
Nov 3: 100% uptime over 1,124,192 requests
Nov 4: 100% uptime over 1,027,300 requests
Nov 5: 100% uptime over 356,157 requests
Nov 6: 99.96% uptime over 19,779 requests
Nov 7: 99.97% uptime over 17,242 requests
Nov 8: 99.99% uptime over 71,881 requests

30 days ago90 days agoToday

≥ 99.5%
≥ 98%
≥ 95%
≥ 90%
< 90%
No data
Official incident

Automatic failover

When TypeSafe AI fails or slows down, LLM Gateway retries the request on another healthy provider serving the same model, with no change to your code. 0 of 2 TypeSafe AI models can fail over.

TypeSafe AI models and pricing

Frequently asked questions

Is TypeSafe AI down right now?

TypeSafe AI does not publish a machine-readable status feed. This page shows the success rate LLM Gateway measured on real TypeSafe AI traffic over the last 24 hours and 90 days.

How is TypeSafe AI uptime measured?

Uptime is the share of requests to TypeSafe AI through LLM Gateway that completed without a provider or gateway error. Invalid requests (4xx caused by the request) and traffic on customers' own provider keys are excluded.

What happens to my requests when TypeSafe AI has an outage?

LLM Gateway routes new traffic away from degraded providers. The TypeSafe AI models on LLM Gateway are currently served only by TypeSafe AI, so they cannot fail over to another provider.

How often does this page update?

Every five minutes. Measured uptime comes from LLM Gateway's hourly traffic rollups; the official status and incidents come from the provider's status page.