Sporadic transaction timeouts
Timeline · 1 update
- resolved Apr 09, 2026, 10:01 PM UTC
One of the storage pods in metadata service got overloaded, and both reads and writes started queuing causing transactions to fail with timeouts
Firebolt had 4 outages in the last 2 years totaling 36h 9m of downtime — averaging 0.2 incidents per month.
There were 4 Firebolt outages since October 20, 2025 totaling 36h 9m of downtime. Each is summarised below — incident details, duration, and resolution information.
One of the storage pods in metadata service got overloaded, and both reads and writes started queuing causing transactions to fail with timeouts
We are currently experiencing service disruptions due to an ongoing Cloudflare outage. This issue is affecting several Firebolt services, including: - Logins management - New user registrations - Documentation search These disruptions may prevent some users from accessing their accounts, creating new accounts, or searching our documentation. We are monitoring Cloudflare’s status closely and will provide updates as the situation evolves.
Cloudflare services are operating as normal, and we have not identified any ongoing disruptions.
We are performing a scheduled maintenance as part of our ongoing improvements to authentication and service account infrastructure. During this time, users may experience temporary login or registration interruptions (timeouts or brief sign-in errors). No action is required, and service account authentication will remain unaffected. Once the update is complete, all systems will resume normal operation.
The scheduled maintenance related to the SSO domain update has been successfully completed. All authentication and sign-in services are now fully operational, and no further interruptions are expected. Thank you for your patience during this maintenance window.
Some Firebolt services may experience latency or disruptions due to an ongoing AWS outage in the US-EAST-1 region. The issue is impacting multiple AWS services, which may affect engine operations and data access in this region. Our team is actively monitoring the situation and working to minimize customer impact. We'll share updates as more information becomes available from AWS.
AWS is currently throttling requests for new EC2 instance launches to aid recovery and actively working on mitigations. This may impact the start up times of your engines.
Engine and database operations in us-east-1 are generally available but may experience increased error rates as AWS continues to stabilize services. We are monitoring and will update this page once all services have been confirmed to resume normal performance levels.
Post-Incident Update: On October 20, Firebolt services in the US-EAST-1 region experienced disruptions related to a broader AWS outage impacting multiple services, including DynamoDB. During this time, some customers in the us-east-1 region may have encountered increased latency, query suspensions, or ingestion job failures. The underlying AWS issue has since been fully resolved, and all Firebolt services have returned to normal operation. No other regions were affected. We continue to monitor system performance closely to ensure stability.