Starburst Galaxy incident

Autoscaling service degradation

Resolved after 23 hours 36 minutes, affecting AWS ap-northeast1 and Azure centralindia and 1 more, on August 13, 2025.

resolved Aug 14, 2025, 06:30 PM UTC

Our investigation revealed that the autoscaling has been working as expected -- with that we're closing this incident.

Started
Aug 13, 2025, 06:53 PM UTC
Resolved
Aug 14, 2025, 06:30 PM UTC
Duration
23h 36m
Detected by Pingoru
Aug 13, 2025, 06:53 PM UTC

Affected components

AWS ap-northeast1Azure centralindiaGCP asia-south1AWS ap-southeast1Azure eastusGCP asia-southeast1AWS ap-southeast2Azure eastus2GCP europe-west2AWS ca-central1

Update timeline

  1. identified Aug 13, 2025, 06:53 PM UTC

    We have identified an issue with the Galaxy Autoscaler where the recommendation engine is not detecting increased workloads (for scale-ups only, scale-downs are working as expected) which can lead to Trino clusters not being autoscaled to match the workload. We recommend to scale up the clusters manually as we work towards a permanent fix.

  2. resolved Aug 14, 2025, 06:30 PM UTC

    Our investigation revealed that the autoscaling has been working as expected -- with that we're closing this incident.

Your product runs on more than Starburst Galaxy

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →