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

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

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 see
Customers 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.

The full archive is on the Fireworks status & history page.

Related: Fireworks status & history. SquidGrid is not affiliated with Fireworks.