F
Outage recap · Fireworks

Fireworks AI outage — November 3, 2026

On November 3, 2026, Fireworks AI had 8 reported incidents on Fireworks's official status page. Below is what was reported — impact, timing, and the AI services the same upstream outage could affect.

Service Degradation for GLM 5.3

minor
Started
Nov 3, 3:47 AM EST
Resolved
Nov 3, 11:52 PM EST
Duration
20h 5m

Fireworks's updates (2)

  1. investigating · Nov 3, 3:47 AM EST

    We are seeing impacted performance for GLM 5.3. We are actively investigating.

  2. resolved · Nov 3, 11:52 PM EST

    We've resolved the incident and the affected service is now operational.

What our checks recorded

We checked Fireworks AI 241 times from Fireworks's start time to its resolution, once every five minutes. Every one of them reached Fireworks AI's site, so this incident did not show up as a failed page load. Our check loads the public site; it cannot see an API error or a broken feature. Median response time was 435 ms, against 443 ms over the 24 hours before. Fireworks posted the incident at Nov 3, 3:47 AM EST.

Updates are Fireworks's own words from its status page (status: resolved); we never add an inferred cause.

Service Degradation for Kimi K3

minor
Started
Nov 3, 4:50 AM EST
Resolved
Nov 3, 5:04 AM EST
Duration
14 min

Fireworks's updates (2)

  1. investigating · Nov 3, 4:50 AM EST

    We are seeing impacted performance for Kimi K3. We are actively investigating.

  2. resolved · Nov 3, 5:04 AM EST

    We've resolved the incident and the affected service is now operational.

What our checks recorded

We checked Fireworks AI 2 times from Fireworks's start time to its resolution, once every five minutes. Every one of them reached Fireworks AI's site, so this incident did not show up as a failed page load. Our check loads the public site; it cannot see an API error or a broken feature. Median response time was 186 ms, against 445 ms over the 24 hours before. Fireworks posted the incident at Nov 3, 4:50 AM EST.

Updates are Fireworks's own words from its status page (status: resolved); we never add an inferred cause.

Service Degradation for Kimi K3 US

minor
Started
Nov 3, 5:07 AM EST
Resolved
Nov 3, 5:16 AM EST
Duration
9 min

Fireworks's updates (2)

  1. investigating · Nov 3, 5:07 AM EST

    We are seeing impacted performance for Kimi K3 US. We are actively investigating.

  2. resolved · Nov 3, 5:16 AM EST

    We've resolved the incident and the affected service is now operational.

What our checks recorded

We checked Fireworks AI 2 times from Fireworks's start time to its resolution, once every five minutes. Every one of them reached Fireworks AI's site, so this incident did not show up as a failed page load. Our check loads the public site; it cannot see an API error or a broken feature. Median response time was 341 ms, against 444 ms over the 24 hours before. Fireworks posted the incident at Nov 3, 5:07 AM EST.

Updates are Fireworks's own words from its status page (status: resolved); we never add an inferred cause.

Service Degradation for Kimi K3 US

minor
Started
Nov 3, 5:48 AM EST
Resolved
Nov 3, 6:03 AM EST
Duration
15 min

Fireworks's updates (2)

  1. investigating · Nov 3, 5:48 AM EST

    We are seeing impacted performance for Kimi K3 US. We are actively investigating.

  2. resolved · Nov 3, 6:03 AM EST

    We've resolved the incident and the affected service is now operational.

What our checks recorded

We checked Fireworks AI 3 times from Fireworks's start time to its resolution, once every five minutes. Every one of them reached Fireworks AI's site, so this incident did not show up as a failed page load. Our check loads the public site; it cannot see an API error or a broken feature. Median response time was 181 ms, against 440 ms over the 24 hours before. Fireworks posted the incident at Nov 3, 5:48 AM EST.

Updates are Fireworks's own words from its status page (status: resolved); we never add an inferred cause.

Service Degradation for Kimi K3 US

minor
Started
Nov 3, 7:39 AM EST
Resolved
Nov 3, 7:50 AM EST
Duration
11 min

Fireworks's updates (2)

  1. investigating · Nov 3, 7:39 AM EST

    We are seeing impacted performance for Kimi K3 US. We are actively investigating.

  2. resolved · Nov 3, 7:50 AM EST

    We've resolved the incident and the affected service is now operational.

What our checks recorded

We checked Fireworks AI 2 times from Fireworks's start time to its resolution, once every five minutes. Every one of them reached Fireworks AI's site, so this incident did not show up as a failed page load. Our check loads the public site; it cannot see an API error or a broken feature. Median response time was 118 ms, against 438 ms over the 24 hours before. Fireworks posted the incident at Nov 3, 7:39 AM EST.

Updates are Fireworks's own words from its status page (status: resolved); we never add an inferred cause.

Service Degradation for Kimi K3 US

minor
Started
Nov 3, 8:32 AM EST
Resolved
Nov 3, 10:14 AM EST
Duration
1h 42m

Fireworks's updates (2)

  1. investigating · Nov 3, 8:32 AM EST

    We are seeing impacted performance for Kimi K3 US. We are actively investigating.

  2. resolved · Nov 3, 10:14 AM EST

    We've resolved the incident and the affected service is now operational.

What our checks recorded

We checked Fireworks AI 20 times from Fireworks's start time to its resolution, once every five minutes. Every one of them reached Fireworks AI's site, so this incident did not show up as a failed page load. Our check loads the public site; it cannot see an API error or a broken feature. Median response time was 405 ms, against 438 ms over the 24 hours before. Fireworks posted the incident at Nov 3, 8:32 AM EST.

Updates are Fireworks's own words from its status page (status: resolved); we never add an inferred cause.

Service Degradation for Kimi K3 US

minor
Started
Nov 3, 11:02 AM EST
Resolved
Nov 3, 12:12 PM EST
Duration
1h 10m

Fireworks's updates (2)

  1. investigating · Nov 3, 11:02 AM EST

    We are seeing impacted performance for Kimi K3 US. We are actively investigating.

  2. resolved · Nov 3, 12:12 PM EST

    We've resolved the incident and the affected service is now operational.

What our checks recorded

We checked Fireworks AI 14 times from Fireworks's start time to its resolution, once every five minutes. Every one of them reached Fireworks AI's site, so this incident did not show up as a failed page load. Our check loads the public site; it cannot see an API error or a broken feature. Median response time was 420 ms, against 446 ms over the 24 hours before. Fireworks posted the incident at Nov 3, 11:02 AM EST.

Updates are Fireworks's own words from its status page (status: resolved); we never add an inferred cause.

Service Degradation for GLM 5.3 Fast

minor
Started
Nov 3, 11:05 AM EST
Resolved
Nov 3, 11:48 AM EST
Duration
43 min

Fireworks's updates (2)

  1. investigating · Nov 3, 11:05 AM EST

    We are seeing impacted performance for GLM 5.3 Fast. We are actively investigating.

  2. resolved · Nov 3, 11:48 AM EST

    We've resolved the incident and the affected service is now operational.

What our checks recorded

We checked Fireworks AI 8 times from Fireworks's start time to its resolution, once every five minutes. Every one of them reached Fireworks AI's site, so this incident did not show up as a failed page load. Our check loads the public site; it cannot see an API error or a broken feature. Median response time was 485 ms, against 447 ms over the 24 hours before. Fireworks posted the incident at Nov 3, 11:05 AM EST.

Updates are Fireworks's own words from its status page (status: resolved); we never add an inferred cause.

AIDownCheck is not affiliated with Fireworks. This recap summarizes incidents published on Fireworks's official status page.