Incidentsby Glyphstarting & stopping engines takes long time.
Jun 8, 08:18 UTCJun 8, 11:08 UTC
Duration
2h 50m
Impact
Major
Root cause
Not disclosed
Firebolt, 90 days
0 incidents
Affected
EnginesFirebolt Components - Engines
Final update
The issue resolved and the system is back to normal state.
Timeline
- Resolved · Jun 8, 11:08 UTC
The issue resolved and the system is back to normal state.
- Monitoring · Jun 8, 09:37 UTC
The fix deployed to production, and engines can be started and stopped again.
- Identified · Jun 8, 09:11 UTC
We are running some tests on staging to make sure the fix resolved the issue.
- Identified · Jun 8, 08:36 UTC
We are deploying a fix, and the issue should be resolved soon.
- Identified · Jun 8, 08:18 UTC
The issue is back, and Starting/Stopping engines may not work properly. We are continuing to investigate this issue.
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