Starburst Galaxy incident

Slow Cluster initialization

Resolved after 39 minutes, affecting AWS ap-northeast1 and Azure centralindia and 1 more, on April 22, 2025.

investigating Apr 22, 2025, 08:32 PM UTC

An issue with slow cluster initialization has been identified. Actively running clusters are not affected. However newly started clusters may experience slower than usual initialization time. The cause is still under investigation.

Started
Apr 22, 2025, 08:32 PM UTC
Resolved
Apr 22, 2025, 09:12 PM UTC
Duration
39m
Detected by Pingoru
Apr 22, 2025, 08:32 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. investigating Apr 22, 2025, 08:32 PM UTC

    An issue with slow cluster initialization has been identified. Actively running clusters are not affected. However newly started clusters may experience slower than usual initialization time. The cause is still under investigation.

  2. resolved Apr 22, 2025, 09:12 PM UTC

    The issue has been identified and resolved. Cluster startup is back to normal.

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 →