Search

Companies / Firebolt / incidents

Firebolt: Unable to start Engines on FB 2.0

Impact: criticalStatus: resolvedStarted Resolved (24 min)3 updatesSource: stspg.io (opens in new tab)
Summary

Firebolt reported a critical FB 2.0 outage across all regions: engines could not start or Autostop, and inserts failed on running engines. The incident started at 2024-11-14 19:46 UTC, with symptoms reported since 18:26 UTC; its recorded duration was 23 min. Reverting a recent network change restored service at 20:03 UTC; it was marked resolved at 20:10 UTC.

Machine-written from the archived incident (Sol). Check the timeline before relying on it.

Affected components: EnginesFirebolt Components - Engines

Timeline of updates

  1. investigating

    We are currently experiencing an unplanned service outage affecting all regions. As of 18:26 UTC, you may encounter difficulties starting engines in our FB 2.0 environment. Our engineering team is actively working to resolve the issue as quickly as possible. We will provide updates on our Statuspage at least every 15 minutes. Thank you for your patience and understanding.

  2. investigating

    We are still experiencing the issue, and continuing to work on a fix Updated Impact: - Engines are unable to start. - Engines are unable to stop with Autostop and remain in the "Running" state, even when no queries are executed. - Insert commands are failing on currently running engines. We continue to look into this with the highest priority.

  3. resolved

    The issue was resolved at 20:03 UTC. We experienced an outage in engine operations, which was addressed by reverting a recent network change. Services are now fully operational. Please reach out if you experience any further issues.

Rewindex changes for this incident

Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab). Firebolt profile · Recent Firebolt incidents · Markdown · JSON