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

Yes, measured. 8 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 04:14 UTC, at least 125 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:49-01:54 | host probes | ap-tokyo eu-hetzner sa-east us-central | >=65 min | 12 | unattributed |
| 04:14-04:17 | host probes | ap-tokyo sa-east | >=3 min | 2 | provider_outage |
| 05:37-06:19 | host probes | ap-tokyo eu-hetzner sa-east us-central | >=42 min | 6 | unattributed |
| 06:37-06:44 | host probes | ap-tokyo eu-hetzner | >=7 min | 2 | provider_outage |
| 07:07-07:19 | host probes | ap-tokyo eu-hetzner | >=12 min | 2 | unattributed |
| 07:34-07:39 | host probes | eu-hetzner sa-east | >=5 min | 2 | provider_outage |
| 08:14-08:22 | host probes | ap-tokyo sa-east us-central | >=8 min | 4 | unattributed |
| 09:12-09:14 | host probes | eu-hetzner sa-east us-central | >=2 min | 3 | unattributed |
| 10:35-11:10 | host probes | ap-tokyo sa-east us-central | >=35 min | 5 | unattributed |
| 11:40-11:55 | host probes | eu-hetzner sa-east | >=15 min | 2 | unattributed |
| 12:15-12:55 | host probes | ap-tokyo eu-hetzner sa-east us-central | >=40 min | 7 | unattributed |
| 13:50-14:20 | host probes | ap-tokyo eu-hetzner sa-east us-central | >=30 min | 5 | unattributed |
| 14:35-15:25 | host probes | ap-tokyo eu-hetzner sa-east us-central | >=50 min | 7 | unattributed |
| 16:10-16:20 | host probes | ap-tokyo us-central | >=10 min | 3 | unattributed |
| 16:45-17:50 | host probes | ap-tokyo eu-hetzner sa-east us-central | >=64 min | 9 | unattributed |
| 18:45-19:05 | host probes | ap-tokyo sa-east us-central | >=20 min | 4 | provider_outage |
| 19:40-20:30 | host probes | ap-tokyo eu-hetzner sa-east us-central | >=50 min | 10 | provider_outage |
| 22:05-22:15 | host probes | ap-tokyo us-central | >=10 min | 2 | provider_outage |
| 22:50-23:00 | host probes | ap-tokyo sa-east | >=10 min | 2 | provider_outage |
| 23:20-23:40 | host probes | ap-tokyo eu-hetzner sa-east us-central | >=20 min | 8 | provider_outage |

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

## Was the baseten API down on August 1, 2026?

Not by our measurements. No failure of baseten was seen from two or more regions at once. baseten's own status page opened 1 entry that day (self-reported, listed below).
- self-reported 23:57 UTC: Elevated inference 502s for a subset of models in a single US cluster (minor)

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

## Was the minimax API down on August 1, 2026?

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

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

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

## Was the sensenova API down on August 1, 2026?

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

| UTC | What failed | Regions | Duration (lower bound) | Failed probes | Verdict |
| --- | --- | --- | --- | --- | --- |
| 07:07-07:19 | host probes | ap-tokyo sa-east | >=12 min | 2 | unattributed |

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

## Was the yi-01ai API down on August 1, 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 |
| --- | --- | --- | --- | --- | --- |
| 10:45-11:05 | host probes | ap-tokyo sa-east | >=20 min | 4 | unattributed |
| 14:55-15:00 | host probes | ap-tokyo eu-hetzner | >=5 min | 2 | unattributed |

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

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