# AI API outages on October 5, 2026 (UTC)

Measured every 5 minutes from 4 regions. An outage is attributed to a provider only when it failed from 2+ regions at once and no other provider failed in the same minutes.

## Was the TypeSafe API down on October 5, 2026?

Yes, measured. 2 outage(s) attributed to TypeSafe: host probes, requests to jev-1.13.0 failed from up to 4 of 4 regions at once while no other provider was failing, first at 23:10 UTC, at least 3 minutes observed in total. At least once TypeSafe's own host answered with an HTTP 5xx. TypeSafe's status page lists nothing that day.

| UTC | What failed | Regions | Duration (lower bound) | Failed probes | Verdict |
| --- | --- | --- | --- | --- | --- |
| 23:10-23:10 | requests to jev-1.13.0 | ap-tokyo sa-east us-central | <5 min | 3 | provider_outage |
| 23:10-23:12 | host probes | ap-tokyo eu-hetzner sa-east us-central | >=3 min | 4 | provider_outage |

Live status now: https://llmlatency.dev/provider/typesafe

## Was the Gemini API (Google) down on October 5, 2026?

Yes, measured. 1 outage(s) attributed to Google: requests to gemini-flash-lite-latest failed from up to 3 of 4 regions at once while no other provider was failing, first at 17:30 UTC, each shorter than one 5-minute probe cycle.

| UTC | What failed | Regions | Duration (lower bound) | Failed probes | Verdict |
| --- | --- | --- | --- | --- | --- |
| 17:30-17:30 | requests to gemini-flash-lite-latest | ap-tokyo sa-east us-central | <5 min | 3 | provider_outage |

Live status now: https://llmlatency.dev/provider/google

## Was the doubao API down on October 5, 2026?

Yes, measured. 1 outage(s) attributed to doubao: host probes failed from up to 4 of 4 regions at once while no other provider was failing, first at 07:42 UTC, at least 17 minutes observed in total.

| UTC | What failed | Regions | Duration (lower bound) | Failed probes | Verdict |
| --- | --- | --- | --- | --- | --- |
| 07:42-08:00 | host probes | ap-tokyo eu-hetzner sa-east us-central | >=17 min | 4 | provider_outage |
| 08:55-09:15 | host probes | ap-tokyo sa-east us-central | >=20 min | 5 | unattributed |
| 10:50-10:50 | host probes | sa-east us-central | <5 min | 2 | unattributed |

Live status now: https://llmlatency.dev/provider/doubao

## Was the iflytek API down on October 5, 2026?

Yes, measured. 1 outage(s) attributed to iflytek: host probes failed from up to 2 of 4 regions at once while no other provider was failing, first at 10:18 UTC, at least 5 minutes observed in total.

| UTC | What failed | Regions | Duration (lower bound) | Failed probes | Verdict |
| --- | --- | --- | --- | --- | --- |
| 10:18-10:23 | host probes | eu-hetzner sa-east | >=5 min | 3 | provider_outage |
| 12:00-12:20 | host probes | ap-tokyo sa-east us-central | >=20 min | 4 | unattributed |

Live status now: https://llmlatency.dev/provider/iflytek

## Was the OpenAI API down on October 5, 2026?

Not by our measurements. No failure of OpenAI was seen from two or more regions at once. OpenAI's own status page opened 5 entries that day (self-reported, listed below).
- self-reported 07:03 UTC: Elevated Work Mode errors (minor)
- self-reported 12:44 UTC: Issues saving and editing Pages (minor)
- self-reported 15:50 UTC: Admin Console Intermittently Inaccessible (none)
- self-reported 16:58 UTC: Elevated errors in ChatGPT conversations (minor)
- self-reported 17:58 UTC: Elevated error rates in Codex Cloud (none)

Live status now: https://llmlatency.dev/provider/openai

## Was the Claude API (Anthropic) down on October 5, 2026?

Not by our measurements. No failure of Anthropic was seen from two or more regions at once. Anthropic's own status page opened 1 entry that day (self-reported, listed below).
- self-reported 13:05 UTC: Elevated errors for Claude Mythos 5.1 and Claude Fable 5.1 (major)

Live status now: https://llmlatency.dev/provider/anthropic

## Was the baichuan API down on October 5, 2026?

Not attributably. 2 multi-region failure(s) of baichuan coincided with failures of other providers, so the cause sat above baichuan and is not blamed on it.

| UTC | What failed | Regions | Duration (lower bound) | Failed probes | Verdict |
| --- | --- | --- | --- | --- | --- |
| 09:10-09:23 | host probes | ap-tokyo eu-hetzner sa-east | >=13 min | 3 | unattributed |
| 12:20-12:20 | host probes | sa-east us-central | <5 min | 2 | unattributed |

Live status now: https://llmlatency.dev/provider/baichuan

## Was the writer API down on October 5, 2026?

Not attributably. 1 multi-region failure(s) of writer coincided with failures of other providers, so the cause sat above writer and is not blamed on it.

| UTC | What failed | Regions | Duration (lower bound) | Failed probes | Verdict |
| --- | --- | --- | --- | --- | --- |
| 15:55-15:55 | host probes | sa-east us-central | <5 min | 2 | unattributed |

Live status now: https://llmlatency.dev/provider/writer

Source: https://llmlatency.dev/incidents/2026-10-05 · CC BY 4.0