HomeIncidents
Data API

AI API outages on November 16, 2026

UTC day · measured every 5 minutes from 4 regions · method

On November 16, 2026 (UTC) no AI API outage could be attributed to a provider: nothing failed from two or more regions at once without other providers failing alongside. Providers’ own status pages opened 3 entries (Anthropic, replicate).

This page is history. Is it down right now?

Live status, updated every 30 minutes: Claude API (Anthropic), Gemini API (Google), replicate API, sensenova API · all AI APIs, last 72 hours

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

Not by our measurements. No failure of Anthropic was seen from two or more regions at once. Anthropic’s own status page opened 2 entries that day (self-reported, listed below).

Self-reported on Anthropic’s status page, not verified by our probes:

Current Claude API (Anthropic) status

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

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

UTCWhat failedRegionsDurationFailed probesVerdictError
12:22–12:24requests to gemini-flash-lite-latest2 of 4: Asia (Tokyo), Europe (Germany)≥2 min2shared with 1 other provider(s) — not attributedtimeout

Current Gemini API (Google) status

Was the replicate API down on November 16, 2026?

Not attributably. 1 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).

UTCWhat failedRegionsDurationFailed probesVerdictError
12:06–12:31host probes3 of 4: Europe (Germany), South America (Santiago), US (Central)≥25 min5shared with 1 other provider(s) — not attributedhttp 502

Self-reported on replicate’s status page, not verified by our probes:

Current replicate API status

Was the sensenova API down on November 16, 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.

UTCWhat failedRegionsDurationFailed probesVerdictError
17:09–17:11host probes3 of 4: Asia (Tokyo), South America (Santiago), US (Central)≥2 min3shared with 1 other provider(s) — not attributedtimeout

Current sensenova API status

35 single-region failure(s) were also recorded that day (iflytek 9, doubao 7, google 4, baichuan 4, hyperbolic 2, sambanova 2, friendli 1, featherless 1, baseten 1, stepfun 1). A failure seen from one region cannot be separated from a problem on that network path, so none of them is called an outage.

How is an outage told apart from a network problem?

Each provider is probed every five minutes from 4 independent regions. A failure is attributed to the provider only when it is seen from two or more regions at once and no other provider fails in the same minutes; a failure shared with other providers has a cause above all of them and is not blamed on anyone. Durations are lower bounds: we see the first and last failed probe, not the real start and end. Status-page entries are the provider’s own words, shown next to the measurement, not instead of it.

· Last 72 hours

Machine-readable: incidents.json · Licence: CC BY 4.0