# AI API outages on September 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 Gemini API (Google) down on September 1, 2026?

Yes, measured. 2 outage(s) attributed to Google: requests to gemini-flash-lite-latest failed from up to 2 of 4 regions at once while no other provider was failing, first at 14:35 UTC, at least 5 minutes observed in total.

| UTC | What failed | Regions | Duration (lower bound) | Failed probes | Verdict |
| --- | --- | --- | --- | --- | --- |
| 14:35-14:35 | requests to gemini-flash-lite-latest | ap-tokyo sa-east | <5 min | 2 | provider_outage |
| 17:25-17:30 | requests to gemini-flash-lite-latest | sa-east us-central | >=5 min | 2 | provider_outage |

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

## Was the friendli API down on September 1, 2026?

Yes, measured. 1 outage(s) attributed to friendli: host probes failed from up to 3 of 4 regions at once while no other provider was failing, first at 23:00 UTC, each shorter than one 5-minute probe cycle.

| UTC | What failed | Regions | Duration (lower bound) | Failed probes | Verdict |
| --- | --- | --- | --- | --- | --- |
| 23:00-23:00 | host probes | ap-tokyo sa-east us-central | <5 min | 3 | provider_outage |

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

## Was the Claude API (Anthropic) down on September 1, 2026?

Not by our measurements. No failure of Anthropic was seen from two or more regions at once; 1 single-region failure(s) are not called an outage. Anthropic's own status page opened 3 entries that day (self-reported, listed below).
- self-reported 16:02 UTC: Degraded performance on Claude for Microsoft Office 365 (minor)
- self-reported 17:05 UTC: Degraded performance on platform.claude.com and Claude for Microsoft Office 365 (minor)
- self-reported 23:26 UTC: Delays in credit purchases (minor)

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

## Was the Cohere API down on September 1, 2026?

Not attributably. 1 multi-region failure(s) of Cohere coincided with failures of other providers, so the cause sat above Cohere and is not blamed on it. Cohere's own status page opened 1 entry that day (self-reported, listed below).

| UTC | What failed | Regions | Duration (lower bound) | Failed probes | Verdict |
| --- | --- | --- | --- | --- | --- |
| 14:55-14:58 | host probes | ap-tokyo eu-hetzner sa-east | >=3 min | 3 | unattributed |
- self-reported 15:41 UTC: Multiple Endpoint Disruptions (minor)

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

## Was the nebius API down on September 1, 2026?

Not by our measurements. No failure of nebius was seen from two or more regions at once. nebius's own status page opened 1 entry that day (self-reported, listed below).
- self-reported 16:11 UTC: Connectivity issues for newly created worker nodes (major)

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

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