Hyperstack Outage History

Hyperstack is up right now

Hyperstack had 42 outages in the last 2 years totaling 320h 27m of downtime, averaging 1.7 incidents per month.

There were 42 Hyperstack outages since May 1, 2025 totaling 320h 27m of downtime. Each is summarised below. Incident details, duration, and resolution information.

Source: status.hyperstack.cloud

Major September 18, 2025

CA1 - Electrical Issue

Detected by Pingoru
Sep 18, 2025, 03:05 PM UTC
Resolved
Sep 18, 2025, 03:56 PM UTC
Duration
50m
Affected: Canada 1 Datacentre
Timeline · 3 updates
  1. identified Sep 18, 2025, 03:05 PM UTC

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

  2. monitoring Sep 18, 2025, 03:51 PM UTC

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

  3. resolved Sep 18, 2025, 03:56 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor September 3, 2025

CPU-only Instance Availability in CA1

Detected by Pingoru
Sep 03, 2025, 12:33 AM UTC
Resolved
Sep 03, 2025, 12:58 AM UTC
Duration
24m
Affected: Canada 1 Datacentre
Timeline · 2 updates
  1. identified Sep 03, 2025, 12:33 AM 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 not affected.

  2. resolved Sep 03, 2025, 12:58 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 28, 2025

NO1- Some users may experience outages due to electrical issues.

Detected by Pingoru
Aug 28, 2025, 12:51 PM UTC
Resolved
Aug 28, 2025, 03:08 PM UTC
Duration
2h 17m
Affected: Norway 1 Datacentre
Timeline · 2 updates
  1. investigating Aug 28, 2025, 12:51 PM 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 of identifying an underlying cause and taking action.

  2. resolved Aug 28, 2025, 04:08 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 27, 2025

CA1 AI Studio Outage

Detected by Pingoru
Aug 27, 2025, 10:48 PM UTC
Resolved
Aug 27, 2025, 11:15 PM UTC
Duration
27m
Affected: Canada 1 Datacentre
Timeline · 3 updates
  1. identified Aug 27, 2025, 10:48 PM UTC

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

  2. identified Aug 27, 2025, 10:48 PM UTC

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

  3. resolved Aug 27, 2025, 11:15 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 27, 2025

CA1 Storage Node replacement

Detected by Pingoru
Aug 27, 2025, 03:55 PM UTC
Resolved
Aug 28, 2025, 12:47 PM UTC
Duration
20h 52m
Affected: Canada 1 Datacentre
Timeline · 3 updates
  1. identified Aug 27, 2025, 03:55 PM 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 Aug 27, 2025, 10:48 PM UTC

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

  3. resolved Aug 28, 2025, 12:47 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 15, 2025

CA1 - Storage Degradation

Detected by Pingoru
Aug 15, 2025, 10:40 PM UTC
Resolved
Aug 18, 2025, 03:11 AM UTC
Duration
2d 4h
Affected: Canada 1 Datacentre
Timeline · 4 updates
  1. investigating Aug 15, 2025, 10:40 PM UTC

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

  2. identified Aug 15, 2025, 10:52 PM UTC

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

  3. monitoring Aug 15, 2025, 10:58 PM 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 Aug 18, 2025, 03:11 AM UTC

    This incident has been resolved.

Read the full incident report →

Major August 12, 2025

US1 Outage

Detected by Pingoru
Aug 12, 2025, 05:38 PM UTC
Resolved
Aug 13, 2025, 01:36 AM UTC
Duration
7h 58m
Affected: US 1 DataCenter
Timeline · 3 updates
  1. investigating Aug 12, 2025, 05:38 PM 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 Aug 13, 2025, 01:14 AM 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 Customer Support team will be reaching out directly to coordinate replacement capacity. Please note there may be temporary reduced stock availability in the US1 region while recovery efforts continue. We will provide further updates as more information becomes available.

  3. resolved Aug 15, 2025, 01:09 AM 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 continue to monitor the environment closely to ensure stability. We thank you for your patience during the recovery process.

Read the full incident report →

Major August 7, 2025

Storage Service Outage in CA1

Detected by Pingoru
Aug 07, 2025, 01:45 AM UTC
Resolved
Aug 08, 2025, 03:00 AM UTC
Duration
1d 1h
Affected: Canada 1 Datacentre
Timeline · 4 updates
  1. investigating Aug 07, 2025, 01:45 AM 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, hibernating, or snapshotting instances. - Instances booting from volume may be temporarily unavailable or exhibit degraded I/O performance. - General instance operation is unaffected if you are using root disk or ephemeral. Our engineering team is working with our hardware partner to restore full service as soon as possible. We’ll continue to provide updates here as more information becomes available.

  2. identified Aug 07, 2025, 02:20 AM 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 Aug 07, 2025, 03:20 AM UTC

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

  4. resolved Aug 08, 2025, 03:00 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 31, 2025

NO1 Network Connectivity Issue

Detected by Pingoru
Jul 31, 2025, 07:08 PM UTC
Resolved
Jul 31, 2025, 07:20 PM UTC
Duration
12m
Affected: Norway 1 Datacentre
Timeline · 3 updates
  1. investigating Jul 31, 2025, 07:08 PM 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 Jul 31, 2025, 07:13 PM UTC

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

  3. resolved Jul 31, 2025, 07:20 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 16, 2025

API Service Degradation - Instance Creation Impacted

Detected by Pingoru
Jul 16, 2025, 09:30 PM UTC
Resolved
Jul 17, 2025, 09:41 AM UTC
Duration
12h 10m
Affected: Canada 1 DatacentreHyperstack API
Timeline · 5 updates
  1. investigating Jul 16, 2025, 09:30 PM 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 Jul 16, 2025, 09:40 PM UTC

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

  3. identified Jul 16, 2025, 11:00 PM UTC

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

  4. identified Jul 17, 2025, 04:12 AM 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 Jul 17, 2025, 09:41 AM 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 engineering team worked to implement and verify the solution.

Read the full incident report →

Minor July 9, 2025

Storage Expansion in NO1

Detected by Pingoru
Jul 09, 2025, 11:40 PM UTC
Resolved
Jul 10, 2025, 03:10 AM UTC
Duration
3h 29m
Affected: Norway 1 Datacentre
Timeline · 2 updates
  1. monitoring Jul 09, 2025, 11:40 PM 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 your patience and understanding. If you encounter any issues, please contact our support team.

  2. resolved Jul 10, 2025, 03:10 AM UTC

    The expansion has finished. Thank you for your patience.

Read the full incident report →

Notice June 23, 2025

Potential Impact on Service Stability Due to Extreme Heat in CA-1

Detected by Pingoru
Jun 23, 2025, 11:20 PM UTC
Resolved
Jun 29, 2025, 11:37 PM UTC
Duration
6d
Affected: Canada 1 Datacentre
Timeline · 2 updates
  1. monitoring Jun 23, 2025, 11:20 PM 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 actively monitoring the situation and are implementing measures to minimize any impact on your services. We appreciate your understanding and continued support during this time.

  2. resolved Jun 29, 2025, 11:37 PM UTC

    This incident has been resolved.

Read the full incident report →

Major June 23, 2025

Disruption with Hyperstack services in US1

Detected by Pingoru
Jun 23, 2025, 11:14 PM UTC
Resolved
Jun 24, 2025, 12:45 AM UTC
Duration
1h 31m
Affected: US 1 DataCenter
Timeline · 2 updates
  1. identified Jun 23, 2025, 11:14 PM 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 available. We appreciate your patience.

  2. resolved Jun 24, 2025, 12:45 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 2, 2025

CA1 - Temporary Storage Performance Degradation

Detected by Pingoru
Jun 02, 2025, 04:14 PM UTC
Resolved
Jun 03, 2025, 08:18 AM UTC
Duration
16h 3m
Affected: Canada 1 Datacentre
Timeline · 3 updates
  1. investigating Jun 02, 2025, 04:14 PM 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 degradation during this process. Our engineering team is actively monitoring the situation to ensure a swift and smooth recovery. We will provide updates as the recovery progresses.

  2. monitoring Jun 02, 2025, 10:26 PM UTC

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

  3. resolved Jun 03, 2025, 08:18 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 23, 2025

CA1 Region External Network Degradation

Detected by Pingoru
May 23, 2025, 04:59 AM UTC
Resolved
May 23, 2025, 02:39 PM UTC
Duration
9h 40m
Affected: Canada 1 Datacentre
Timeline · 3 updates
  1. investigating May 23, 2025, 04:59 AM 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 operational. While connectivity has since been restored, the region is currently experiencing degraded network performance. Users may notice increased latency and reduced bandwidth for inbound and outbound connections. We are actively monitoring the situation and working to resolve the issue and restore full performance.

  2. monitoring May 23, 2025, 05:47 AM 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 May 23, 2025, 02:39 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 19, 2025

Ceph Storage Expansion in CA1

Detected by Pingoru
May 19, 2025, 01:15 AM UTC
Resolved
May 19, 2025, 11:01 PM UTC
Duration
21h 46m
Affected: Canada 1 Datacentre
Timeline · 3 updates
  1. investigating May 19, 2025, 01:15 AM 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 your patience and understanding. If you encounter any issues, please contact our support team.

  2. monitoring May 19, 2025, 01:15 AM UTC

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

  3. resolved May 19, 2025, 11:01 PM UTC

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

Read the full incident report →

Notice May 13, 2025

US-1 Service Outage

Detected by Pingoru
May 13, 2025, 05:39 AM UTC
Resolved
May 13, 2025, 06:18 AM UTC
Duration
39m
Affected: US 1 DataCenter
Timeline · 2 updates
  1. identified May 13, 2025, 05:39 AM 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 updates as we learn more. Thank you for your patience.

  2. resolved May 13, 2025, 06:18 AM UTC

    This incident has been resolved.

Read the full incident report →