Live / Fireworks / Incident
Fireworks: Service degradation
Fireworks · fireworks.aiResolved2026-11-06 18:28 UTC
Public — what happened
Summary
Fireworks reported a service degradation that began on 2026-10-30 at 20:51 UTC and affected creating deployments, dedicated training, and batch inference. The company said it was working on the problem and would post updates. On 2026-11-06 at 18:28 UTC, Fireworks said dedicated deployments, training, and batch inference had been restored. The incident is still marked as monitoring rather than resolved, and Fireworks did not state a cause.
Timeline
- Started — 2026-10-30 20:51 UTC
- Identified — 2026-10-30 20:51 UTC
- Monitoring — 2026-11-06 18:28 UTC
- Resolved — 2026-11-06 18:28 UTC · 7 days after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Fireworks against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Fireworks: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Fireworks report →
More from Fireworks
Covered in The Squid’s Ink, Week 45, 2026, our weekly internet health report.