HomeIncidents
Data API

AI API outages on November 12, 2026

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

On November 12, 2026 (UTC) our probes attributed 9 outage(s) to 3 provider(s): Gemini API (Google): 7; aleph-alpha API: 1; sensenova API: 1. Providers’ own status pages opened 5 entries (OpenAI, Anthropic, baseten, replicate).

This page is history. Is it down right now?

Live status, updated every 30 minutes: Gemini API (Google), aleph-alpha API, sensenova API, OpenAI API, Claude API (Anthropic), baseten API · all AI APIs, last 72 hours

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

Yes, measured. 7 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 07:20 UTC, at least 14 minutes observed in total. At least once Google’s own host answered with an HTTP 5xx.

UTCWhat failedRegionsDurationFailed probesVerdictError
07:20–07:25requests to gemini-flash-lite-latest2 of 4: Europe (Germany), US (Central)≥4 min2provider outagetimeout
11:05–11:05requests to gemini-flash-lite-latest2 of 4: South America (Santiago), US (Central)<5 min2provider outagehttp 503
16:22–16:25requests to gemini-flash-lite-latest2 of 4: Europe (Germany), US (Central)≥3 min2provider outagehttp 503; timeout
16:42–16:45requests to gemini-flash-lite-latest2 of 4: Asia (Tokyo), Europe (Germany)≥3 min2provider outagetimeout
17:22–17:25requests to gemini-flash-lite-latest3 of 4: Europe (Germany), South America (Santiago), US (Central)≥3 min3provider outagetimeout
17:45–17:45requests to gemini-flash-lite-latest2 of 4: Asia (Tokyo), US (Central)<5 min2provider outagetimeout
18:05–18:05requests to gemini-flash-lite-latest2 of 4: Asia (Tokyo), US (Central)<5 min2provider outagetimeout

Current Gemini API (Google) status

Was the aleph-alpha API down on November 12, 2026?

Yes, measured. 1 outage(s) attributed to aleph-alpha: host probes failed from up to 4 of 4 regions at once while no other provider was failing, first at 04:00 UTC, each shorter than one 5-minute probe cycle. At least once aleph-alpha’s own host answered with an HTTP 5xx.

UTCWhat failedRegionsDurationFailed probesVerdictError
04:00–04:00host probes4 of 4: Asia (Tokyo), Europe (Germany), South America (Santiago), US (Central)<5 min4provider outagehttp 503

Current aleph-alpha API status

Was the sensenova API down on November 12, 2026?

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

UTCWhat failedRegionsDurationFailed probesVerdictError
06:15–06:15host probes3 of 4: Asia (Tokyo), South America (Santiago), US (Central)<5 min3provider outagetimeout
20:07–20:10host probes2 of 4: Europe (Germany), US (Central)≥3 min2shared with 1 other provider(s) — not attributedtimeout

Current sensenova API status

Was the OpenAI API down on November 12, 2026?

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

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

  • minor GPT-image-2.5 and 2.6 Sunburst & Flare High error rate · resolved Nov 12, 09:25 UTC
  • minor Elevated errors affecting the Microsoft 365 connector · resolved Nov 14, 00:18 UTC

Current OpenAI API status

Was the Claude API (Anthropic) down on November 12, 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 1 entry 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 baseten API down on November 12, 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 on baseten’s status page, not verified by our probes:

Current baseten API status

Was the replicate API down on November 12, 2026?

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

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

Current replicate API status

25 single-region failure(s) were also recorded that day (google 11, featherless 5, sambanova 2, iflytek 2, friendli 1, deepseek 1, sarvam 1, anthropic 1, qwencloud 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