# AI API outages on September 29, 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 doubao API down on September 29, 2026? Yes, measured. 1 outage(s) attributed to doubao: host probes failed from up to 2 of 4 regions at once while no other provider was failing, first at 20:30 UTC, each shorter than one 5-minute probe cycle. | UTC | What failed | Regions | Duration (lower bound) | Failed probes | Verdict | | --- | --- | --- | --- | --- | --- | | 03:55-04:05 | host probes | ap-tokyo sa-east | >=10 min | 3 | unattributed | | 08:30-08:35 | host probes | ap-tokyo eu-hetzner sa-east | >=5 min | 4 | unattributed | | 20:30-20:31 | host probes | eu-hetzner sa-east | <5 min | 2 | provider_outage | Live status now: https://llmlatency.dev/provider/doubao ## Was the iflytek API down on September 29, 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 13:15 UTC, at least 6 minutes observed in total. | UTC | What failed | Regions | Duration (lower bound) | Failed probes | Verdict | | --- | --- | --- | --- | --- | --- | | 08:50-09:05 | host probes | ap-tokyo sa-east | >=15 min | 3 | unattributed | | 09:30-09:55 | host probes | ap-tokyo sa-east | >=25 min | 4 | unattributed | | 13:15-13:21 | host probes | ap-tokyo eu-hetzner | >=6 min | 2 | provider_outage | | 14:55-15:10 | host probes | ap-tokyo sa-east us-central | >=15 min | 3 | unattributed | Live status now: https://llmlatency.dev/provider/iflytek ## Was the inference-net API down on September 29, 2026? Yes, measured. 1 outage(s) attributed to inference-net: host probes failed from up to 4 of 4 regions at once while no other provider was failing, first at 22:00 UTC, at least 11 minutes observed in total. At least once inference-net's own host answered with an HTTP 5xx. | UTC | What failed | Regions | Duration (lower bound) | Failed probes | Verdict | | --- | --- | --- | --- | --- | --- | | 22:00-22:10 | host probes | ap-tokyo eu-hetzner sa-east us-central | >=11 min | 12 | provider_outage | Live status now: https://llmlatency.dev/provider/inference-net ## Was the kimi API down on September 29, 2026? Yes, measured. 1 outage(s) attributed to kimi: host probes failed from up to 4 of 4 regions at once while no other provider was failing, first at 23:20 UTC, at least 36 minutes observed in total. At least once kimi's own host answered with an HTTP 5xx. | UTC | What failed | Regions | Duration (lower bound) | Failed probes | Verdict | | --- | --- | --- | --- | --- | --- | | 23:20-23:55 | host probes | ap-tokyo eu-hetzner sa-east us-central | >=36 min | 32 | provider_outage | Live status now: https://llmlatency.dev/provider/kimi ## Was the yi-01ai API down on September 29, 2026? Yes, measured. 1 outage(s) attributed to yi-01ai: host probes failed from up to 2 of 4 regions at once while no other provider was failing, first at 10:00 UTC, at least 5 minutes observed in total. | UTC | What failed | Regions | Duration (lower bound) | Failed probes | Verdict | | --- | --- | --- | --- | --- | --- | | 06:00-06:00 | host probes | sa-east us-central | <5 min | 2 | unattributed | | 08:40-09:05 | host probes | ap-tokyo sa-east | >=25 min | 4 | unattributed | | 10:00-10:05 | host probes | ap-tokyo sa-east | >=5 min | 2 | provider_outage | | 10:55-11:05 | host probes | ap-tokyo sa-east | >=10 min | 3 | unattributed | | 14:50-15:15 | host probes | ap-tokyo us-central | >=25 min | 3 | unattributed | | 16:05-16:15 | host probes | ap-tokyo us-central | >=10 min | 2 | unattributed | Live status now: https://llmlatency.dev/provider/yi-01ai ## Was the OpenAI API down on September 29, 2026? Not by our measurements. No failure of OpenAI was seen from two or more regions at once; 1 single-region failure(s) are not called an outage. OpenAI's own status page opened 2 entries that day (self-reported, listed below). - self-reported 17:49 UTC: Support available via email (none) - self-reported 17:52 UTC: Elevated errors across ChatGPT, Codex, and the API including the Agents API (minor) Live status now: https://llmlatency.dev/provider/openai ## Was the Claude API (Anthropic) down on September 29, 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 14:21 UTC: Elevated errors on claude.ai, Claude Code, Claude Cowork and the Claude API (major) Live status now: https://llmlatency.dev/provider/anthropic ## Was the TypeSafe API down on September 29, 2026? Not by our measurements. No failure of TypeSafe was seen from two or more regions at once; 1 single-region failure(s) are not called an outage. TypeSafe's own status page opened 1 entry that day (self-reported, listed below). - self-reported 15:02 UTC: Routine operational maintenance (none) Live status now: https://llmlatency.dev/provider/typesafe ## Was the Gemini API (Google) down on September 29, 2026? Not attributably. 2 multi-region failure(s) of Google coincided with failures of other providers, so the cause sat above Google and is not blamed on it. | UTC | What failed | Regions | Duration (lower bound) | Failed probes | Verdict | | --- | --- | --- | --- | --- | --- | | 12:35-12:45 | requests to gemini-flash-lite-latest | ap-tokyo eu-hetzner sa-east us-central | >=9 min | 4 | unattributed | | 14:16-14:25 | requests to gemini-flash-lite-latest | eu-hetzner us-central | >=9 min | 2 | unattributed | Live status now: https://llmlatency.dev/provider/google ## Was the baseten API down on September 29, 2026? Not by our measurements. No failure of baseten was seen from two or more regions at once. baseten's own status page opened 2 entries that day (self-reported, listed below). - self-reported 01:07 UTC: Metrics degradation in UI and API. **Inference not affected** (minor) - self-reported 08:12 UTC: Elevated 500s in Single us-central Region (major) Live status now: https://llmlatency.dev/provider/baseten ## Was the baichuan API down on September 29, 2026? Not attributably. 6 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 | | --- | --- | --- | --- | --- | --- | | 05:55-05:56 | host probes | ap-tokyo eu-hetzner | <5 min | 2 | unattributed | | 07:20-07:45 | host probes | ap-tokyo sa-east | >=25 min | 3 | unattributed | | 08:50-08:55 | host probes | ap-tokyo sa-east | >=5 min | 2 | unattributed | | 12:45-12:50 | host probes | ap-tokyo us-central | >=5 min | 2 | unattributed | | 14:00-14:10 | host probes | ap-tokyo sa-east us-central | >=10 min | 3 | unattributed | | 15:25-15:55 | host probes | ap-tokyo eu-hetzner us-central | >=30 min | 6 | unattributed | Live status now: https://llmlatency.dev/provider/baichuan ## Was the sarvam API down on September 29, 2026? Not attributably. 1 multi-region failure(s) of sarvam coincided with failures of other providers, so the cause sat above sarvam and is not blamed on it. | UTC | What failed | Regions | Duration (lower bound) | Failed probes | Verdict | | --- | --- | --- | --- | --- | --- | | 18:00-18:00 | host probes | sa-east us-central | <5 min | 2 | unattributed | Live status now: https://llmlatency.dev/provider/sarvam ## Was the sensenova API down on September 29, 2026? Not attributably. 1 multi-region failure(s) of sensenova coincided with failures of other providers, so the cause sat above sensenova and is not blamed on it. | UTC | What failed | Regions | Duration (lower bound) | Failed probes | Verdict | | --- | --- | --- | --- | --- | --- | | 09:25-09:30 | host probes | sa-east us-central | >=5 min | 2 | unattributed | Live status now: https://llmlatency.dev/provider/sensenova ## Was the stepfun API down on September 29, 2026? Not attributably. 1 multi-region failure(s) of stepfun coincided with failures of other providers, so the cause sat above stepfun and is not blamed on it. | UTC | What failed | Regions | Duration (lower bound) | Failed probes | Verdict | | --- | --- | --- | --- | --- | --- | | 06:00-06:10 | host probes | sa-east us-central | >=10 min | 3 | unattributed | Live status now: https://llmlatency.dev/provider/stepfun Source: https://llmlatency.dev/incidents/2026-09-29 ยท CC BY 4.0