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

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

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

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

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

Yes, measured. 1 outage(s) attributed to Google: requests to gemini-flash-lite-latest failed from up to 3 of 4 regions at once while no other provider was failing, first at 21:30 UTC, each shorter than one 5-minute probe cycle.

| UTC | What failed | Regions | Duration (lower bound) | Failed probes | Verdict |
| --- | --- | --- | --- | --- | --- |
| 14:25-14:25 | requests to gemini-flash-lite-latest | sa-east us-central | <5 min | 2 | unattributed |
| 21:30-21:30 | requests to gemini-flash-lite-latest | eu-hetzner sa-east us-central | <5 min | 3 | provider_outage |

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

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

Yes, measured. 1 outage(s) attributed to yi-01ai: host probes failed from up to 2 of 4 regions at once while no other provider was failing, first at 09:55 UTC, each shorter than one 5-minute probe cycle.

| UTC | What failed | Regions | Duration (lower bound) | Failed probes | Verdict |
| --- | --- | --- | --- | --- | --- |
| 09:55-09:55 | host probes | ap-tokyo eu-hetzner | <5 min | 2 | provider_outage |

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

## Was the stepfun API down on August 2, 2026?

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

| UTC | What failed | Regions | Duration (lower bound) | Failed probes | Verdict |
| --- | --- | --- | --- | --- | --- |
| 17:55-17:55 | host probes | eu-hetzner us-central | <5 min | 2 | unattributed |

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

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