Unable to start Engines on FB 2.0
Nov 14, 19:46 UTCNov 14, 20:10 UTC
Duration
24m
Impact
Critical
Root cause
Not disclosed
Firebolt, 90 days
0 incidents
Affected
EnginesFirebolt Components - Engines
Final update
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.
Timeline
- Resolved · Nov 14, 20:10 UTC
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.
- Investigating · Nov 14, 20:02 UTC
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.
- Investigating · Nov 14, 19:46 UTC
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.
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