HomeIncidents
Data API

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.

UTCWhat failedRegionsDurationFailed probesVerdictError
10:20–10:20host probes3 of 4: Asia (Tokyo), South America (Santiago), US (Central)<5 min3provider outagetimeout
17:33–17:35host probes4 of 4: Asia (Tokyo), Europe (Germany), South America (Santiago), US (Central)≥2 min4provider outagetimeout
18:35–18:35host probes3 of 4: Asia (Tokyo), South America (Santiago), US (Central)<5 min3provider outagetimeout

Current sensenova API status

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.

UTCWhat failedRegionsDurationFailed probesVerdictError
18:10–18:13host probes2 of 4: Europe (Germany), US (Central)≥3 min2provider outagetimeout

Current ai21 API status

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.

UTCWhat failedRegionsDurationFailed probesVerdictError
08:50–09:00host probes2 of 4: Asia (Tokyo), US (Central)≥10 min2provider outagetimeout

Current iflytek API status

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:

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

Current OpenAI API status

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:

Current baseten API status

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:

Current nebius API status

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.

UTCWhat failedRegionsDurationFailed probesVerdictError
07:15–07:15host probes2 of 4: South America (Santiago), US (Central)<5 min2shared with 2 other provider(s) — not attributedtimeout

Current upstage API status

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.

· Last 72 hours ·

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