Vendor reports: operationalResolved · vendor status “resolved”Official status API

Galaxy Clusters abruptly restarting

Reported by Starburst · Data & Analytics · source last read 2 min ago

Official source (opens in a new tab)
Vendor start
Nov 20, 2024, 17:07 UTC
Vendor's clock
Resolved
Nov 21, 2024, 07:20 UTC
Vendor's clock
First seen by Statuswall
Nov 11, 2026, 02:11 UTC
Statuswall's clock
Duration
14 h 13 min
From vendor start and resolution

Summary

Built from the facts below, no AI

Potential impact, not a confirmed outage of your systems.

What the vendor confirmed

  • Starburst reports operational: "Galaxy Clusters abruptly restarting".[E1, E2]
  • The vendor marked it resolved at 2024-11-21 07:20 UTC.[E3, E7]

Affected products and regions

  • Components: AWS ap-northeast1, Azure centralindia, GCP asia-south1, AWS ap-southeast1, Azure eastus, GCP asia-southeast1, AWS ap-southeast2, Azure eastus2, GCP europe-west2, AWS ca-central1, azure francecentral, GCP europe-west6, AWS eu-central1, Azure southcentralus, GCP southamerica-east1, AWS eu-west1, Azure westeurope, GCP us-central1, AWS eu-west2, GCP us-east1, AWS eu-west3, AWS us-east1, AWS us-east2, AWS us-west1, AWS us-west2.[E6]

What is unknown

  • Which regions are affected: the vendor did not say.[E5]
  • Whether your own systems are affected: a vendor report cannot tell you; check your monitoring.

Last update in these facts: 2026-11-11 02:11 UTC · summary s1, evidence 4d24488063485d5f

Evidence (8)
  1. E1Starburst reports operational. (vendor) source (opens in a new tab)
  2. E2Vendor title: "Galaxy Clusters abruptly restarting". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2024-11-20 17:07 UTC. (vendor) source (opens in a new tab)
  5. E5The vendor did not state which regions are affected. (Statuswall)
  6. E6Components the vendor attached: AWS ap-northeast1, Azure centralindia, GCP asia-south1, AWS ap-southeast1, Azure eastus, GCP asia-southeast1, AWS ap-southeast2, Azure eastus2, GCP europe-west2, AWS ca-central1, azure francecentral, GCP europe-west6, AWS eu-central1, Azure southcentralus, GCP southamerica-east1, AWS eu-west1, Azure westeurope, GCP us-central1, AWS eu-west2, GCP us-east1, AWS eu-west3, AWS us-east1, AWS us-east2, AWS us-west1, AWS us-west2. (vendor) source (opens in a new tab)
  7. E7Vendor-reported resolution: 2024-11-21 07:20 UTC. (vendor) source (opens in a new tab)
  8. E8First seen by Statuswall: 2026-11-11 02:11 UTC. (Statuswall)

Affected scope

Not stated by the vendor

Components: AWS ap-northeast1, Azure centralindia, GCP asia-south1, AWS ap-southeast1, Azure eastus, GCP asia-southeast1, AWS ap-southeast2, Azure eastus2, GCP europe-west2, AWS ca-central1, azure francecentral, GCP europe-west6, AWS eu-central1, Azure southcentralus, GCP southamerica-east1, AWS eu-west1, Azure westeurope, GCP us-central1, AWS eu-west2, GCP us-east1, AWS eu-west3, AWS us-east1, AWS us-east2, AWS us-west1, AWS us-west2

No region Statuswall recognises is stated for this incident (place names and provider-specific codes are not converted). It is not assumed to be global.

Potential relevance

Starburst is not in your stack. Follow it to see whether reports like this fall inside the regions you use.

Timeline

Vendor times come from the vendor. “Seen by Statuswall” times are when Statuswall noticed a change, which can lag the vendor by a few minutes. Statuswall does not store the vendor's update text; read it on the official page.

  1. Nov 20, 2024, 17:07 UTCVendor-reported startVendor time
  2. Nov 21, 2024, 07:20 UTCVendor-reported resolutionVendor time
  3. Nov 11, 2026, 02:11 UTCFirst seen by Statuswall (vendor status: resolved)Seen by Statuswall