F
Outage recap · Fireworks

Fireworks AI outage — November 18, 2026

On November 18, 2026, Fireworks AI had 2 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 18, 7:11 AM EST
Resolved
Nov 18, 7:30 AM EST
Duration
19 min

Fireworks's updates (2)

  1. investigating · Nov 18, 7:11 AM EST

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

  2. resolved · Nov 18, 7:30 AM EST

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

What our checks recorded

We checked Fireworks AI 4 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 381 ms, against 418 ms over the 24 hours before. Fireworks posted the incident at Nov 18, 7:11 AM EST.

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

Service Outage for Kimi K3.1 Pro

critical
Started
Nov 18, 8:12 PM EST
Resolved
Nov 18, 11:16 PM EST
Duration
3h 5m

Fireworks's updates (4)

  1. investigating · Nov 18, 8:12 PM EST

    We are actively investigating an outage for Kimi K3.1 Pro

  2. investigating · Nov 18, 8:46 PM EST

    We’ve partially restored service to Kimi K3.1 Pro, and are still actively root causing the situation

  3. monitoring · Nov 18, 9:58 PM EST

    Kimi K3.1 Pro services are restored and we are monitoring

  4. resolved · Nov 18, 11:16 PM EST

    Service is restored

What our checks recorded

We checked Fireworks AI 37 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 404 ms, against 423 ms over the 24 hours before. Fireworks posted the incident at Nov 18, 8:12 PM 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.