# AI API outages on August 16, 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 yi-01ai API down on August 16, 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 06:45 UTC, at least 10 minutes observed in total.

| UTC | What failed | Regions | Duration (lower bound) | Failed probes | Verdict |
| --- | --- | --- | --- | --- | --- |
| 06:45-06:55 | host probes | ap-tokyo sa-east | >=10 min | 2 | provider_outage |

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

## Was the Claude API (Anthropic) down on August 16, 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 21:58 UTC: Service disruption on Claude services (critical)

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

## Was the Gemini API (Google) down on August 16, 2026?

Not attributably. 1 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 |
| --- | --- | --- | --- | --- | --- |
| 10:35-10:35 | requests to gemini-flash-lite-latest | sa-east us-central | <5 min | 2 | unattributed |

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

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