Get webhook notifications whenever Hyperstack Service Status creates an incident, updates an incident, resolves an incident or changes a component status.
We will be undergoing weekly scheduled maintenance on HyperStack and underlying services to ensure better, smoother, and faster user experiences for the customers. During this time, HyperStack end-users may see a slight impact on the dashboard performance, but no VM operations should be impacted.
Completed -
The scheduled maintenance has been completed.
May 12, 14:30 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 12, 12:30 UTC
Scheduled -
We will be undergoing weekly scheduled maintenance on HyperStack and underlying services to ensure better, smoother, and faster user experiences for the customers. During this time, HyperStack end-users may see a slight impact on the dashboard performance, but no VM operations should be impacted.
Completed -
The scheduled maintenance has been completed.
May 5, 14:30 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 5, 12:30 UTC
Scheduled -
We will be undergoing weekly scheduled maintenance on HyperStack and underlying services to ensure better, smoother, and faster user experiences for the customers. During this time, HyperStack end-users may see a slight impact on the dashboard performance, but no VM operations should be impacted.
Resolved -
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 support@hyperstack.cloud.
Apr 29, 14:11 UTC
Identified -
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.
Apr 29, 13:38 UTC
Update -
We are continuing to investigate this issue.
Apr 29, 10:39 UTC
Investigating -
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.
Apr 29, 10:36 UTC