# AI API outages on August 25, 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 August 25, 2026?

Yes, measured. 3 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 07:35 UTC, at least 3 minutes observed in total.

| UTC | What failed | Regions | Duration (lower bound) | Failed probes | Verdict |
| --- | --- | --- | --- | --- | --- |
| 07:35-07:35 | requests to gemini-flash-lite-latest | ap-tokyo sa-east us-central | <5 min | 3 | provider_outage |
| 10:05-10:08 | requests to gemini-flash-lite-latest | eu-hetzner sa-east us-central | >=3 min | 3 | unattributed |
| 11:45-11:48 | requests to gemini-flash-lite-latest | ap-tokyo eu-hetzner sa-east | >=3 min | 3 | unattributed |
| 12:10-12:13 | requests to gemini-flash-lite-latest | eu-hetzner sa-east us-central | >=3 min | 3 | provider_outage |
| 13:25-13:28 | requests to gemini-flash-lite-latest | ap-tokyo eu-hetzner sa-east us-central | >=3 min | 4 | unattributed |
| 13:50-13:53 | requests to gemini-flash-lite-latest | eu-hetzner sa-east | >=3 min | 2 | unattributed |
| 14:15-14:18 | requests to gemini-flash-lite-latest | ap-tokyo eu-hetzner sa-east us-central | >=3 min | 4 | unattributed |
| 14:40-14:40 | requests to gemini-flash-lite-latest | sa-east us-central | <5 min | 2 | provider_outage |
| 15:05-15:05 | requests to gemini-flash-lite-latest | ap-tokyo us-central | <5 min | 2 | unattributed |

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

## Was the Mistral API down on August 25, 2026?

Yes, measured. 1 outage(s) attributed to Mistral: host probes failed from up to 4 of 4 regions at once while no other provider was failing, first at 22:05 UTC, at least 5 minutes observed in total. At least once Mistral's own host answered with an HTTP 5xx.

| UTC | What failed | Regions | Duration (lower bound) | Failed probes | Verdict |
| --- | --- | --- | --- | --- | --- |
| 22:05-22:10 | host probes | ap-tokyo eu-hetzner sa-east us-central | >=5 min | 7 | provider_outage |

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

## Was the friendli API down on August 25, 2026?

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

| UTC | What failed | Regions | Duration (lower bound) | Failed probes | Verdict |
| --- | --- | --- | --- | --- | --- |
| 18:10-18:10 | host probes | ap-tokyo sa-east us-central | <5 min | 3 | provider_outage |

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

## Was the baseten API down on August 25, 2026?

Not by our measurements. No failure of baseten was seen from two or more regions at once; 3 single-region failure(s) are not called an outage. baseten's own status page opened 2 entries that day (self-reported, listed below).
- self-reported 12:34 UTC: Elevated inference 500s for models in an EU cluster due to provider outage (minor)
- self-reported 16:17 UTC: Elevated errors for deepseek-ai/DeepSeek-V4-Flash-0731 on Model APIs. **Dedicated Inferenc (minor)

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

## Was the yi-01ai API down on August 25, 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 |
| --- | --- | --- | --- | --- | --- |
| 03:55-04:15 | host probes | ap-tokyo sa-east | >=20 min | 4 | unattributed |
| 08:45-09:25 | host probes | ap-tokyo sa-east | >=40 min | 5 | unattributed |
| 13:50-14:00 | host probes | ap-tokyo eu-hetzner | >=10 min | 4 | unattributed |

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

Source: https://llmlatency.dev/incidents/2026-08-25 · CC BY 4.0