HomeIncidents
Data API

AI API outages on September 29, 2026

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

On September 29, 2026 (UTC) our probes attributed 5 outage(s) to 4 provider(s): doubao API: 2; iflytek API: 1; inference-net API: 1; kimi API: 1. Providers’ own status pages opened 6 entries (OpenAI, Anthropic, TypeSafe, baseten).

This page is history. Is it down right now?

Live status, updated every 30 minutes: doubao API, iflytek API, inference-net API, kimi API, OpenAI API, Claude API (Anthropic) · all AI APIs, last 72 hours

Was the doubao API down on September 29, 2026?

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

UTCWhat failedRegionsDurationFailed probesVerdictError
03:55–04:05host probes2 of 4: Asia (Tokyo), South America (São Paulo)≥10 min3shared with 1 other provider(s) — not attributedtimeout
08:30–08:35host probes3 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo)≥5 min4provider outagetimeout
20:30–20:31host probes2 of 4: Europe (Germany), South America (São Paulo)<5 min2provider outagetimeout

Current doubao API status

Was the iflytek API down on September 29, 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 13:15 UTC, at least 6 minutes observed in total.

UTCWhat failedRegionsDurationFailed probesVerdictError
08:50–09:05host probes2 of 4: Asia (Tokyo), South America (São Paulo)≥15 min3shared with 4 other provider(s) — not attributedtimeout
09:30–09:55host probes2 of 4: Asia (Tokyo), South America (São Paulo)≥25 min4shared with 6 other provider(s) — not attributedtimeout
13:15–13:21host probes2 of 4: Asia (Tokyo), Europe (Germany)≥6 min2provider outagetimeout
14:55–15:10host probes3 of 4: Asia (Tokyo), South America (São Paulo), US (Central)≥15 min3shared with 3 other provider(s) — not attributedtimeout

Current iflytek API status

Was the inference-net API down on September 29, 2026?

Yes, measured. 1 outage(s) attributed to inference-net: host probes failed from up to 4 of 4 regions at once while no other provider was failing, first at 22:00 UTC, at least 11 minutes observed in total. At least once inference-net’s own host answered with an HTTP 5xx.

UTCWhat failedRegionsDurationFailed probesVerdictError
22:00–22:10host probes4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central)≥11 min12provider outagehttp 500

Current inference-net API status

Was the kimi API down on September 29, 2026?

Yes, measured. 1 outage(s) attributed to kimi: host probes failed from up to 4 of 4 regions at once while no other provider was failing, first at 23:20 UTC, at least 36 minutes observed in total. At least once kimi’s own host answered with an HTTP 5xx.

UTCWhat failedRegionsDurationFailed probesVerdictError
23:20–23:55host probes4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central)≥36 min32provider outagehttp 521

Current kimi API status

Was the OpenAI API down on September 29, 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 2 entries that day (self-reported, listed below).

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

  • notice Support available via email · resolved Sep 29, 23:18 UTC
  • minor Elevated errors across ChatGPT, Codex, and the API including the Agents API · resolved Sep 29, 23:14 UTC

Current OpenAI API status

Was the Claude API (Anthropic) down on September 29, 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 TypeSafe API down on September 29, 2026?

Not by our measurements. No failure of TypeSafe was seen from two or more regions at once; 1 single-region failure(s) are not called an outage. TypeSafe’s own status page opened 1 entry that day (self-reported, listed below).

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

Current TypeSafe API status

Was the Gemini API (Google) down on September 29, 2026?

Not attributably. 2 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:35–12:45requests to gemini-flash-lite-latest4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central)≥9 min4shared with 1 other provider(s) — not attributedtimeout
14:16–14:25requests to gemini-flash-lite-latest2 of 4: Europe (Germany), US (Central)≥9 min2shared with 2 other provider(s) — not attributedtimeout

Current Gemini API (Google) status

Was the baseten API down on September 29, 2026?

Not by our measurements. No failure of baseten was seen from two or more regions at once. baseten’s own status page opened 2 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 baichuan API down on September 29, 2026?

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

UTCWhat failedRegionsDurationFailed probesVerdictError
05:55–05:56host probes2 of 4: Asia (Tokyo), Europe (Germany)<5 min2shared with 2 other provider(s) — not attributed[Errno 101] Network is unreachable; timeout
07:20–07:45host probes2 of 4: Asia (Tokyo), South America (São Paulo)≥25 min3shared with 2 other provider(s) — not attributed[Errno 101] Network is unreachable; timeout
08:50–08:55host probes2 of 4: Asia (Tokyo), South America (São Paulo)≥5 min2shared with 4 other provider(s) — not attributed[Errno 101] Network is unreachable; timeout
12:45–12:50host probes2 of 4: Asia (Tokyo), US (Central)≥5 min2shared with 1 other provider(s) — not attributed[Errno 101] Network is unreachable; timeout
14:00–14:10host probes3 of 4: Asia (Tokyo), South America (São Paulo), US (Central)≥10 min3shared with 5 other provider(s) — not attributed[Errno 101] Network is unreachable; timeout
15:25–15:55host probes3 of 4: Asia (Tokyo), Europe (Germany), US (Central)≥30 min6shared with 2 other provider(s) — not attributed[Errno 101] Network is unreachable; timeout

Current baichuan API status

Was the sarvam API down on September 29, 2026?

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

UTCWhat failedRegionsDurationFailed probesVerdictError
18:00–18:00host probes2 of 4: South America (São Paulo), US (Central)<5 min2shared with 1 other provider(s) — not attributedhttp 502; timeout

Current sarvam API status

Was the sensenova API down on September 29, 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
09:25–09:30host probes2 of 4: South America (São Paulo), US (Central)≥5 min2shared with 4 other provider(s) — not attributedtimeout

Current sensenova API status

Was the stepfun API down on September 29, 2026?

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

UTCWhat failedRegionsDurationFailed probesVerdictError
06:00–06:10host probes2 of 4: South America (São Paulo), US (Central)≥10 min3shared with 2 other provider(s) — not attributedtimeout

Current stepfun API status

81 single-region failure(s) were also recorded that day (baichuan 20, iflytek 15, doubao 10, sensenova 9, google 7, aleph-alpha 4, nebius 3, stepfun 3, cerebras 1, perplexity 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