Is Hyperstack down? › Outage history › Apr 29, 2026
Hyperstack partial outage on Apr 29, 2026: what happened
On Apr 29, 2026, the Hyperstack Service status page reported "NVIDIA Helm Repository Unreachable". About 3 hours 34 min: from Apr 29, 2026, 10:36 UTC to Apr 29, 2026, 14:11 UTC, by the official start and resolution times.
Hyperstack right now
At our last refresh (Oct 22, 2026, 12:35 UTC) Hyperstack was up: All Systems Operational.
- Started
- Apr 29, 2026, 10:36 UTC
- Resolved
- Apr 29, 2026, 14:11 UTC
- Duration
- 3 hours 34 min
- Official impact
- Major
- Affected
- Norway 1 Datacentre, Canada 1 Datacentre, Hyperstack Portal, Hyperstack API, US 1 DataCenter, Canada 2 Datacentre
- Source
- NVIDIA Helm Repository Unreachable on the Hyperstack Service status page
The Hyperstack Service status page rated the impact "Major": a partial outage. Some parts or some users were affected; it was not a complete outage.
What caused the Hyperstack partial outage?
The Hyperstack Service status page has not published a cause. When it identified the problem at 13:38 UTC on Apr 29, 2026, it said: "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."
When was it fixed?
The Hyperstack Service status page marked it resolved at Apr 29, 2026, 14:11 UTC, 3 hours 34 min after it started. Its resolution note: "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 ..."
Timeline of official updates
Every update the Hyperstack Service status page posted, oldest first. Times are UTC.
Apr 29, 2026, 10:36 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, 2026, 10:39 UTC investigating
We are continuing to investigate this issue.
Apr 29, 2026, 13:38 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, 2026, 14:11 UTC 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.
Hyperstack partial outage questions
What caused the Hyperstack partial outage on Apr 29, 2026?
The Hyperstack Service status page has not published a cause. When it identified the problem (Apr 29, 2026, 13:38 UTC) it said: "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 ..."
When was the Hyperstack partial outage on Apr 29, 2026 fixed?
The Hyperstack Service status page marked it resolved at Apr 29, 2026, 14:11 UTC, 3 hours 34 min after it started. Its resolution note: "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 ..."
How long did the Hyperstack partial outage last?
About 3 hours 34 min: from Apr 29, 2026, 10:36 UTC to Apr 29, 2026, 14:11 UTC, by the official start and resolution times.
Was Hyperstack completely down?
No. The Hyperstack Service status page rated the impact "Major": a partial outage. Some parts or some users were affected; it was not a complete outage. The affected parts listed were: Norway 1 Datacentre, Canada 1 Datacentre, Hyperstack Portal, Hyperstack API, US 1 DataCenter, Canada 2 Datacentre.
Which parts of Hyperstack were affected?
The Hyperstack Service status page listed: Norway 1 Datacentre, Canada 1 Datacentre, Hyperstack Portal, Hyperstack API, US 1 DataCenter, Canada 2 Datacentre.
Other recent Hyperstack incidents
- US-1 - Network Maintenance Sep 1, 2026, 23:26 UTC, 5 hours 36 min
- Emergency Maintenance - Hyperstack Platform and API Services Aug 27, 2026, 10:03 UTC, 11 hours 39 min
- Hyperstack Support Portal Migration Jul 30, 2026, 11:25 UTC, 3 hours 19 min
- Service degredation in CA1 Region Jul 7, 2026, 23:16 UTC, 9 hours 53 min
- API Degradation affecting all Regions Jun 1, 2026, 11:00 UTC, 6 hours 31 min
- Hyperstack API Degradation May 31, 2026, 20:45 UTC, 1 hour 29 min
Full Hyperstack outage history and biggest outages → · Recent outages across all services →
Quotes are the Hyperstack Service status page's own words, from the official incident. Is It Up or Down is independent and not affiliated with Hyperstack. Times are UTC.