AI API outages on September 30, 2026
UTC day · measured every 5 minutes from 4 regions · method
On September 30, 2026 (UTC) our probes attributed 4 outage(s) to 3 provider(s): friendli API: 2; Gemini API (Google): 1; sarvam API: 1. Providers’ own status pages opened 3 entries (OpenAI).
This page is history. Is it down right now?
Live status, updated every 30 minutes: friendli API, Gemini API (Google), sarvam API, OpenAI API, SambaNova API · all AI APIs, last 72 hours
Was the friendli API down on September 30, 2026?
Yes, measured. 2 outage(s) attributed to friendli: host probes failed from up to 2 of 4 regions at once while no other provider was failing, first at 11:49 UTC, at least 2 minutes observed in total.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 11:49–11:50 | host probes | 2 of 4: Asia (Tokyo), South America (São Paulo) | ≥1 min | 2 | provider outage | timeout |
| 12:19–12:20 | host probes | 2 of 4: South America (São Paulo), US (Central) | ≥1 min | 2 | provider outage | timeout |
Is the friendli API down right now? Live status →
Was the Gemini API (Google) down on September 30, 2026?
Yes, measured. 1 outage(s) attributed to Google: requests to gemini-flash-lite-latest failed from up to 2 of 4 regions at once while no other provider was failing, first at 07:55 UTC, at least 8 minutes observed in total.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 06:05–06:05 | requests to gemini-flash-lite-latest | 3 of 4: Asia (Tokyo), South America (São Paulo), US (Central) | <5 min | 3 | shared with 1 other provider(s) — not attributed | timeout |
| 07:55–08:04 | requests to gemini-flash-lite-latest | 2 of 4: Europe (Germany), South America (São Paulo) | ≥8 min | 2 | provider outage | timeout |
Is the Gemini API (Google) down right now? Live status →
Was the sarvam API down on September 30, 2026?
Yes, measured. 1 outage(s) attributed to sarvam: host probes failed from up to 3 of 4 regions at once while no other provider was failing, first at 20:07 UTC, at least 3 minutes observed in total. At least once sarvam’s own host answered with an HTTP 5xx.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 20:07–20:10 | host probes | 3 of 4: Europe (Germany), South America (São Paulo), US (Central) | ≥3 min | 3 | provider outage | http 502; timeout |
Is the sarvam API down right now? Live status →
Was the OpenAI API down on September 30, 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 3 entries that day (self-reported, listed below).
Self-reported on OpenAI’s status page, not verified by our probes:
- minor Elevated errors in ChatGPT Space Pages · resolved — UTC
- minor Elevated error rates for ChatGPT Pro and Plus users · resolved Sep 30, 13:23 UTC
- minor Elevated latency for some API requests · resolved Sep 30, 20:35 UTC
Is the OpenAI API down right now? Live status →
Was the SambaNova API down on September 30, 2026?
Not attributably. 1 multi-region failure(s) of SambaNova coincided with failures of other providers, so the cause sat above SambaNova and is not blamed on it. SambaNova’s status page lists nothing that day.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 07:00–07:00 | host probes | 2 of 4: Europe (Germany), US (Central) | <5 min | 2 | shared with 1 other provider(s) — not attributed | timeout |
Is the SambaNova API down right now? Live status →
50 single-region failure(s) were also recorded that day (yi-01ai 18, google 9, doubao 5, iflytek 5, sensenova 4, stepfun 3, hunyuan 3, sarvam 1, sambanova 1, 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.
Machine-readable: incidents.json · Licence: CC BY 4.0