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

Yes, measured. 6 outage(s) attributed to OpenAI: host probes failed from up to 4 of 4 regions at once while no other provider was failing, first at 00:40 UTC, at least 166 minutes observed in total. OpenAI's status page lists nothing that day.

| UTC | What failed | Regions | Duration (lower bound) | Failed probes | Verdict |
| --- | --- | --- | --- | --- | --- |
| 00:00-00:05 | host probes | ap-tokyo eu-hetzner | >=4 min | 2 | unattributed |
| 00:40-00:45 | host probes | sa-east us-central | >=5 min | 2 | provider_outage |
| 01:20-02:15 | host probes | ap-tokyo eu-hetzner sa-east us-central | >=55 min | 10 | unattributed |
| 03:05-04:20 | host probes | ap-tokyo eu-hetzner sa-east us-central | >=75 min | 12 | unattributed |
| 04:50-05:15 | host probes | ap-tokyo eu-hetzner sa-east | >=25 min | 5 | unattributed |
| 05:35-06:00 | host probes | ap-tokyo eu-hetzner sa-east us-central | >=25 min | 6 | unattributed |
| 06:25-06:30 | host probes | eu-hetzner sa-east | >=4 min | 2 | unattributed |
| 07:05-07:35 | host probes | ap-tokyo eu-hetzner sa-east us-central | >=30 min | 8 | unattributed |
| 08:25-08:40 | host probes | ap-tokyo eu-hetzner | >=16 min | 4 | unattributed |
| 09:15-09:35 | host probes | ap-tokyo eu-hetzner us-central | >=20 min | 4 | unattributed |
| 09:55-11:20 | host probes | ap-tokyo eu-hetzner sa-east us-central | >=85 min | 19 | unattributed |
| 11:40-12:05 | host probes | ap-tokyo sa-east us-central | >=25 min | 4 | unattributed |
| 12:45-12:55 | host probes | eu-hetzner sa-east | >=10 min | 2 | unattributed |
| 13:40-14:45 | host probes | ap-tokyo eu-hetzner us-central | >=65 min | 8 | unattributed |
| 15:20-15:45 | host probes | ap-tokyo eu-hetzner sa-east | >=26 min | 4 | provider_outage |
| 16:40-16:50 | host probes | eu-hetzner us-central | >=10 min | 2 | provider_outage |
| 17:10-17:35 | host probes | eu-hetzner sa-east us-central | >=25 min | 6 | provider_outage |
| 18:00-19:30 | host probes | ap-tokyo eu-hetzner sa-east us-central | >=90 min | 15 | unattributed |
| 19:55-20:10 | host probes | eu-hetzner sa-east us-central | >=14 min | 3 | provider_outage |
| 20:25-21:50 | host probes | ap-tokyo eu-hetzner sa-east us-central | >=85 min | 13 | provider_outage |
| 22:10-23:45 | host probes | ap-tokyo eu-hetzner sa-east us-central | >=95 min | 17 | unattributed |

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

## Was the Claude API (Anthropic) down on August 12, 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 13:50 UTC: Degraded performance for multiple models (minor)

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

## Was the nebius API down on August 12, 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 13:30 UTC: External VPC connectivity issues (major)

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

## Was the iflytek API down on August 12, 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 |
| --- | --- | --- | --- | --- | --- |
| 12:35-13:10 | host probes | ap-tokyo us-central | >=35 min | 4 | unattributed |

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

## Was the yi-01ai API down on August 12, 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 |
| --- | --- | --- | --- | --- | --- |
| 07:05-07:40 | host probes | ap-tokyo eu-hetzner | >=35 min | 5 | unattributed |
| 11:50-12:10 | host probes | ap-tokyo sa-east us-central | >=20 min | 5 | unattributed |

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

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