# AI API outages on July 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 July 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 18:13 UTC, each shorter than one 5-minute probe cycle.

| UTC | What failed | Regions | Duration (lower bound) | Failed probes | Verdict |
| --- | --- | --- | --- | --- | --- |
| 18:13-18:13 | requests to gemini-flash-lite-latest | ap-tokyo us-central | <5 min | 2 | provider_outage |

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

## Was the doubao API down on July 26, 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 08:22 UTC, at least 13 minutes observed in total.

| UTC | What failed | Regions | Duration (lower bound) | Failed probes | Verdict |
| --- | --- | --- | --- | --- | --- |
| 08:22-08:35 | host probes | eu-hetzner sa-east | >=13 min | 3 | provider_outage |
| 13:25-13:33 | host probes | ap-tokyo sa-east | >=9 min | 2 | unattributed |

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

## Was the iflytek API down on July 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 |
| --- | --- | --- | --- | --- | --- |
| 09:01-09:16 | host probes | sa-east us-central | >=16 min | 3 | unattributed |

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

## Was the stepfun API down on July 26, 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 |
| --- | --- | --- | --- | --- | --- |
| 16:46-16:51 | host probes | sa-east us-central | >=5 min | 3 | unattributed |

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

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

Not attributably. 2 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 |
| --- | --- | --- | --- | --- | --- |
| 15:26-15:31 | host probes | ap-tokyo us-central | >=5 min | 3 | unattributed |
| 16:46-16:51 | host probes | ap-tokyo us-central | >=5 min | 3 | unattributed |

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

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