Starburst: PrivateLink connections issues
Affected components: - AWS ap-northeast1 - AWS ap-southeast1 - AWS ap-southeast2 - AWS ca-central1 - AWS eu-central1 - AWS eu-west1 - AWS eu-west2 - AWS eu-west3 - AWS us-east1 - AWS us-east2 - AWS us-west1 - AWS us-west2Clusters - AWS
Timeline of updates
- identified
We are investigating an issue causing clusters and pipelines connected via AWS/Azure PrivateLink to fail to start, with queries timing out. Clusters using standard (non-PrivateLink) connectivity are not affected. Our team has identified the likely area (an Istio/networking change) and is working to confirm and remediate. We will post updates as we learn more.
- monitoring
A fix has been implemented and we are monitoring the results.
- resolved
This incident has been resolved.
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.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
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: major) posted by Starburst, started 2026-08-13 15:39 UTC, resolved after 0 min, 3 update(s).
- Title
- PrivateLink connections issues
- Vendor
- Starburst
- Date
- URL
- https://rewindex.com/company/starburst/incidents/ls4pgsp77ljm
Starburst profileRecent Starburst incidentsAll outages on August 13, 2026Starburst in August 2026MarkdownJSON