Incidentsby GlyphAWS Outage affecting Start/Stop Engines
Jun 13, 21:20 UTCJun 13, 21:37 UTC
Duration
17m
Impact
Minor
Root cause
Not disclosed
Firebolt, 90 days
0 incidents
Affected
EnginesFirebolt Components - Engines
Final update
AWS has announced all services are restored, although there is a backlog of requests in their services. We are seeing engines start and stop succesfully, although it may take longer than usual for a few hours.
Timeline
- Resolved · Jun 13, 21:37 UTC
AWS has announced all services are restored, although there is a backlog of requests in their services. We are seeing engines start and stop succesfully, although it may take longer than usual for a few hours.
- Identified · Jun 13, 21:20 UTC
Several AWS services are experiencing issues. Because of this, Firebolt engines are not able to Start. Also, engines that are Stopped will be in Stopping status for a period of time, and then report Failed Stopping. They are effectively stopped and no longer running. We are monitoring updates from AWS.
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