Incidentsby GlyphEngines failing to start in us-east-1
Apr 19, 15:18 UTCApr 19, 18:04 UTC
Duration
2h 45m
Impact
Major
Root cause
Not disclosed
Firebolt, 90 days
0 incidents
Affected
EnginesFirebolt Components - Engines
Final update
The AWS issue has been resolved and any engine that was stuck will start up shortly. You may execute engine start ups and restarts in us-east-1 again. We appreciate your patience on this issue.
Timeline
- Resolved · Apr 19, 18:04 UTC
The AWS issue has been resolved and any engine that was stuck will start up shortly. You may execute engine start ups and restarts in us-east-1 again. We appreciate your patience on this issue.
- Monitoring · Apr 19, 15:46 UTC
AWS has issued a message as of 8:39am PDT stating they are having issues with all engines in us-east-1 and have identified and are working to fix the root of the issue. We will continue to monitor the AWS event and ensure we are operational asap.
- Investigating · Apr 19, 15:18 UTC
Hello - we are experiencing issues provisioning engines in us-east-1. Please do not stop/restart existing engines during this time. We are actively investigating and will update with an ETA on the fix shortly.
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