Starburst: Service Outage Due to AWS Cloud Provider Issue
Affected components: - AWS us-east1Clusters - AWS
Timeline of updates
- identified
We are currently experiencing a service outage caused by an ongoing incident affecting our cloud provider, Amazon Web Services (AWS). Our teams are actively monitoring the situation and are in close contact with AWS as they work to resolve the issue. We will continue to provide updates and confirm once all services are fully restored.
- identified
Although some AWS services have been restored, others continue to fail, and we are still impacted. In particular, any Galaxy service tied to the AWS region us-east-1 is currently not functioning properly. This includes creating new clusters and modifying RBAC permissions.
We will continue to work with AWS to restore our full functionality and provide updates here. - identified
We are still affected by residual AWS outages, with many Galaxy functions affected (e.g., creating new clusters, result-set caching, modifying RBAC permissions, etc.). We continue to work with AWS to address the problems and will update the status here when we have new information to share.
- identified
We have put in some temporary mitigations to help alleviate the cluster startup problems in us east 1. At the same time we are still actively monitoring the AWS outage. Along with cluster startup, we think customers using galaxy telemetry and managed data ingestion may also experience data staleness.
We are working with AWS to mitigate this and will provide more updates when there is new information to share. - monitoring
AWS services are slowly getting restored. We are actively monitoring our services to ensure they recover as well
- resolved
All galaxy services affected by AWS outage should be operational at this point.
Changes Rewindex caught on this incident
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-11-04 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
e57925df9f4224b1…
Impact, status and times are the vendor’s own, as last archived. View on status.galaxy.starburst.io (opens in new tab).
Cite this
Status incident (vendor impact label: critical) posted by Starburst, started 2025-10-20 22:50 UTC, resolved after 0 min, 6 update(s).
- Title
- Service Outage Due to AWS Cloud Provider Issue
- Vendor
- Starburst
- Date
- URL
- https://rewindex.com/company/starburst/incidents/3zwlj5pmxvwr
Starburst profileRecent Starburst incidentsAll outages on October 20, 2025Starburst in October 2025MarkdownJSON