# AI API outages on October 2, 2026 (UTC) Measured every 5 minutes from 4 regions. An outage is attributed to a provider only when it failed from 2+ regions at once and no other provider failed in the same minutes. ## Was the SambaNova API down on October 2, 2026? Yes, measured. 1 outage(s) attributed to SambaNova: host probes failed from up to 3 of 4 regions at once while no other provider was failing, first at 19:52 UTC, at least 30 minutes observed in total. SambaNova's status page lists nothing that day. | UTC | What failed | Regions | Duration (lower bound) | Failed probes | Verdict | | --- | --- | --- | --- | --- | --- | | 03:23-06:28 | host probes | ap-tokyo us-central | >=185 min | 33 | unattributed | | 06:43-08:43 | host probes | ap-tokyo us-central | >=120 min | 21 | unattributed | | 19:52-20:22 | host probes | eu-hetzner sa-east us-central | >=30 min | 17 | provider_outage | Live status now: https://llmlatency.dev/provider/sambanova ## Was the doubao API down on October 2, 2026? Yes, measured. 1 outage(s) attributed to doubao: host probes failed from up to 2 of 4 regions at once while no other provider was failing, first at 21:18 UTC, at least 11 minutes observed in total. | UTC | What failed | Regions | Duration (lower bound) | Failed probes | Verdict | | --- | --- | --- | --- | --- | --- | | 03:23-03:46 | host probes | ap-tokyo sa-east us-central | >=23 min | 6 | unattributed | | 04:13-05:08 | host probes | ap-tokyo us-central | >=55 min | 9 | unattributed | | 21:18-21:30 | host probes | ap-tokyo sa-east | >=11 min | 2 | provider_outage | Live status now: https://llmlatency.dev/provider/doubao ## Was the sensenova API down on October 2, 2026? Yes, measured. 1 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 22:30 UTC, at least 2 minutes observed in total. | UTC | What failed | Regions | Duration (lower bound) | Failed probes | Verdict | | --- | --- | --- | --- | --- | --- | | 03:51-04:02 | host probes | eu-hetzner us-central | >=10 min | 2 | unattributed | | 22:30-22:32 | host probes | ap-tokyo eu-hetzner sa-east us-central | >=2 min | 4 | provider_outage | Live status now: https://llmlatency.dev/provider/sensenova ## Was the OpenAI API down on October 2, 2026? Not by our measurements. No failure of OpenAI was seen from two or more regions at once; 5 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 16:03 UTC: Issues with data analysis and file creation in ChatGPT (minor) Live status now: https://llmlatency.dev/provider/openai ## Was the Gemini API (Google) down on October 2, 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. | UTC | What failed | Regions | Duration (lower bound) | Failed probes | Verdict | | --- | --- | --- | --- | --- | --- | | 04:57-05:17 | requests to gemini-flash-lite-latest | eu-hetzner us-central | >=20 min | 3 | unattributed | | 17:38-17:51 | requests to gemini-flash-lite-latest | ap-tokyo us-central | >=13 min | 2 | unattributed | Live status now: https://llmlatency.dev/provider/google ## Was the xAI API down on October 2, 2026? Not attributably. 2 multi-region failure(s) of xAI coincided with failures of other providers, so the cause sat above xAI and is not blamed on it. | UTC | What failed | Regions | Duration (lower bound) | Failed probes | Verdict | | --- | --- | --- | --- | --- | --- | | 03:51-04:03 | host probes | ap-tokyo us-central | >=12 min | 2 | unattributed | | 07:56-08:03 | host probes | ap-tokyo us-central | >=7 min | 2 | unattributed | Live status now: https://llmlatency.dev/provider/xai ## Was the nebius API down on October 2, 2026? Not by our measurements. No failure of nebius was seen from two or more regions at once; 14 single-region failure(s) are not called an outage. nebius's own status page opened 2 entries that day (self-reported, listed below). - self-reported 01:34 UTC: Compute VM creation and Object storage are partial unavailable (major) - self-reported 15:31 UTC: Issues with preempted Managed Kubernetes nodes in all regions (minor) Live status now: https://llmlatency.dev/provider/nebius ## Was the aleph-alpha API down on October 2, 2026? Not attributably. 1 multi-region failure(s) of aleph-alpha coincided with failures of other providers, so the cause sat above aleph-alpha and is not blamed on it. | UTC | What failed | Regions | Duration (lower bound) | Failed probes | Verdict | | --- | --- | --- | --- | --- | --- | | 03:46-04:28 | host probes | ap-tokyo us-central | >=42 min | 12 | unattributed | Live status now: https://llmlatency.dev/provider/aleph-alpha ## Was the baichuan API down on October 2, 2026? Not attributably. 1 multi-region failure(s) of baichuan coincided with failures of other providers, so the cause sat above baichuan and is not blamed on it. | UTC | What failed | Regions | Duration (lower bound) | Failed probes | Verdict | | --- | --- | --- | --- | --- | --- | | 15:55-16:30 | host probes | sa-east us-central | >=35 min | 6 | unattributed | Live status now: https://llmlatency.dev/provider/baichuan ## Was the deepinfra API down on October 2, 2026? Not attributably. 2 multi-region failure(s) of deepinfra coincided with failures of other providers, so the cause sat above deepinfra and is not blamed on it. | UTC | What failed | Regions | Duration (lower bound) | Failed probes | Verdict | | --- | --- | --- | --- | --- | --- | | 03:46-04:08 | host probes | ap-tokyo us-central | >=22 min | 6 | unattributed | | 07:23-08:38 | host probes | ap-tokyo us-central | >=75 min | 11 | unattributed | Live status now: https://llmlatency.dev/provider/deepinfra ## Was the friendli API down on October 2, 2026? Not attributably. 1 multi-region failure(s) of friendli coincided with failures of other providers, so the cause sat above friendli and is not blamed on it. | UTC | What failed | Regions | Duration (lower bound) | Failed probes | Verdict | | --- | --- | --- | --- | --- | --- | | 03:23-03:56 | host probes | ap-tokyo us-central | >=33 min | 5 | unattributed | Live status now: https://llmlatency.dev/provider/friendli ## Was the glm API down on October 2, 2026? Not attributably. 1 multi-region failure(s) of glm coincided with failures of other providers, so the cause sat above glm and is not blamed on it. | UTC | What failed | Regions | Duration (lower bound) | Failed probes | Verdict | | --- | --- | --- | --- | --- | --- | | 03:56-03:58 | host probes | ap-tokyo us-central | >=2 min | 2 | unattributed | Live status now: https://llmlatency.dev/provider/glm ## Was the minimax API down on October 2, 2026? Not attributably. 3 multi-region failure(s) of minimax coincided with failures of other providers, so the cause sat above minimax and is not blamed on it. | UTC | What failed | Regions | Duration (lower bound) | Failed probes | Verdict | | --- | --- | --- | --- | --- | --- | | 03:23-03:58 | host probes | ap-tokyo us-central | >=35 min | 7 | unattributed | | 04:18-04:21 | host probes | ap-tokyo us-central | >=3 min | 2 | unattributed | | 07:13-08:53 | host probes | ap-tokyo us-central | >=100 min | 12 | unattributed | Live status now: https://llmlatency.dev/provider/minimax ## Was the nscale API down on October 2, 2026? Not attributably. 2 multi-region failure(s) of nscale coincided with failures of other providers, so the cause sat above nscale and is not blamed on it. | UTC | What failed | Regions | Duration (lower bound) | Failed probes | Verdict | | --- | --- | --- | --- | --- | --- | | 03:23-03:56 | host probes | ap-tokyo us-central | >=33 min | 8 | unattributed | | 07:33-08:03 | host probes | ap-tokyo us-central | >=30 min | 6 | unattributed | Live status now: https://llmlatency.dev/provider/nscale ## Was the stepfun API down on October 2, 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. | UTC | What failed | Regions | Duration (lower bound) | Failed probes | Verdict | | --- | --- | --- | --- | --- | --- | | 03:48-03:56 | host probes | ap-tokyo us-central | >=8 min | 2 | unattributed | Live status now: https://llmlatency.dev/provider/stepfun ## Was the targon API down on October 2, 2026? Not attributably. 1 multi-region failure(s) of targon coincided with failures of other providers, so the cause sat above targon and is not blamed on it. | UTC | What failed | Regions | Duration (lower bound) | Failed probes | Verdict | | --- | --- | --- | --- | --- | --- | | 03:58-04:21 | host probes | ap-tokyo us-central | >=23 min | 3 | unattributed | Live status now: https://llmlatency.dev/provider/targon ## Was the yi-01ai API down on October 2, 2026? Not attributably. 1 multi-region failure(s) of yi-01ai coincided with failures of other providers, so the cause sat above yi-01ai and is not blamed on it. | UTC | What failed | Regions | Duration (lower bound) | Failed probes | Verdict | | --- | --- | --- | --- | --- | --- | | 07:50-08:13 | host probes | ap-tokyo sa-east us-central | >=24 min | 5 | unattributed | Live status now: https://llmlatency.dev/provider/yi-01ai Source: https://llmlatency.dev/incidents/2026-10-02 ยท CC BY 4.0