AI API outages on November 18, 2026
UTC day · measured every 5 minutes from 4 regions · method
On November 18, 2026 (UTC) our probes attributed 5 outage(s) to 3 provider(s): sensenova API: 3; ai21 API: 1; iflytek API: 1. Providers’ own status pages opened 6 entries (Anthropic, OpenAI, baseten, nebius).
This page is history. Is it down right now?
Live status, updated every 30 minutes: sensenova API, ai21 API, iflytek API, Claude API (Anthropic), OpenAI API, baseten API · all AI APIs, last 72 hours
Was the sensenova API down on November 18, 2026?
Yes, measured. 3 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 10:20 UTC, at least 2 minutes observed in total.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 10:20–10:20 | host probes | 3 of 4: Asia (Tokyo), South America (Santiago), US (Central) | <5 min | 3 | provider outage | timeout |
| 17:33–17:35 | host probes | 4 of 4: Asia (Tokyo), Europe (Germany), South America (Santiago), US (Central) | ≥2 min | 4 | provider outage | timeout |
| 18:35–18:35 | host probes | 3 of 4: Asia (Tokyo), South America (Santiago), US (Central) | <5 min | 3 | provider outage | timeout |
Was the ai21 API down on November 18, 2026?
Yes, measured. 1 outage(s) attributed to ai21: host probes failed from up to 2 of 4 regions at once while no other provider was failing, first at 18:10 UTC, at least 3 minutes observed in total. ai21’s status page lists nothing that day.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 18:10–18:13 | host probes | 2 of 4: Europe (Germany), US (Central) | ≥3 min | 2 | provider outage | timeout |
Was the iflytek API down on November 18, 2026?
Yes, measured. 1 outage(s) attributed to iflytek: host probes failed from up to 2 of 4 regions at once while no other provider was failing, first at 08:50 UTC, at least 10 minutes observed in total.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 08:50–09:00 | host probes | 2 of 4: Asia (Tokyo), US (Central) | ≥10 min | 2 | provider outage | timeout |
Was the Claude API (Anthropic) down on November 18, 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 on Anthropic’s status page, not verified by our probes:
- minor Elevated errors affecting the Google Docs connector · resolved Nov 18, 01:44 UTC
Current Claude API (Anthropic) status
Was the OpenAI API down on November 18, 2026?
Not by our measurements. No failure of OpenAI was seen from two or more regions at once; 1 single-region failure(s) are not called an outage. OpenAI’s own status page opened 1 entry that day (self-reported, listed below).
Self-reported on OpenAI’s status page, not verified by our probes:
- minor Elevated conversation errors for Free and Go users · resolved Nov 18, 14:13 UTC
Was the baseten API down on November 18, 2026?
Not by our measurements. No failure of baseten was seen from two or more regions at once. baseten’s own status page opened 3 entries that day (self-reported, listed below).
Self-reported on baseten’s status page, not verified by our probes:
- minor Elevated TTFT on Kimi K3 on MAPIs · resolved Nov 18, 02:32 UTC
- minor Elevated errors on GLM-5.3-Flash on Model APIs · resolved Nov 18, 16:05 UTC
- major Outage on app.baseten.co. Inference is not affected · resolved Nov 18, 18:19 UTC
Was the nebius API down on November 18, 2026?
Not by our measurements. No failure of nebius was seen from two or more regions at once; 2 single-region failure(s) are not called an outage. nebius’s own status page opened 1 entry that day (self-reported, listed below).
Self-reported on nebius’s status page, not verified by our probes:
- major Token Factory: errors on GLM-5.2 model requests in uk-south1 · resolved Nov 19, 19:56 UTC
Was the upstage API down on November 18, 2026?
Not attributably. 1 multi-region failure(s) of upstage coincided with failures of other providers, so the cause sat above upstage and is not blamed on it.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 07:15–07:15 | host probes | 2 of 4: South America (Santiago), US (Central) | <5 min | 2 | shared with 2 other provider(s) — not attributed | timeout |
42 single-region failure(s) were also recorded that day (iflytek 7, baichuan 7, doubao 4, stepfun 4, aleph-alpha 3, tencent-tokenhub 2, nebius 2, friendli 2, ai21 2, openai 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.
Previous: Nov 17 · Last 72 hours · Next: Nov 19
Machine-readable: incidents.json · Licence: CC BY 4.0