# Firebolt change history

Filter: kind=all. Query: `?kind=notable|all|pages|pricing|trust|legal|incident|incident_edit|incident_deleted|incident_update&history=<history_id>&page=N`. Company profile: [Firebolt](https://rewindex.com/company/firebolt.md)
## Changes by kind

| Kind | Changes | Notable | Latest (UTC) |
| --- | --- | --- | --- |
| Major incident | 35 | 35 | 2025-10-20 07:11 UTC |

## Timeline

| When (UTC) | Kind | Change | Label | Summary |
| --- | --- | --- | --- | --- |
| 2025-10-20 07:11 UTC | Major incident | [Major incident: AWS Service Issues in US-East-1](https://rewindex.com/change/i423ab892a4c508.md) | outage | Firebolt reported a major outage in US-EAST-1 from 2025-10-20 07:11 UTC to 2025-10-21 11:14 UTC (28 h 2 min), linked to a broader AWS outage. Customers may have experienced latency, query suspensions, ingestion failures and slower engine startups due to EC2 launch throttling. Firebolt marked the incident resolved and said the underlying AWS issue was fully resolved. |
| 2025-03-26 19:15 UTC | Major incident | [Major incident: Unable to Start Engines in 2.0](https://rewindex.com/change/i8c4b7640158171.md) | outage | Firebolt reported a major outage affecting engine starts in FB 2.0 across all regions, with difficulties reported as of 19:00 UTC on 2025-03-26. The incident was logged from 2025-03-26 19:15 UTC to 2025-03-26 19:18 UTC (3 min); a rollback restored engine starts, with the resolution update stating service was restored at 19:15 UTC. |
| 2025-03-25 18:21 UTC | Major incident | [Major incident: Login flow experiencing interruption in some regions](https://rewindex.com/change/i76c0ea659c1440.md) | outage | Firebolt reported a major login interruption in some regions due to an Auth0 incident, affecting users with expired tokens and possibly service accounts; V1 authentication was not expected to be affected. The incident started at 2025-03-25 18:21 UTC and was resolved at 2025-03-25 21:57 UTC, lasting 3 h 36 min; uninterrupted authentication was reported restored at 19:20 UTC. |
| 2025-01-31 00:23 UTC | Major incident | [Major incident: Firebolt V2 UI Experiencing Outage](https://rewindex.com/change/i484388f0ce41aa.md) | outage | Firebolt V2 UI access was down in a major incident starting 2025-01-31 00:23 UTC, resolved at 2025-01-31 01:29 UTC; the recorded duration was 1 h 5 min. Programmatic access could also be affected if a user token expired. Firebolt reported full operation restored at 01:15 UTC; no cause was stated. |
| 2025-01-22 19:22 UTC | Major incident | [Major incident: US-EAST-1 Engine Operations](https://rewindex.com/change/i148b9e3066e105.md) | outage | Firebolt reported a major US-EAST-1 outage from 2025-01-22 19:22 UTC to 2025-01-22 20:58 UTC, lasting 1 h 36 min. Customers could not start engines or use USE ENGINE and could encounter Develop space access and engine/account listing API issues; queries on running engines were expected to work. Firebolt deployed a fix and confirmed full restoration. |
| 2024-11-14 19:46 UTC | Major incident | [Critical incident: Unable to start Engines on FB 2.0](https://rewindex.com/change/ie26ba78b196ea2.md) | outage | 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. |
| 2024-06-21 06:42 UTC | Major incident | [Major incident: Incident Impacting Engine Start and Ingest Process](https://rewindex.com/change/id6302a69c5b2ad.md) | outage | Firebolt reported a major outage preventing engines from starting and impacting ingestion, from 2024-06-21 06:42 UTC to 2024-06-21 09:36 UTC (2 h 54 min). Engineering identified and resolved the issue, but no cause or specific fix was stated. |
| 2023-09-28 20:10 UTC | Major incident | [Major incident: Engine Startup Issue in US-EAST-1 Region](https://rewindex.com/change/i137c660505dee1.md) | outage | Firebolt reported a major engine startup outage in US-EAST-1 caused by an AWS issue, primarily affecting new instance launches; running engines and other regions were unaffected. It started at 2023-09-28 20:10 UTC and was resolved at 2023-09-29 06:37 UTC, lasting 10 h 26 min, with normal service restored. |
| 2023-08-02 12:25 UTC | Major incident | [Critical incident: Potential access issue to the UI.](https://rewindex.com/change/ib9c33c0c10850d.md) | outage | Firebolt reported a critical incident potentially affecting UI access and, in a later update, programmatic connections. It started at 2023-08-02 12:25 UTC and was resolved at 2023-08-02 13:00 UTC, lasting 35 min; Firebolt confirmed all services were operating as expected. |
| 2023-01-19 15:27 UTC | Major incident | [Major incident: UI issue - reporting engines states](https://rewindex.com/change/i0a6c161f813472.md) | outage | Firebolt reported a major UI incident affecting engine-state reporting across multiple accounts and engines, starting 2023-01-19 15:27 UTC and resolved 2023-01-19 18:43 UTC; the recorded duration was 3 h 15 min. Firebolt said the issue appeared UI-only, advised customers not to restart or stop engines, and applied a fix across all engines. |
| 2022-11-21 15:00 UTC | Major incident | [Critical incident: Engines fail to start](https://rewindex.com/change/i15bafcc163db46.md) | outage | Firebolt engines failed to start during a critical-impact incident beginning 2022-11-21 15:00 UTC, preventing affected customers from starting engines. The incident lasted 48 min and was resolved at 2022-11-21 15:49 UTC; Firebolt did not state a cause or specific fix. |
| 2022-11-14 10:55 UTC | Major incident | [Major incident: Engines fail to start in US-EAST-1](https://rewindex.com/change/i7ac61e3af9ad5c.md) | outage | Firebolt reported a major outage preventing engines from starting in US-EAST-1, beginning 2022-11-14 10:55 UTC and resolved at 2022-11-14 11:54 UTC (59 min). A fix restored normal engine startup by 11:41 UTC; no cause was stated. |
| 2022-08-10 11:52 UTC | Major incident | [Major incident: Start engine may fail](https://rewindex.com/change/i82a7319f9a72f3.md) | outage | Firebolt reported a major incident in which engines could fail to start, beginning 2022-08-10 11:52 UTC and resolved at 2022-08-10 12:50 UTC after 57 min. Recovery was reported for US-EAST-, then EU-WEST-1, before all regions returned to operational status. |
| 2022-06-22 13:20 UTC | Major incident | [Major incident: Errors Logging In](https://rewindex.com/change/ic0dacd93c1427e.md) | outage | Some users could not log into the Firebolt UI, receiving “Failed to fetch feature flag param” errors. Firebolt classified the incident as major; it started at 2022-06-22 13:20 UTC and was resolved at 2022-06-22 14:13 UTC, lasting 53 min. |
| 2022-06-08 08:18 UTC | Major incident | [Major incident: starting & stopping engines takes long time.](https://rewindex.com/change/ibf109797263d61.md) | degradation | Firebolt reported a major degradation affecting engine starts and stops from 2022-06-08 08:18 UTC to 2022-06-08 11:08 UTC, lasting 2 h 50 min. Starting or stopping engines could be slow or fail; a production fix restored those operations at 09:37 UTC, and Firebolt confirmed normal service at resolution. |
| 2022-06-08 07:11 UTC | Major incident | [Major incident: starting & stopping engines takes long time.](https://rewindex.com/change/ic28f7774b6b590.md) | degradation | Firebolt reported a major degradation affecting Engines: starting and stopping engines took a long time. The incident ran from 2022-06-08 07:11 UTC to 2022-06-08 07:35 UTC, lasting 24 min. Firebolt said it identified the root cause without specifying it, then confirmed the issue was fixed and engines could be started and stopped. |
| 2022-05-25 16:38 UTC | Major incident | [Major incident: Login issue](https://rewindex.com/change/i445223b31df5ac.md) | outage | Firebolt reported a major login outage affecting its API and Web Application, starting 2022-05-25 16:38 UTC and resolved at 2022-05-25 17:50 UTC (1 h 11 min). Customers experienced transient login issues; Firebolt said it identified the immediate cause and was implementing a long-term fix before confirming services were back to normal. |
| 2022-04-19 15:18 UTC | Major incident | [Major incident: Engines failing to start in us-east-1](https://rewindex.com/change/i111c23b0255acf.md) | outage | Firebolt reported a major outage affecting engine provisioning and startups in us-east-1 from 2022-04-19 15:18 UTC to 2022-04-19 18:04 UTC, lasting 2 h 45 min. Customers were told not to stop or restart existing engines. Firebolt attributed the disruption to an AWS issue; after its resolution, startups and restarts were permitted again, with stuck engines expected to start shortly. |
| 2022-01-26 13:02 UTC | Major incident | [Major incident: Engines may fail to start and stop](https://rewindex.com/change/i328d9694e34823.md) | outage | Firebolt reported a major incident affecting engine starts and stops from 2022-01-26 13:02 UTC to 2022-01-26 16:48 UTC (3 h 45 min). Ingestion on impacted engines may also have been affected. Firebolt reported a master-cluster outage that disrupted internal services; a fix was deployed and tested before resolution. |
| 2022-01-24 09:24 UTC | Major incident | [Critical incident: Loading databases could fail](https://rewindex.com/change/i0f1c08e53a3923.md) | outage | Firebolt reported a critical outage in which database loading could fail, preventing UI connections and potentially affecting API requests. It started at 2022-01-24 09:24 UTC and was resolved at 2022-01-24 13:25 UTC, lasting 4 h 0 min. A fix was implemented and monitored before resolution. |
| 2021-12-22 12:41 UTC | Major incident | [Major incident: Amazon Elastic Compute outage](https://rewindex.com/change/i0516d46053b434.md) | outage | Firebolt reported a major Amazon Elastic Compute outage affecting AWS EC2 instances, with API, Engines and Web Application listed as affected components. It started at 2021-12-22 12:41 UTC and was resolved at 2021-12-22 20:17 UTC, lasting 7 h 35 min. Firebolt said AWS identified the issue and a fix was in progress before resolution. |
| 2021-12-07 15:58 UTC | Major incident | [Major incident: Engines may fail to start and stop](https://rewindex.com/change/i18a91e433769ed.md) | outage | Firebolt reported a major incident in which engines could fail to start and stop in AWS us-east-1, starting 2021-12-07 15:58 UTC and lasting 15 h 59 min. Firebolt attributed it to partial AWS issues; the incident was resolved at 2021-12-08 07:57 UTC, with engines fully operational. |
| 2021-12-07 10:57 UTC | Major incident | [Critical incident: Accessing Firebolt web application may fail](https://rewindex.com/change/id9a2c18d5431d8.md) | outage | Firebolt reported a critical web application outage starting 2021-12-07 10:57 UTC, resolved at 2021-12-07 11:00 UTC (3 min). DNS configuration changes could prevent UI access; running workloads and engine operations were unaffected. Firebolt announced a fix rollout and advised users with lingering issues to clear their local DNS cache. |
| 2021-11-10 10:17 UTC | Major incident | [Critical incident: Using Firebolt web application may fail](https://rewindex.com/change/ia8695920fc113e.md) | outage | Firebolt reported a critical incident in which its web application could fail for customers in the European region. It started at 2021-11-10 10:17 UTC and was resolved at 2021-11-10 10:23 UTC, lasting 6 min; Firebolt reported a fix in progress before resolution but gave no cause. |
| 2021-09-28 16:19 UTC | Major incident | [Major incident: Signing in to Firebolt may fail](https://rewindex.com/change/i48cabdd5407998.md) | outage | Firebolt sign-ins could fail due to an auth0 outage in US-1 and EU regions, affecting the Web Application. Firebolt rated the incident major; it started at 2021-09-28 16:19 UTC and was resolved at 2021-09-28 16:30 UTC, with a reported duration of 10 min. |
| 2021-09-27 08:30 UTC | Major incident | [Major incident: Engines may fail to start and stop](https://rewindex.com/change/iaa090e2cb7f428.md) | outage | Firebolt reported a major outage in which engines could fail to start and stop due to an issue identified on AWS's side. It started at 2021-09-27 08:30 UTC and was resolved at 2021-09-27 12:13 UTC, lasting 3 h 42 min; Firebolt confirmed it was fully operational. |
| 2021-08-31 18:49 UTC | Major incident | [Major incident: Signing in to Firebolt may fail](https://rewindex.com/change/id2974ef0eb97ea.md) | outage | Firebolt reported a major incident in which sign-ins could fail, affecting AWS ec2-us-east-2, Engines and Web Application. It started at 2021-08-31 18:49 UTC and was resolved at 2021-09-01 02:02 UTC, lasting 7 h 12 min. Firebolt attributed it to cloud-provider networking issues and reported implementing a fix. |
| 2021-08-19 22:17 UTC | Major incident | [Major incident: Signing in to Firebolt may fail](https://rewindex.com/change/i7969b34e15ff59.md) | outage | Firebolt reported a major incident in which signing in could fail due to third-party provider authentication issues. It started at 2021-08-19 22:17 UTC and lasted 24 min, ending at 2021-08-19 22:41 UTC with login operational. |
| 2021-07-20 04:30 UTC | Major incident | [Major incident: Engines may fail to start and stop](https://rewindex.com/change/i87ca5dde3b1e6c.md) | outage | Firebolt reported a major incident in which engines could fail to start or stop, beginning 2021-07-20 04:30 UTC and lasting 4 h 20 min. Firebolt attributed it to unidentified issues on AWS’s side and confirmed resolution there at 2021-07-20 08:50 UTC, restoring engine start/stop functionality. |
| 2021-06-29 11:30 UTC | Major incident | [Major incident: Starting/restarting new engines fails](https://rewindex.com/change/i9f869e128800d4.md) | outage | Firebolt reported a major incident preventing new engines from starting or restarting, beginning 2021-06-29 11:30 UTC and lasting 29 min. A fix was implemented at 2021-06-29 11:55 UTC; engine startup was restored and the incident resolved at 2021-06-29 11:59 UTC. |
| 2021-05-11 07:04 UTC | Major incident | [Critical incident: Logging into FIrebolt may fail](https://rewindex.com/change/if6102251717a41.md) | outage | Firebolt reported a critical login outage affecting direct and JDBC logins from 2021-05-11 07:04 UTC to 2021-05-11 07:52 UTC, lasting 48 min. Login attempts had high failure rates; customers were advised to retry, while all other functionality remained operational. Firebolt confirmed logins were fully functional at resolution. |
| 2021-04-20 16:25 UTC | Major incident | [Critical incident: Logging into FIrebolt may fail](https://rewindex.com/change/i7be2bdfb343501.md) | outage | Firebolt reported a critical Web Application incident where login attempts could fail or take significantly longer than usual, starting 2021-04-20 16:25 UTC and resolved at 2021-04-20 17:19 UTC (53 min). Firebolt attributed the issue to an Auth0 outage and reported implementing a fix. |
| 2021-04-18 10:49 UTC | Major incident | [Major incident: Engines may fail to start or stop](https://rewindex.com/change/i66f206a7c627ea.md) | outage | Firebolt reported a major incident in which engines could fail to start or stop, beginning 2021-04-18 10:49 UTC and resolved at 2021-04-18 11:10 UTC, with a reported duration of 20 min. Firebolt said it identified the issue and was implementing a fix, but provided no cause or fix details. |
| 2021-02-23 09:07 UTC | Major incident | [Critical incident: Web application is experiencing a significant outage](https://rewindex.com/change/i59626dbd83213f.md) | outage | Firebolt’s Web Application experienced a critical outage starting at 2021-02-23 09:07 UTC, lasting 6 min and resolving at 2021-02-23 09:14 UTC. Firebolt reported that the issue was identified and a fix was being implemented, but did not specify the cause or fix. |
| 2021-02-22 17:38 UTC | Major incident | [Critical incident: Engines may fail to start](https://rewindex.com/change/i70bf67211406cb.md) | outage | Firebolt reported a critical incident in which engines could fail to start, beginning 2021-02-22 17:38 UTC and resolved at 2021-02-22 18:16 UTC, lasting 37 min. The vendor attributed it to a global Terraform/Hashicorp outage and stated that running engines should not be affected. |


---
Canonical: https://rewindex.com/company/firebolt/changes · Markdown: https://rewindex.com/company/firebolt/changes.md · JSON: https://rewindex.com/api/v1/companies/firebolt/changes · Generated 2026-10-18T02:27:56.820Z
