# AI API outages on November 17, 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 sensenova API down on November 17, 2026?

Yes, measured. 6 outage(s) attributed to sensenova: host probes failed from up to 4 of 4 regions at once while no other provider was failing, first at 00:15 UTC, at least 15 minutes observed in total.

| UTC | What failed | Regions | Duration (lower bound) | Failed probes | Verdict |
| --- | --- | --- | --- | --- | --- |
| 00:15-00:20 | host probes | ap-tokyo sa-west us-central | >=5 min | 5 | provider_outage |
| 02:20-02:20 | host probes | ap-tokyo us-central | <5 min | 2 | provider_outage |
| 03:20-03:23 | host probes | ap-tokyo eu-hetzner us-central | >=3 min | 3 | provider_outage |
| 20:20-20:23 | host probes | eu-hetzner sa-west | >=3 min | 2 | provider_outage |
| 21:23-21:25 | host probes | ap-tokyo eu-hetzner sa-west us-central | >=2 min | 4 | provider_outage |
| 23:23-23:25 | host probes | ap-tokyo eu-hetzner sa-west us-central | >=2 min | 4 | provider_outage |

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

## Was the Gemini API (Google) down on November 17, 2026?

Yes, measured. 1 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 09:45 UTC, at least 10 minutes observed in total.

| UTC | What failed | Regions | Duration (lower bound) | Failed probes | Verdict |
| --- | --- | --- | --- | --- | --- |
| 09:45-09:55 | requests to gemini-flash-lite-latest | ap-tokyo sa-west | >=10 min | 2 | provider_outage |

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

## Was the baichuan API down on November 17, 2026?

Yes, measured. 1 outage(s) attributed to baichuan: host probes failed from up to 2 of 4 regions at once while no other provider was failing, first at 11:43 UTC, at least 12 minutes observed in total.

| UTC | What failed | Regions | Duration (lower bound) | Failed probes | Verdict |
| --- | --- | --- | --- | --- | --- |
| 11:43-11:55 | host probes | ap-tokyo eu-hetzner | >=12 min | 2 | provider_outage |

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

## Was the Claude API (Anthropic) down on November 17, 2026?

Not by our measurements. No failure of Anthropic was seen from two or more regions at once. Anthropic's own status page opened 1 entry that day (self-reported, listed below).
- self-reported 18:55 UTC: Some users unable to sign in with Apple on claude.ai and the Claude iOS app (major)

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

## Was the Cerebras API down on November 17, 2026?

Not by our measurements. No failure of Cerebras was seen from two or more regions at once. Cerebras's own status page opened 1 entry that day (self-reported, listed below).
- self-reported 08:00 UTC: Partial Service Disruption (none)

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

## Was the OpenAI API down on November 17, 2026?

Not by our measurements. No failure of OpenAI was seen from two or more regions at once. OpenAI's own status page opened 1 entry that day (self-reported, listed below).
- self-reported 17:46 UTC: Costs API data is delayed (minor)

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

## Was the replicate API down on November 17, 2026?

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

| UTC | What failed | Regions | Duration (lower bound) | Failed probes | Verdict |
| --- | --- | --- | --- | --- | --- |
| 13:13-13:20 | host probes | eu-hetzner sa-west | >=7 min | 2 | unattributed |
| 14:10-14:10 | host probes | sa-west us-central | <5 min | 2 | unattributed |
| 14:38-14:48 | host probes | ap-tokyo eu-hetzner sa-west us-central | >=10 min | 6 | unattributed |
- self-reported 15:02 UTC: Errors and stalled predictions on some models (minor)

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

## Was the iflytek API down on November 17, 2026?

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

| UTC | What failed | Regions | Duration (lower bound) | Failed probes | Verdict |
| --- | --- | --- | --- | --- | --- |
| 04:50-05:10 | host probes | ap-tokyo us-central | >=20 min | 5 | unattributed |
| 15:20-15:33 | host probes | ap-tokyo eu-hetzner sa-west | >=13 min | 3 | unattributed |

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

Source: https://llmlatency.dev/incidents/2026-11-17 · CC BY 4.0
