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

Yes, measured. 11 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:35 UTC, at least 134 minutes observed in total. OpenAI's status page lists nothing that day.

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

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

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

Not attributably. 1 multi-region failure(s) of friendli coincided with failures of other providers, so the cause sat above friendli and is not blamed on it.

| UTC | What failed | Regions | Duration (lower bound) | Failed probes | Verdict |
| --- | --- | --- | --- | --- | --- |
| 12:55-12:55 | host probes | ap-tokyo sa-east | <5 min | 2 | unattributed |

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

## Was the yi-01ai API down on August 11, 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:20-07:25 | host probes | ap-tokyo us-central | >=5 min | 2 | unattributed |
| 15:30-15:35 | host probes | ap-tokyo sa-east | >=5 min | 2 | unattributed |

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

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