Hyperstack experienced a major incident on April 29, 2026 affecting Norway 1 Datacentre and Canada 1 Datacentre and 1 more component, lasting 3h 34m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Apr 29, 2026, 10:36 AM UTC
Summary We are currently investigating an issue affecting cluster reconciliation. The NVIDIA Helm chart repository (https://helm.ngc.nvidia.com/nvidia) is returning errors and appears to be unreachable. Impact Clusters that depend on NVIDIA Helm charts may fail to reconcile to their desired state. Observed Error 502 Bad Gateway when attempting to fetch index.yaml from the NVIDIA Helm repository. Current Status Investigation is ongoing. We are monitoring the upstream NVIDIA repository and assessing potential mitigation options. Next Update We will provide an update as soon as additional information or mitigation steps become available.
- investigating Apr 29, 2026, 10:39 AM UTC
We are continuing to investigate this issue.
- identified Apr 29, 2026, 01:38 PM UTC
Summary We have narrowed down the issue to just cluster creation. Reconciliation for existing clusters (incl adding/removing nodes/groups) aren't affected. Impact Clusters that depend on NVIDIA Helm charts may fail to create. Observed Error 502 Bad Gateway when attempting to fetch index.yaml from the NVIDIA Helm repository. Current Status Investigation is ongoing. We are monitoring the upstream NVIDIA repository and assessing potential mitigation options. Next Update We will provide an update as soon as additional information or mitigation steps become available.
- resolved Apr 29, 2026, 02:11 PM UTC
Summary The underlying issue has been resolved. New clusters are now creating successfully and transitioning to an Active state as expected. Impact Cluster creation and reconciliation processes are now fully operational. Current Status All systems are functioning normally. We apologise for any inconvenience this issue may have caused. We will continue to monitor the situation closely. If you experience any further issues, please contact us at [email protected].