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

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

| UTC | What failed | Regions | Duration (lower bound) | Failed probes | Verdict |
| --- | --- | --- | --- | --- | --- |
| 03:07-03:17 | host probes | ap-tokyo eu-hetzner sa-east us-central | >=10 min | 9 | provider_outage |

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

## Was the Claude API (Anthropic) down on August 19, 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 09:42 UTC: Degraded performance for Claude Opus 5 and Claude Haiku 4.5 (minor)

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

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

Not attributably. 3 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:02-10:10 | requests to gemini-flash-lite-latest | eu-hetzner us-central | >=7 min | 2 | unattributed |
| 13:48-13:55 | requests to gemini-flash-lite-latest | eu-hetzner us-central | >=7 min | 2 | unattributed |
| 15:02-15:10 | requests to gemini-flash-lite-latest | eu-hetzner us-central | >=7 min | 2 | unattributed |

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

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

Not by our measurements. No failure of baseten was seen from two or more regions at once. baseten's own status page opened 1 entry that day (self-reported, listed below).
- self-reported 01:23 UTC: Elevated errors for moonshotai/Kimi-K3 for US-pinned traffic on Model APIs. **Dedicated In (minor)

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

## Was the nebius API down on August 19, 2026?

Not by our measurements. No failure of nebius was seen from two or more regions at once; 1 single-region failure(s) are not called an outage. nebius's own status page opened 1 entry that day (self-reported, listed below).
- self-reported 10:43 UTC: Region us-central1 partial degradation (major)

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

## Was the yi-01ai API down on August 19, 2026?

Not attributably. 1 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 |
| --- | --- | --- | --- | --- | --- |
| 13:15-14:10 | host probes | ap-tokyo us-central | >=55 min | 8 | unattributed |

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

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