Starburst: Several Galaxy accounts are having issues to start clusters on Azure
Affected components: - Azure eastus - Azure eastus2 - Azure westeuropeClusters - Azure
Timeline of updates
- investigating
Several Galaxy accounts are experiencing issues restarting Azure clusters across multiple regions. The team is actively investigating the root cause and working to restore normal operations as quickly as possible.
- identified
According to Azure status page https://azure.status.microsoft/en-us/status (opens in new tab)
"Active - Virtual Machine service management issues - Multiple regions
Impact statement: We are aware of an ongoing issue causing customers to receive error notifications when performing service management operations - such as create, delete, update, scaling, start, stop - for Virtual Machines (VMs). These issues are also causing impact to services with dependencies on these operations, including Azure Arc Enabled Servers, Azure Batch, Azure DevOps, and GitHub. For details on the latter, please see https://www.githubstatus.com (opens in new tab). Current status: We have determined that these issues were caused by a recent configuration change that affected public access to certain Microsoft‑managed storage accounts, used to host extension packages. We are actively working on mitigation, including updating configuration to restore relevant access permissions. Our next update will be provided by 22:30 UTC, approximately 60 minutes from now.
This message was last updated at 21:35 UTC on 02 February 2026" - identified
Current status from Azure team( https://azure.status.microsoft/en-us/status (opens in new tab)) : "We have determined that these issues were caused by a recent configuration change that affected public access to certain Microsoft‑managed storage accounts, used to host extension packages. We are actively working to mitigate impact, by updating our configuration to restore relevant access permissions. After applying this update in one region, we validated that it mitigates the issues customers were experiencing - we are making good progress applying this same mitigation across all impacted regions, in parallel where possible. We still expect that this will be completed across all impacted regions by approximately 00:00 UTC, approximately one hour from now. Our next update will be provided by then, or sooner if we have progress to share.
This message was last updated at 22:59 UTC on 02 February 2026" - identified
We are continuing to work on a fix for this issue.
- 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-02-03 14:41 UTC, resolved after 0 min, 5 update(s).
- Title
- Several Galaxy accounts are having issues to start clusters on Azure
- Vendor
- Starburst
- Date
- URL
- https://rewindex.com/company/starburst/incidents/2qbtqkvhnms5
Starburst profileRecent Starburst incidentsAll outages on February 3, 2026Starburst in February 2026MarkdownJSON