Firebolt incident

US-EAST-1 Engine Operations

Major Resolved View vendor source →

Firebolt experienced a major incident on January 22, 2025 affecting Web Application and API and 1 more component, lasting 1h 36m. The incident has been resolved; the full update timeline is below.

Started
Jan 22, 2025, 07:22 PM UTC
Resolved
Jan 22, 2025, 08:58 PM UTC
Duration
1h 36m
Detected by Pingoru
Jan 22, 2025, 07:22 PM UTC

Affected components

Web ApplicationAPIEngines

Update timeline

  1. investigating Jan 22, 2025, 07:22 PM UTC

    We’re currently experiencing an unplanned service outage that impacts the US-EAST-1 region only. As a result, you may encounter issues accessing the Develop space and receiving API call responses listing engines and accounts. Our team is actively investigating the issue and working toward a resolution. We understand the inconvenience this may cause and appreciate your patience. We will be updating the Statuspage with new information at the latest every 15 minutes.

  2. investigating Jan 22, 2025, 07:23 PM UTC

    We are continuing to investigate this issue.

  3. identified Jan 22, 2025, 07:30 PM UTC

    We have identified the root cause of the issue and are making significant progress toward resolving it.

  4. identified Jan 22, 2025, 07:53 PM UTC

    We are still experiencing the issue and are actively working on a resolution. To clarify the impact: - You will not be able to start engines or - you will not be able to use the USE ENGINE command. However, if you already have a running engine, queries should execute as expected. We apologize for the inconvenience and appreciate your patience as we work to resolve this as quickly as possible.

  5. identified Jan 22, 2025, 08:32 PM UTC

    We are continuing to work toward a resolution and will provide an update as soon as operations are fully restored.

  6. monitoring Jan 22, 2025, 08:41 PM UTC

    We’ve deployed a fix, and the situation is showing signs of improvement. We are monitoring closely as we wait for operations to stabilize further.

  7. resolved Jan 22, 2025, 08:58 PM UTC

    The issue is now fully resolved and services are fully operational.