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

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

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

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

## Was the doubao API down on August 10, 2026?

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

| UTC | What failed | Regions | Duration (lower bound) | Failed probes | Verdict |
| --- | --- | --- | --- | --- | --- |
| 19:45-19:45 | host probes | eu-hetzner sa-east | <5 min | 2 | unattributed |

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

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