# AI API outages on September 26, 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 26, 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 11:56 UTC, at least 4 minutes observed in total.

| UTC | What failed | Regions | Duration (lower bound) | Failed probes | Verdict |
| --- | --- | --- | --- | --- | --- |
| 11:56-12:00 | requests to gemini-flash-lite-latest | eu-hetzner sa-east | >=4 min | 2 | provider_outage |

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

## Was the stepfun API down on September 26, 2026?

Yes, measured. 1 outage(s) attributed to stepfun: host probes failed from up to 2 of 4 regions at once while no other provider was failing, first at 15:30 UTC, each shorter than one 5-minute probe cycle.

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

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

## Was the baichuan API down on September 26, 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 |
| --- | --- | --- | --- | --- | --- |
| 04:55-05:01 | host probes | eu-hetzner sa-east | >=6 min | 2 | unattributed |
| 12:35-12:50 | host probes | ap-tokyo us-central | >=15 min | 3 | unattributed |

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

## Was the iflytek API down on September 26, 2026?

Not attributably. 1 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 |
| --- | --- | --- | --- | --- | --- |
| 14:20-14:20 | host probes | ap-tokyo sa-east | <5 min | 2 | unattributed |

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

## Was the yi-01ai API down on September 26, 2026?

Not attributably. 4 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 |
| --- | --- | --- | --- | --- | --- |
| 04:15-05:00 | host probes | ap-tokyo sa-east | >=45 min | 6 | unattributed |
| 09:00-09:10 | host probes | sa-east us-central | >=10 min | 2 | unattributed |
| 12:20-12:50 | host probes | ap-tokyo eu-hetzner | >=30 min | 4 | unattributed |
| 14:50-15:20 | host probes | ap-tokyo sa-east | >=30 min | 5 | unattributed |

Live status now: https://llmlatency.dev/provider/yi-01ai

Source: https://llmlatency.dev/incidents/2026-09-26 · CC BY 4.0