Changes / Fireworks AI / Kimi K3 service disruption
Fireworks AI: Major incident: Kimi K3 service disruption
Summary
Kimi K3 experienced elevated errors and degraded availability during a major incident starting 2026-08-18 05:52 UTC, caused by connectivity issues affecting one region. Availability recovered by 06:22 UTC; the incident was resolved at 2026-08-18 07:01 UTC after 1 h 9 min.
Machine-written from the diff below (Sol; type: incident outage). Check the diff before relying on it.
What changed
Before: not present
After: Kimi K3 service disruption
Before: not present
After: major
Before: not present
After: resolved
Before: not present
After: 2026-08-18 05:52 UTC
Before: not present
After: 2026-08-18 07:01 UTC
Before: not present
After: Customers may be experiencing elevated errors and degraded availability when using Kimi K3. We are mitigating the impact while we investigate connectivity issues affecting one of our regions.
Before: not present
After: Kimi K3 availability has recovered following the regional connectivity disruption. We are monitoring the service closely to confirm the recovery remains stable.
Before: not present
After: Kimi K3 availability has recovered and the service is operating normally following the regional connectivity disruption. We will continue monitoring to confirm recovery remains stable.
Before: not present
After: Kimi K3 availability has recovered and the service is operating normally. We have resolved this incident.
First version of this incident archived by Rewindex. View the live incident.
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Major incident: Kimi K3 service disruption (this change) Kimi K3 experienced elevated errors and degraded availability during a major incident starting 2026-08-18 05:52 UTC, caused by connectivity issues affecting one region. Availability recovered by 06:22 UTC; the incident was resolved at 2026-08-18 07:01 UTC after 1 h 9 min. | Major incident |
All Fireworks AI changes → · Fireworks AI profile · Markdown · JSON