Inability to Start Engines
Mar 4, 18:12 UTCMar 4, 20:38 UTC
Duration
2h 25m
Impact
Minor
Root cause
Not disclosed
Firebolt, 90 days
0 incidents
Affected
EnginesFirebolt Components - Engines
Final update
Service is now fully restored.
Timeline
- Resolved · Mar 4, 20:38 UTC
Service is now fully restored.
- Monitoring · Mar 4, 19:46 UTC
We have fixed the issue. Engines are now able to start. We are still working on restoring the engines that are currently in "Starting up" state.
- Identified · Mar 4, 19:35 UTC
We have identified the issue and are working towards restoring the functionality.
- Investigating · Mar 4, 18:54 UTC
We are continuing to investigate the issue.
- Investigating · Mar 4, 18:20 UTC
We have come to learn the issue is not bound to us-east-1 region only, but is unfortunately impacting all regions. The only impact we know of for now is the inability to start engines. Already running engines should not be impacted.
- Investigating · Mar 4, 18:12 UTC
We’re experiencing an issue with starting engines that affects us-east-1 since 4:49pm UTC, Starting engines will fail until the issue is resolved. If you have already started an engine and are experiencing unusual timings please reach out to support. Our engineers are working to resolve the issue as soon as possible. We will be updating the Status page page with new information at the latest every 30 minutes.
More from Firebolt
Full historySporadic transaction timeoutslasted 0mCloudflare Outage Impacting Authentication & Documentation Serviceslasted 6h 10mAuthentication Service Maintenance - SSO Infrastructure Updatelasted 1h 57mAWS Service Issues in US-East-1lasted 28h 3mUnable to Start Engines in 2.0lasted 3mLogin flow experiencing interruption in some regionslasted 3h 36m