# AI API outages on September 28, 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 Gemini API (Google) down on September 28, 2026? Yes, measured. 1 outage(s) attributed to Google: requests to gemini-flash-lite-latest failed from up to 2 of 4 regions at once while no other provider was failing, first at 06:05 UTC, each shorter than one 5-minute probe cycle. | UTC | What failed | Regions | Duration (lower bound) | Failed probes | Verdict | | --- | --- | --- | --- | --- | --- | | 02:25-02:45 | requests to gemini-flash-lite-latest | ap-tokyo eu-hetzner us-central | >=20 min | 3 | unattributed | | 05:05-05:05 | requests to gemini-flash-lite-latest | sa-east us-central | <5 min | 2 | unattributed | | 06:05-06:05 | requests to gemini-flash-lite-latest | sa-east us-central | <5 min | 2 | provider_outage | | 06:45-07:05 | requests to gemini-flash-lite-latest | ap-tokyo eu-hetzner sa-east us-central | >=20 min | 5 | unattributed | | 08:55-09:05 | requests to gemini-flash-lite-latest | ap-tokyo eu-hetzner | >=9 min | 2 | unattributed | | 11:45-18:25 | requests to gemini-flash-lite-latest | ap-tokyo eu-hetzner sa-east us-central | >=400 min | 80 | unattributed | | 19:05-21:45 | requests to gemini-flash-lite-latest | ap-tokyo eu-hetzner sa-east us-central | >=160 min | 31 | unattributed | | 22:35-22:45 | requests to gemini-flash-lite-latest | eu-hetzner sa-east | >=9 min | 2 | unattributed | Live status now: https://llmlatency.dev/provider/google ## Was the TypeSafe API down on September 28, 2026? Not attributably. 5 multi-region failure(s) of TypeSafe coincided with failures of other providers, so the cause sat above TypeSafe and is not blamed on it. TypeSafe's own status page opened 1 entry that day (self-reported, listed below). | UTC | What failed | Regions | Duration (lower bound) | Failed probes | Verdict | | --- | --- | --- | --- | --- | --- | | 13:21-13:50 | host probes | ap-tokyo eu-hetzner sa-east us-central | >=29 min | 9 | unattributed | | 13:35-13:35 | requests to jev-1.13.0 | eu-hetzner us-central | <5 min | 2 | unattributed | | 14:55-14:55 | requests to jev-1.13.0 | ap-tokyo us-central | <5 min | 2 | unattributed | | 15:01-15:25 | host probes | ap-tokyo eu-hetzner sa-east | >=24 min | 5 | unattributed | | 16:00-16:06 | host probes | eu-hetzner sa-east | >=6 min | 2 | unattributed | - self-reported 16:07 UTC: Degradation in API Traffic (none) Live status now: https://llmlatency.dev/provider/typesafe ## Was the baichuan API down on September 28, 2026? Not attributably. 4 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 | | --- | --- | --- | --- | --- | --- | | 00:50-01:00 | host probes | ap-tokyo sa-east | >=10 min | 2 | unattributed | | 07:30-07:45 | host probes | ap-tokyo us-central | >=15 min | 2 | unattributed | | 09:10-09:25 | host probes | ap-tokyo sa-east | >=15 min | 2 | unattributed | | 14:00-14:05 | host probes | ap-tokyo sa-east | >=5 min | 2 | unattributed | Live status now: https://llmlatency.dev/provider/baichuan ## Was the friendli API down on September 28, 2026? Not attributably. 1 multi-region failure(s) of friendli coincided with failures of other providers, so the cause sat above friendli and is not blamed on it. | UTC | What failed | Regions | Duration (lower bound) | Failed probes | Verdict | | --- | --- | --- | --- | --- | --- | | 12:55-13:00 | host probes | eu-hetzner sa-east us-central | >=5 min | 3 | unattributed | Live status now: https://llmlatency.dev/provider/friendli ## Was the iflytek API down on September 28, 2026? Not attributably. 2 multi-region failure(s) of iflytek coincided with failures of other providers, so the cause sat above iflytek and is not blamed on it. | UTC | What failed | Regions | Duration (lower bound) | Failed probes | Verdict | | --- | --- | --- | --- | --- | --- | | 10:10-10:15 | host probes | ap-tokyo sa-east | >=5 min | 2 | unattributed | | 14:05-14:25 | host probes | ap-tokyo sa-east | >=20 min | 3 | unattributed | Live status now: https://llmlatency.dev/provider/iflytek ## Was the stepfun API down on September 28, 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 | | --- | --- | --- | --- | --- | --- | | 14:05-14:20 | host probes | sa-east us-central | >=15 min | 2 | unattributed | Live status now: https://llmlatency.dev/provider/stepfun ## Was the yi-01ai API down on September 28, 2026? Not attributably. 3 multi-region failure(s) of yi-01ai coincided with failures of other providers, so the cause sat above yi-01ai and is not blamed on it. | UTC | What failed | Regions | Duration (lower bound) | Failed probes | Verdict | | --- | --- | --- | --- | --- | --- | | 08:00-08:10 | host probes | ap-tokyo us-central | >=10 min | 3 | unattributed | | 09:15-09:15 | host probes | ap-tokyo sa-east | <5 min | 2 | unattributed | | 14:15-14:25 | host probes | sa-east us-central | >=10 min | 2 | unattributed | Live status now: https://llmlatency.dev/provider/yi-01ai Source: https://llmlatency.dev/incidents/2026-09-28 ยท CC BY 4.0