# Starburst: Service Outage Due to AWS Cloud Provider Issue

> Starburst status incident “Service Outage Due to AWS Cloud Provider Issue” on 2025-10-20: impact critical (vendor’s label), 0 min, 6 update(s). Archived by Rewindex.

Canonical: https://rewindex.com/company/starburst/incidents/3zwlj5pmxvwr
Last updated: 2025-10-20T22:50:51Z

- Impact (vendor’s label): critical
- Status: resolved
- Started: 2025-10-20 22:50 UTC · Resolved: 2025-10-20 22:50 UTC · Duration: 0 min
- Updates: 6 · Affected components:  - AWS us-east1, Clusters - AWS
- [Vendor status page: https://status.galaxy.starburst.io/incidents/3zwlj5pmxvwr](https://status.galaxy.starburst.io/incidents/3zwlj5pmxvwr)
- [Company: Starburst](https://rewindex.com/company/starburst.md)

## Timeline of updates

- **identified** 2025-10-20 09:42 UTC: 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** 2025-10-20 13:10 UTC: 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** 2025-10-20 15:18 UTC: 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** 2025-10-20 19:08 UTC: 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** 2025-10-20 20:51 UTC: AWS services are slowly getting restored. We are actively monitoring our services to ensure they recover as well
- **resolved** 2025-10-20 22:50 UTC: All galaxy services affected by AWS outage should be operational at this point.

## Rewindex changes for this incident

- 2025-10-20 22:50 UTC: [Critical incident: Service Outage Due to AWS Cloud Provider Issue](https://rewindex.com/change/i19f4db8710ab6d.md)

## 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).

- Canonical URL: https://rewindex.com/company/starburst/incidents/3zwlj5pmxvwr
- Citation: Starburst, “Service Outage Due to AWS Cloud Provider Issue” (2025-10-20 22:50 UTC). Archived by Rewindex: https://rewindex.com/company/starburst/incidents/3zwlj5pmxvwr (CC BY 4.0).
- Markdown link: `[Starburst: Service Outage Due to AWS Cloud Provider Issue (2025-10-20)](https://rewindex.com/company/starburst/incidents/3zwlj5pmxvwr)`


---
Canonical: https://rewindex.com/company/starburst/incidents/3zwlj5pmxvwr · Markdown: https://rewindex.com/company/starburst/incidents/3zwlj5pmxvwr.md · JSON: https://rewindex.com/api/v1/companies/starburst/incidents/3zwlj5pmxvwr · Data licensed CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) · Generated 2026-11-05T18:49:40.223Z