Hyperstack

Affected: US 1 DataCenter

Failure mode: A zone, region or data center became unavailable. Root cause: Hardware or facility. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-09-01 23:26 UTC

   Hyperstack services and resources running in the US1 region are experiencing a degradation in connectivity due a data center outage. The ETA for restoration is September 2nd 3:00 AM UTC [9PM MDT].

2. resolved 2026-09-02 05:01 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hyperstack's status page.

Affected: Hyperstack Portal, Hyperstack API

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-27 10:03 UTC

   We are performing an emergency maintenance on the Hyperstack platform and API Services to address a platform issue. During this window, the Hyperstack console and public API may be unavailable or return errors. Existing running workloads (VMs, containers, and Kubernetes...

2. investigating 2026-08-27 10:19 UTC

   We are continuing to investigate this issue.

3. identified 2026-08-27 12:27 UTC

   The issue has been identified and a fix is being implemented.

4. monitoring 2026-08-27 17:57 UTC

   A fix has been applied and the services are returning to normal operation. The console will be accessible again in a while along with the API services.

5. resolved 2026-08-27 21:42 UTC

   Emergency maintenance is complete. The Hyperstack console and API Services have been restored and are operating normally. All components have returned to full service . If you continue to experience issues, please contact our support team at support@hyperstack.cloud Thank you...

Excerpts are shortened. Read the full incident on Hyperstack's status page.

Affected: Hyperstack Portal

Failure mode: A schema or data migration caused the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-30 11:25 UTC

   As previously communicated via email we are currently in the process of transitioning the Hyperstack Support Solution. We will be temporarily disabling the Live Chat option but we will still be able to respond to queries over email via support@hyperstack.cloud. We apologies for...

2. resolved 2026-07-30 14:45 UTC

   The transition of the Hyperstack Support Solution is still in progress and we are adjusting this update for the Hyperstack Portal to be in a Maintenance window. The Live Chat option is still currently disable but we will still be able to respond to queries over email via...

Excerpts are shortened. Read the full incident on Hyperstack's status page.

Affected: Canada 1 Datacentre, Hyperstack Portal, Infrahub Customer Portal, Hyperstack API

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-07 23:16 UTC

   We are currently investigating an issue in the Canada-1 region following emergency maintenance. This has resulted in some hosts not becoming active following reboot. This has also resulted in a reduced selection of deployments available. We are working to resolve this issue as...

2. resolved 2026-07-08 09:09 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hyperstack's status page.

Affected: Norway 1 Datacentre, Canada 1 Datacentre, Hyperstack Portal, Hyperstack API, US 1 DataCenter, Canada 2 Datacentre

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-01 11:00 UTC

   We are investigating degraded API availability affecting the Hyperstack Console. Some API-dependent workflows may be degraded or unavailable.

2. resolved 2026-06-01 17:31 UTC

   Hotfix v1.51.5 has been successfully deployed for infrahub api. Server cpu load stable and apis are responding.

Excerpts are shortened. Read the full incident on Hyperstack's status page.

Affected: Hyperstack API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-31 20:45 UTC

   We are investigating degraded API availability affecting the Hyperstack Console. Some API-dependent workflows may be degraded or unavailable.

2. resolved 2026-05-31 22:14 UTC

   Hyperstack API availability has been restored.

Excerpts are shortened. Read the full incident on Hyperstack's status page.

Affected: Hyperstack Portal, Infrahub Customer Portal, Hyperstack API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-21 18:33 UTC

   Some customers may be unable to access the Hyperstack console or related services. We are working to restore access as quickly as possible.

2. monitoring 2026-05-21 19:35 UTC

   We have identified the issue and implemented a fix. Services have recovered, and customers should now be able to access the console normally. We will continue to monitor for stability.

3. resolved 2026-05-21 21:35 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hyperstack's status page.

Affected: Canada 1 Datacentre

Failure mode: Network, DNS, routing or connectivity failure. Root cause: Network or DNS. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-05-14 22:35 UTC

   Our monitoring has identified network issues that are affecting these two regions. This is currently under investigation and work is underway by our team to return service to expected levels.

2. investigating 2026-05-14 22:35 UTC

   We are continuing to investigate this issue.

3. monitoring 2026-05-15 03:40 UTC

   The issue appeared to be related to our DC networking, which impacted our external connectivity from the data center. Our engineers have applied a fix, and the network is back in the datacenter. All the services are back and working fine. We will be actively monitoring for any...

4. resolved 2026-05-15 09:21 UTC

   We are happy to advise that all network-related issues have been fully remediated, and services are working normally. We apologize for any inconvenience caused during this time. If you continue to experience any connectivity problems with resources in any of our regions, please...

Excerpts are shortened. Read the full incident on Hyperstack's status page.

Affected: Norway 1 Datacentre, Canada 1 Datacentre, Hyperstack Portal, Hyperstack API, US 1 DataCenter, Canada 2 Datacentre

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-04-29 10:36 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...

2. investigating 2026-04-29 10:39 UTC

   We are continuing to investigate this issue.

3. identified 2026-04-29 13:38 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...

4. resolved 2026-04-29 14:11 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...

Excerpts are shortened. Read the full incident on Hyperstack's status page.

Affected: Canada 1 Datacentre, Hyperstack Portal, Infrahub Customer Portal

Failure mode: Network, DNS, routing or connectivity failure. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-04-28 05:31 UTC

   We are currently investigating a network connectivity issue affecting customer VM reachability from the public internet in CANADA-1 (CA-1) Region. Our on-site team is actively engaged and working to resolve the fault. What we know: • The issue has been isolated to the network...

2. monitoring 2026-04-28 05:53 UTC

   The issue appeared to be related to internet routing with our DC Network Partners, which impacted our external connectivity from the data center. They have provided the fix, and the network is back again in the datacenter. All the services are back and working fine. We will be...

3. resolved 2026-04-28 07:00 UTC

   The issue impacting external connectivity from the data center has been fully resolved for all customers at 07.00 UTC. The root cause was identified as an internet routing issue with our data center network partners. Our DC Network Partners have implemented the required fix, and...

Excerpts are shortened. Read the full incident on Hyperstack's status page.

Affected: Canada 2 Datacentre

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-03-26 05:40 UTC

   We are currently aware of a network-related issue affecting our CANADA-2 Data Centre. Our engineering teams are actively investigating the matter. We will provide further updates on the status and progress as soon as they become available.

2. identified 2026-03-26 06:40 UTC

   We are currently investigating a network connectivity issue affecting customer VM reachability from the public internet. Our on-site team is actively engaged and working to resolve the fault. What we know: • The issue has been isolated to the network layer at the data centre...

3. monitoring 2026-03-26 08:03 UTC

   Our engineering teams have successfully implemented a fix at the network layer, and full reachability from the public internet to customer VMs has been restored. Additionally, the ability to create new VMs with functional network interfaces is now fully operational. We are...

4. resolved 2026-03-26 10:03 UTC

   We are happy to advise that all network-related issues have been fully remediated in the region, and services have returned to normal. We apologise for any inconvenience caused during this time. If you continue to experience any connectivity problems with resources in the...

Excerpts are shortened. Read the full incident on Hyperstack's status page.

Affected: Canada 1 Datacentre

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-20 09:10 UTC

   We are currently investigating an issue where newly created H100 virtual machines in our CANADA-1 (CA-1) Region may fail to launch and report an error during creation. Other VM/Flavor types and regions are not impacted. Our engineering teams are actively working to identify the...

2. identified 2026-03-20 11:13 UTC

   We have identified the root cause of the intermittent H100 VM creation failures in the CANADA-1 (CA-1) region. Our engineering team is now working on the fix and will monitor recovery as remediation progresses. We will provide another update once normal H100 VM provisioning has...

3. resolved 2026-03-20 13:41 UTC

   The issue affecting the H100 VM creation intermittently in the CANADA-1 (CA-1) region has been resolved. Our engineering team has completed fixing the impacted hosts and validated that new H100 VMs are launching successfully again. All systems in the CANADA-1 (CA-1) Datacentre...

Excerpts are shortened. Read the full incident on Hyperstack's status page.

Affected: Canada 1 Datacentre

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-05 03:15 UTC

   We are currently investigating intermittent failures to launch on-demand Kubernetes clusters in our CA1 region. When failing, the cluster build will respond with an error "Infrastructure reconciliation failed".

2. identified 2026-03-05 04:04 UTC

   The issue has been identified and a fix is being implemented.

3. resolved 2026-03-05 09:50 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hyperstack's status page.

Affected: Canada 1 Datacentre

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-02-10 14:35 UTC

   Investigating – Connectivity Issues in Canada (CA1) We are currently investigating an issue affecting newly created and restored virtual machines in our Canada (CA1) region, where some instances may not become reachable immediately after launch (e.g. SSH or network access). Our...

2. identified 2026-02-10 16:00 UTC

   The issue has been identified and service operations are beginning to recover. Our engineering teams are continuing to investigate the root cause and are working to fully remediate the problem as soon as possible.

3. identified 2026-02-10 22:18 UTC

   The root cause has been identified. Remediation work and validation are in progress and we are preparing to deploy a fix on the Hyperstack side.

4. resolved 2026-02-10 23:45 UTC

   After identifying and remediating the root cause, this problem has now been addressed. We have verified that everything in the Canada1 region has returned to normal operations.

Excerpts are shortened. Read the full incident on Hyperstack's status page.

Affected: Canada 1 Datacentre

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-02-03 15:07 UTC

   We are currently aware of a network-related issue affecting our Canada Data Centre. Our engineering teams are actively investigating the matter. We will provide further updates on the status and progress as soon as they become available.

2. identified 2026-02-03 15:59 UTC

   The issue has been identified as a control plane failure in CA1, and remediation efforts are underway.

3. identified 2026-02-04 01:09 UTC

   We are actively replacing the failed control plane to restore full system health. This action requires a momentary network reset. Some customers should expect a brief disconnection, during which all active network sessions will be interrupted for a few seconds. Service is...

4. monitoring 2026-02-04 02:27 UTC

   Engineering have been investigating intermittent connectivity interruptions in our Canada (CA1) region. Our engineering teams identified the issue as control-plane instability affecting routing services, which under certain conditions caused brief disruptions for a subset of...

5. monitoring 2026-02-04 10:28 UTC

   We have implemented additional stabilisation measures in our Canada (CA1) region and are currently seeing improved stability and healthy traffic levels. Our engineering teams have reduced routing instability and are continuing to monitor the region closely to ensure sustained...

6. resolved 2026-02-04 16:00 UTC

   We are happy to advise network-related issues have been remediated and services have returned to normal. We apologise for any inconvenience caused during this time.

Excerpts are shortened. Read the full incident on Hyperstack's status page.

Affected: US 1 DataCenter

Failure mode: Hardware, power, cooling or another physical failure. Root cause: Hardware or facility. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. monitoring 2026-01-05 22:08 UTC

   We are currently performing a storage maintenance in our US1 region to replace faulty drives. Impact: There is no expected disruption to running workloads. However, clients may experience minor performance variations during data rebalancing. We appreciate your patience and...

2. resolved 2026-01-06 02:43 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hyperstack's status page.

Affected: Canada 1 Datacentre

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2025-11-18 22:33 UTC

   We are currently performing a storage expansion in our CA1 region to support future growth and improve performance. Impact: There is no expected disruption to running workloads. However, clients may experience minor performance variations during data rebalancing. We appreciate...

2. resolved 2025-11-30 23:13 UTC

   Our storage expansion in CA1 has finished. Thank you for your patience.

Excerpts are shortened. Read the full incident on Hyperstack's status page.

Affected: Hyperstack Portal, Hyperstack API

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Cloudflare.

1. investigating 2025-11-18 11:58 UTC

   We are currently aware of a service disruption affecting HyperStack and API Services. This issue appears to be related to a wider incident on the Cloudflare Global Network, which Cloudflare is actively investigating. Our team is monitoring the situation closely and working to...

2. monitoring 2025-11-18 12:20 UTC

   We have implemented mitigations for the issue impacting the Cloudflare Global Network by rerouting our API calls externally, and we are seeing recovery across HyperStack and API Services. Our systems are operating normally, and we are continuing to closely monitor them for...

3. resolved 2025-11-19 17:39 UTC

   The Cloudflare Global Network incident has been fully resolved, and our long-running tests have shown no issues with the system. Our HyperStack and API Services are fully recovered and are operating normally. We are flagging that the issues have been resolved based on system...

Excerpts are shortened. Read the full incident on Hyperstack's status page.

Affected: Canada 1 Datacentre

Failure mode: The text does not say enough to tell. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2025-11-18 00:57 UTC

   We are currently performing a storage expansion in our CA1 region to support future growth and improve performance. Impact: There is no expected disruption to running workloads. However, clients may experience minor performance variations during data rebalancing. We appreciate...

2. resolved 2025-11-18 12:21 UTC

   We have completed the storage expansion and all operations have returned to normal.

Excerpts are shortened. Read the full incident on Hyperstack's status page.

Affected: Norway 1 Datacentre

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2025-11-13 23:25 UTC

   We have identified that our upstream ISPs in the NO1 datacentre are experiencing outages on certain network paths affecting connectivity to specific external locations. We are working with our ISPs to resolve this issue as soon as possible.

2. resolved 2025-11-14 05:19 UTC

   The upstream network links to Norway have been restored. Thank you for your patience.

Excerpts are shortened. Read the full incident on Hyperstack's status page.

Affected: US 1 DataCenter

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-10-17 22:14 UTC

   We are currently investigating reports of a service impairment impacting the US-1 region. Customers in this region may experience degraded performance or issues when deploying new resources. Our engineering team is actively working to identify the root cause. We will share...

2. resolved 2025-10-18 07:50 UTC

   The issue was identified and fixed.

Excerpts are shortened. Read the full incident on Hyperstack's status page.

Affected: US 1 DataCenter

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-10-13 19:45 UTC

   We are currently investigating reports of a potential service impairment affecting the US-1 region. Customers in this region may experience degraded services. Our engineering team is actively working to identify the root cause and will provide an update as soon as more...

2. resolved 2025-10-14 01:06 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hyperstack's status page.

Affected: Norway 1 Datacentre

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-10-09 07:11 UTC

   We are currently experiencing degraded performance on one of our upstream ISP connections in the NO1 datacentre. While network traffic continues to operate normally through redundant paths, customers may experience reduced available bandwidth until the affected link is fully...

2. identified 2025-10-09 07:22 UTC

   We have further identified that one of our upstream ISPs in the NO1 datacentre is experiencing outages on certain network paths affecting connectivity to specific external locations. To maintain stability, we have temporarily disabled the affected ISP link and rerouted all...

3. resolved 2025-10-09 16:34 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hyperstack's status page.

Affected: Hyperstack Portal

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2025-10-09 02:56 UTC

   We’re currently investigating an issue where the Hyperstack frontend is unable to communicate with backend services. All API endpoints are operational, but the dashboard and web interface may appear unavailable or unresponsive. Our engineers are actively investigating the...

2. resolved 2025-10-09 03:08 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hyperstack's status page.

Affected: Hyperstack API

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2025-10-07 23:01 UTC

   We will be performing maintenance on our storage backend. During this time there will be a slight performance impact which may cause storage-related operations to take longer to complete. Data resiliency will not be impacted.

2. resolved 2025-10-07 23:31 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hyperstack's status page.

Affected: Norway 1 Datacentre, Canada 1 Datacentre, Hyperstack Portal, Hyperstack API

Failure mode: Network, DNS, routing or connectivity failure. Root cause: Network or DNS. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. monitoring 2025-09-24 10:31 UTC

   We are aware of intermittent connectivity issues affecting access to Hyperstack VMs and the portal. - The issue appears to be related to internet routing, impacting certain regions (notably Asia). - This is not isolated to a specific ISP or customer environment. Our team is...

2. resolved 2025-09-25 02:33 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hyperstack's status page.

Affected: Canada 1 Datacentre

Failure mode: Hardware, power, cooling or another physical failure. Root cause: Hardware or facility. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-09-18 15:05 UTC

   We are currently experiencing an electrical issue that might affect some systems, more information to come.

2. monitoring 2025-09-18 15:51 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2025-09-18 15:56 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hyperstack's status page.

Affected: Canada 1 Datacentre

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2025-09-03 00:33 UTC

   We are currently experiencing a shortage of CPU-only nodes in the CA1 region. Customers may see errors when attempting to launch CPU-only instances. Our infrastructure team is actively working to bring additional capacity online to restore availability. GPU-backed instances are...

2. resolved 2025-09-03 00:58 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hyperstack's status page.

Affected: Norway 1 Datacentre

Failure mode: Hardware, power, cooling or another physical failure. Root cause: Hardware or facility. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-08-28 12:51 UTC

   We're experiencing intermittent electrical-related issues in NO1 region, a small selection of racks are currently identified as affected which in turn is causing unexpected reset of certain hosts. We're currently working with our on-site engineering team and are in the process...

2. resolved 2025-08-28 15:08 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hyperstack's status page.

Affected: Canada 1 Datacentre

Failure mode: A configuration change caused the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2025-08-27 22:48 UTC

   There will be a short outage to AI Studio while backend services are reconfigured.

2. identified 2025-08-27 22:48 UTC

   We are continuing to work on a fix for this issue.

3. resolved 2025-08-27 23:15 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hyperstack's status page.

Affected: Canada 1 Datacentre

Failure mode: Hardware, power, cooling or another physical failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2025-08-27 15:55 UTC

   At 1600 UTC we will be shutting down a storage node to perform maintenance. During this time there may be a slight decrease in IO performance for storage volumes.

2. identified 2025-08-27 22:48 UTC

   We are continuing to work on a fix for this issue.

3. resolved 2025-08-28 12:47 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hyperstack's status page.

Affected: Canada 1 Datacentre

Failure mode: Hardware, power, cooling or another physical failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-08-15 22:40 UTC

   We are currently investigating a downed storage node. There may be a slight effect on performance as the cluster rebalances.

2. identified 2025-08-15 22:52 UTC

   We have identified an inaccessible storage node and are attempting remediation to access.

3. monitoring 2025-08-15 22:58 UTC

   The storage node has been brought back online and the cluster is now recovering. We will continue to monitor performance. While recovery is performed there may be a minor performance impact to storage in customer VMs.

4. resolved 2025-08-18 03:11 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hyperstack's status page.

Affected: US 1 DataCenter

Failure mode: A zone, region or data center became unavailable. Root cause: Hardware or facility. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-08-12 17:38 UTC

   We are currently investigating an outage affecting multiple nodes in the US1 region. We are currently working toward finding a resolution at this time.

2. identified 2025-08-13 01:14 UTC

   We have been informed by our US1 data centre partner that a catastrophic power outage has impacted some pods and compute nodes, affecting a subset of customers. Our engineering team is working around the clock to bring new compute nodes online. For customers being affected, our...

3. resolved 2025-08-13 01:36 UTC

   We have successfully restored capacity in the US1 region following the recent outage at our data centre. Additional compute nodes have been brought online, and stock levels have been replenished to meet on-demand customer requirements. Our engineering and support teams will...

Excerpts are shortened. Read the full incident on Hyperstack's status page.

Affected: Canada 1 Datacentre

Failure mode: Hardware, power, cooling or another physical failure. Root cause: Hardware or facility. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-08-07 01:45 UTC

   We're currently investigating a storage-related issue in our CA1 region. A subset of storage nodes is unavailable, which is affecting performance and availability for some virtual machines and operations that rely on block storage. - You may experience delays launching,...

2. identified 2025-08-07 02:20 UTC

   Our CA1 data centre experienced a power disruption. While critical infrastructure responded as expected, some backend systems remain affected and we are actively working with our partners to restore full service.

3. monitoring 2025-08-07 03:20 UTC

   All services are now restored in CA1. However, clients might still expected IOs degradation when our storage nodes are being rebalanced.

4. resolved 2025-08-08 03:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hyperstack's status page.

Affected: Canada 1 Datacentre

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-08-05 16:23 UTC

   We are currently performing a storage expansion in our CA1 region to support future growth and improve performance. Impact: There is no expected disruption to running workloads. However, clients may experience minor performance variations during data rebalancing. We appreciate...

2. resolved 2025-08-06 18:47 UTC

   We have completed the Ceph expansion and all operations have returned to normal.

Excerpts are shortened. Read the full incident on Hyperstack's status page.

Affected: Norway 1 Datacentre

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-07-31 19:08 UTC

   We are currently investigating a network connectivity issue affecting the NO1 region. Our team is working to identify the root cause and restore connectivity as quickly as possible. Updates will follow as more information becomes available.

2. identified 2025-07-31 19:13 UTC

   The issue has been identified and a fix is being implemented.

3. resolved 2025-07-31 19:20 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hyperstack's status page.

Affected: Canada 1 Datacentre, Hyperstack API

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-07-16 21:30 UTC

   We are currently experiencing an API service issue affecting instance creation and network configuration changes. Our engineering team has identified the root cause and is actively working on remediation. Existing instances and network configurations remain unaffected.

2. identified 2025-07-16 21:40 UTC

   The issue has been identified and a fix is being implemented.

3. identified 2025-07-16 23:00 UTC

   We are continuing to work on a fix for this issue.

4. identified 2025-07-17 04:12 UTC

   The fix was successfully tested and we are actively rolling it out in our Canada1 region. VM creation and management will be recovered by GPU types, starting with the RTX A6000.

5. resolved 2025-07-17 09:41 UTC

   The issue impacting instance creation and network configuration changes in the CA1 region has been resolved. As of now, all GPU types have been restored to normal operation, and VM creation and management are functioning as expected. We appreciate your patience while our...

Excerpts are shortened. Read the full incident on Hyperstack's status page.

Affected: Canada 1 Datacentre

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2025-07-15 23:58 UTC

   We are currently performing a storage expansion in our CA1 region to support future growth and improve performance. Impact: There is no expected disruption to running workloads. However, clients may experience minor performance variations during data rebalancing. We appreciate...

2. resolved 2025-07-17 05:29 UTC

   The storage expansion has finished. Thank you for your patience.

Excerpts are shortened. Read the full incident on Hyperstack's status page.

Affected: Norway 1 Datacentre

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2025-07-09 23:40 UTC

   We are currently performing a storage expansion in our NO1 region to support future growth and improve performance. Impact: There is no expected disruption to running workloads. However, clients may experience minor performance variations during data rebalancing. We appreciate...

2. resolved 2025-07-10 03:10 UTC

   The expansion has finished. Thank you for your patience.

Excerpts are shortened. Read the full incident on Hyperstack's status page.

Affected: Canada 1 Datacentre

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2025-07-02 00:27 UTC

   We are currently performing a storage expansion in our CA1 region to support future growth and improve performance. Impact: There is no expected disruption to running workloads. However, clients may experience minor performance variations during data rebalancing. We appreciate...

2. resolved 2025-07-07 00:13 UTC

   The expansion has finished. Thank you for your patience.

Excerpts are shortened. Read the full incident on Hyperstack's status page.

Affected: Canada 1 Datacentre

Failure mode: A zone, region or data center became unavailable. Root cause: Hardware or facility. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2025-06-23 23:20 UTC

   NexGen wishes to inform you that Montreal is currently experiencing an extreme heatwave, with temperatures reaching up to 46°C. This unprecedented heat is placing significant strain on our data centre infrastructure in CA-1 region, potentially affecting system stability. We are...

2. resolved 2025-06-29 23:37 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hyperstack's status page.

Affected: US 1 DataCenter

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-06-23 23:14 UTC

   We are currently experiencing a disruption with Hyperstack services in the US1 region. Existing workloads continue to run without interruption; however, API calls to this region are temporarily unavailable. Our team is investigating and will provide updates as they become...

2. resolved 2025-06-24 00:45 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hyperstack's status page.

Affected: Canada 1 Datacentre

Failure mode: Hardware, power, cooling or another physical failure. Root cause: Hardware or facility. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-06-02 16:14 UTC

   We are currently addressing an issue within our CA1 region storage cluster. One of the storage nodes has experienced a failure and is being investigated. While the system is designed to self-heal and redistribute data automatically, you may notice temporary performance...

2. monitoring 2025-06-02 22:26 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2025-06-03 08:18 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hyperstack's status page.

Affected: US 1 DataCenter

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-05-26 03:09 UTC

   We are currently experiencing a disruption with Hyperstack services in the US1 region. Existing workloads continue to run without interruption; however, API calls to this region are temporarily unavailable. Our team is investigating and will provide updates as they become...

2. monitoring 2025-05-26 04:24 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2025-05-27 00:07 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hyperstack's status page.

Affected: Canada 1 Datacentre

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-05-23 04:59 UTC

   CA1 region experienced a complete network outage lasting approximately 5 minutes due to an upstream issue with our internet service provider. The disruption impacted all external connectivity, including access to public services and remote management. Internal services remained...

2. monitoring 2025-05-23 05:47 UTC

   We are observing ongoing degraded performance on a small number of routes. Most network traffic remains stable and unaffected. We are continuing to monitor the situation closely and are working with our upstream provider to ensure full resolution.

3. resolved 2025-05-23 14:39 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hyperstack's status page.

Affected: Canada 1 Datacentre

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-05-19 01:15 UTC

   We are currently performing a storage expansion in our CA1 region to support future growth and improve performance. Impact: There is no expected disruption to running workloads. However, clients may experience minor performance variations during data rebalancing. We appreciate...

2. monitoring 2025-05-19 01:15 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2025-05-19 23:01 UTC

   The storage expansion in CA1 has finished. Thank you for your understanding.

Excerpts are shortened. Read the full incident on Hyperstack's status page.

Affected: Canada 1 Datacentre

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2025-05-14 20:56 UTC

   We are currently performing a storage expansion in our CA1 region to support future growth and improve performance. Impact: There is no expected disruption to running workloads. However, clients may experience minor performance variations during data rebalancing. We appreciate...

2. resolved 2025-05-15 05:04 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hyperstack's status page.

Affected: US 1 DataCenter

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-05-13 05:39 UTC

   We are currently investigating a service outage affecting the US-1 Data Center. Please note that this incident does not impact any running workloads, but you may experience issues when launching new services. We sincerely apologise for the inconvenience and will provide further...

2. resolved 2025-05-13 06:18 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hyperstack's status page.

Affected: Canada 1 Datacentre

Failure mode: Hardware, power, cooling or another physical failure. Root cause: Hardware or facility. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-05-06 15:44 UTC

   We are currently addressing an issue within our CA1 region storage cluster. One of the storage nodes has experienced a failure and is in the process of being removed from the cluster. While the system is designed to self-heal and automatically redistribute data, you may...

2. monitoring 2025-05-06 19:34 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2025-05-08 00:30 UTC

   The cluster has now been rebalanced, and full data redundancy is restored.

Excerpts are shortened. Read the full incident on Hyperstack's status page.

Affected: Canada 1 Datacentre

Failure mode: Hardware, power, cooling or another physical failure. Root cause: Hardware or facility. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-05-01 00:36 UTC

   We are currently addressing an issue within our CA1 region storage cluster. One of the storage nodes has experienced a failure and is being removed from the cluster. While the system is designed to self-heal and redistribute data automatically, you may notice temporary...

2. monitoring 2025-05-01 00:37 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2025-05-02 20:07 UTC

   All maintenance on the storage cluster has completed successfully and all active monitoring checks are returning healthy results.

Excerpts are shortened. Read the full incident on Hyperstack's status page.