# AI API outages on October 19, 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 doubao API down on October 19, 2026?

Yes, measured. 5 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 03:50 UTC, at least 39 minutes observed in total.

| UTC | What failed | Regions | Duration (lower bound) | Failed probes | Verdict |
| --- | --- | --- | --- | --- | --- |
| 01:30-01:41 | host probes | eu-hetzner us-central | >=11 min | 2 | unattributed |
| 02:06-02:10 | host probes | eu-hetzner sa-east | >=4 min | 2 | unattributed |
| 03:50-03:56 | host probes | eu-hetzner sa-east | >=6 min | 2 | provider_outage |
| 05:11-05:15 | host probes | eu-hetzner us-central | >=4 min | 2 | provider_outage |
| 06:00-06:00 | host probes | ap-tokyo sa-east | <5 min | 2 | provider_outage |
| 06:46-07:05 | host probes | eu-hetzner us-central | >=19 min | 3 | provider_outage |
| 08:00-08:10 | host probes | ap-tokyo sa-east us-central | >=10 min | 3 | provider_outage |
| 08:26-08:35 | host probes | eu-hetzner us-central | >=9 min | 2 | unattributed |
| 09:45-10:01 | host probes | ap-tokyo eu-hetzner us-central | >=16 min | 3 | unattributed |
| 11:55-12:01 | host probes | ap-tokyo eu-hetzner sa-east us-central | >=6 min | 5 | unattributed |
| 12:25-12:36 | host probes | ap-tokyo eu-hetzner us-central | >=11 min | 4 | unattributed |
| 13:40-14:01 | host probes | eu-hetzner sa-east | >=21 min | 5 | unattributed |
| 14:45-15:05 | host probes | ap-tokyo sa-east | >=20 min | 4 | unattributed |
| 15:56-16:25 | host probes | ap-tokyo eu-hetzner sa-east us-central | >=29 min | 5 | unattributed |

Live status now: https://llmlatency.dev/provider/doubao

## Was the Gemini API (Google) down on October 19, 2026?

Yes, measured. 2 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 05:30 UTC, each shorter than one 5-minute probe cycle.

| UTC | What failed | Regions | Duration (lower bound) | Failed probes | Verdict |
| --- | --- | --- | --- | --- | --- |
| 05:30-05:30 | requests to gemini-flash-lite-latest | sa-east us-central | <5 min | 2 | provider_outage |
| 21:00-21:01 | requests to gemini-flash-lite-latest | ap-tokyo eu-hetzner sa-east us-central | <5 min | 4 | unattributed |
| 21:20-21:20 | requests to gemini-flash-lite-latest | ap-tokyo eu-hetzner sa-east us-central | <5 min | 4 | unattributed |
| 22:20-22:20 | requests to gemini-flash-lite-latest | sa-east us-central | <5 min | 2 | provider_outage |

Live status now: https://llmlatency.dev/provider/google

## Was the stepfun API down on October 19, 2026?

Yes, measured. 1 outage(s) attributed to stepfun: host probes failed from up to 2 of 4 regions at once while no other provider was failing, first at 23:15 UTC, each shorter than one 5-minute probe cycle.

| UTC | What failed | Regions | Duration (lower bound) | Failed probes | Verdict |
| --- | --- | --- | --- | --- | --- |
| 23:15-23:15 | host probes | ap-tokyo us-central | <5 min | 2 | provider_outage |

Live status now: https://llmlatency.dev/provider/stepfun

## Was the writer API down on October 19, 2026?

Yes, measured. 1 outage(s) attributed to writer: host probes failed from up to 2 of 4 regions at once while no other provider was failing, first at 05:35 UTC, each shorter than one 5-minute probe cycle.

| UTC | What failed | Regions | Duration (lower bound) | Failed probes | Verdict |
| --- | --- | --- | --- | --- | --- |
| 05:35-05:35 | host probes | ap-tokyo us-central | <5 min | 2 | provider_outage |

Live status now: https://llmlatency.dev/provider/writer

## Was the yi-01ai API down on October 19, 2026?

Yes, measured. 1 outage(s) attributed to yi-01ai: host probes failed from up to 2 of 4 regions at once while no other provider was failing, first at 00:50 UTC, at least 10 minutes observed in total.

| UTC | What failed | Regions | Duration (lower bound) | Failed probes | Verdict |
| --- | --- | --- | --- | --- | --- |
| 00:50-01:00 | host probes | ap-tokyo sa-east | >=10 min | 2 | provider_outage |
| 13:00-13:30 | host probes | ap-tokyo sa-east | >=30 min | 5 | unattributed |
| 15:25-16:20 | host probes | ap-tokyo sa-east | >=55 min | 10 | unattributed |

Live status now: https://llmlatency.dev/provider/yi-01ai

## Was the OpenAI API down on October 19, 2026?

Not by our measurements. No failure of OpenAI was seen from two or more regions at once. OpenAI's own status page opened 1 entry that day (self-reported, listed below).
- self-reported 13:31 UTC: File Download errors (minor)

Live status now: https://llmlatency.dev/provider/openai

Source: https://llmlatency.dev/incidents/2026-10-19 · CC BY 4.0