Struck in red is what Starburst removed; blue is what they added. Muted text is unchanged context.
BeforeAfter
AddedTitle#1
Before: not present
After: Service Outage Due to AWS Cloud Provider Issue
AddedImpact#2
Before: not present
After: critical
AddedStatus#3
Before: not present
After: resolved
AddedStart time#4
Before: not present
After: 2025-10-20 22:50 UTC
AddedResolved time#5
Before: not present
After: 2025-10-20 22:50 UTC
AddedAffected components#6
Before: not present
After: - AWS us-east1, Clusters - AWS
AddedUpdateidentified#7
Before: not present
After: 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.
AddedUpdateidentified#8
Before: not present
After: 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.
AddedUpdateidentified#9
Before: not present
After: 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.
AddedUpdateidentified#10
Before: not present
After: 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.
AddedUpdatemonitoring#11
Before: not present
After: AWS services are slowly getting restored. We are actively monitoring our services to ensure they recover as well
AddedUpdateresolved#12
Before: not present
After: All galaxy services affected by AWS outage should be operational at this point.
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.