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

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

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

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

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

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

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

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

Not attributably. 3 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 |
| --- | --- | --- | --- | --- | --- |
| 04:32-04:35 | host probes | ap-tokyo eu-hetzner | >=3 min | 2 | unattributed |
| 10:30-10:40 | host probes | ap-tokyo eu-hetzner us-central | >=10 min | 3 | unattributed |
| 18:00-18:15 | host probes | ap-tokyo eu-hetzner | >=15 min | 3 | unattributed |

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

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