- Detected by Pingoru
- Oct 13, 2026, 04:40 PM UTC
- Resolved
- Oct 20, 2026, 02:30 PM UTC
- Duration
- 6d 21h
Affected: Hyperstack PortalHyperstack API
Timeline · 4 updates
-
scheduled Oct 13, 2026, 04:40 PM UTC
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. If you have any questions or queries, please contact support via [email protected] Thank you!
-
scheduled Oct 20, 2026, 11:30 AM UTC
Maintenance will begin as scheduled in 60 minutes.
-
in progress Oct 20, 2026, 12:30 PM UTC
Scheduled maintenance is currently in progress. We will provide updates as necessary.
-
completed Oct 20, 2026, 02:30 PM UTC
The scheduled maintenance has been completed.
Read the full incident report →
- Detected by Pingoru
- Sep 01, 2026, 11:26 PM UTC
- Resolved
- Sep 02, 2026, 05:01 AM UTC
- Duration
- 5h 35m
Affected: US 1 DataCenter
Timeline · 2 updates
-
identified Sep 01, 2026, 11:26 PM 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].
-
resolved Sep 02, 2026, 05:01 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Aug 27, 2026, 10:03 AM UTC
- Resolved
- Aug 27, 2026, 09:42 PM UTC
- Duration
- 11h 39m
Affected: Hyperstack PortalHyperstack API
Timeline · 5 updates
-
investigating Aug 27, 2026, 10:18 AM 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 clusters) are not affected and continue to run; only management-plane operations are impacted. We expect our services to be restored soon. We will post an update every 60 minutes or sooner if the situation changes. We apologise for the short notice and any disruption caused.
-
investigating Aug 27, 2026, 10:19 AM UTC
We are continuing to investigate this issue.
-
identified Aug 27, 2026, 12:27 PM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Aug 27, 2026, 05:57 PM 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.
-
resolved Aug 27, 2026, 09:42 PM 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 [email protected] Thank you for your patience.
Read the full incident report →
- Detected by Pingoru
- Jul 30, 2026, 11:25 AM UTC
- Resolved
- Jul 30, 2026, 02:45 PM UTC
- Duration
- 3h 19m
Affected: Hyperstack Portal
Timeline · 2 updates
-
investigating Jul 30, 2026, 11:25 AM 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 [email protected]. We apologies for any inconvenience caused by this.
-
resolved Jul 30, 2026, 02:45 PM 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 [email protected]. We apologies for any inconvenience caused by this.
Read the full incident report →
- Detected by Pingoru
- Jul 07, 2026, 11:16 PM UTC
- Resolved
- Jul 08, 2026, 09:09 AM UTC
- Duration
- 9h 52m
Affected: Canada 1 DatacentreHyperstack PortalInfrahub Customer PortalHyperstack API
Timeline · 2 updates
-
investigating Jul 07, 2026, 11:16 PM 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 soon as possible.
-
resolved Jul 08, 2026, 09:09 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 01, 2026, 11:00 AM UTC
- Resolved
- Jun 01, 2026, 05:31 PM UTC
- Duration
- 6h 30m
Affected: Norway 1 DatacentreCanada 1 DatacentreHyperstack PortalHyperstack APIUS 1 DataCenterCanada 2 Datacentre
Timeline · 2 updates
-
investigating Jun 01, 2026, 04:04 PM UTC
We are investigating degraded API availability affecting the Hyperstack Console. Some API-dependent workflows may be degraded or unavailable.
-
resolved Jun 01, 2026, 05:31 PM UTC
Hotfix v1.51.5 has been successfully deployed for infrahub api. Server cpu load stable and apis are responding.
Read the full incident report →
- Detected by Pingoru
- May 31, 2026, 08:45 PM UTC
- Resolved
- May 31, 2026, 10:14 PM UTC
- Duration
- 1h 29m
Affected: Hyperstack API
Timeline · 2 updates
-
investigating May 31, 2026, 08:45 PM UTC
We are investigating degraded API availability affecting the Hyperstack Console. Some API-dependent workflows may be degraded or unavailable.
-
resolved May 31, 2026, 10:14 PM UTC
Hyperstack API availability has been restored.
Read the full incident report →
- Detected by Pingoru
- May 21, 2026, 06:33 PM UTC
- Resolved
- May 21, 2026, 09:35 PM UTC
- Duration
- 3h 1m
Affected: Hyperstack PortalInfrahub Customer PortalHyperstack API
Timeline · 3 updates
-
investigating May 21, 2026, 06:33 PM UTC
Some customers may be unable to access the Hyperstack console or related services. We are working to restore access as quickly as possible.
-
monitoring May 21, 2026, 07:35 PM 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.
-
resolved May 21, 2026, 09:35 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 14, 2026, 10:35 PM UTC
- Resolved
- May 15, 2026, 09:21 AM UTC
- Duration
- 10h 45m
Affected: Canada 1 Datacentre
Timeline · 4 updates
-
investigating May 14, 2026, 10:35 PM 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.
-
investigating May 14, 2026, 10:35 PM UTC
We are continuing to investigate this issue.
-
monitoring May 15, 2026, 04:40 AM 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 further issues. If you still encounter any issues with our services, please reach out to [email protected] for immediate help.
-
resolved May 15, 2026, 09:21 AM 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 contact our support team at [email protected] and reference this incident.
Read the full incident report →
- Detected by Pingoru
- Apr 29, 2026, 10:36 AM UTC
- Resolved
- Apr 29, 2026, 02:11 PM UTC
- Duration
- 3h 34m
Affected: Norway 1 DatacentreCanada 1 DatacentreHyperstack PortalHyperstack APIUS 1 DataCenterCanada 2 Datacentre
Timeline · 4 updates
-
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].
Read the full incident report →
- Detected by Pingoru
- Apr 28, 2026, 05:31 AM UTC
- Resolved
- Apr 28, 2026, 07:00 AM UTC
- Duration
- 1h 29m
Affected: Canada 1 DatacentreHyperstack PortalInfrahub Customer Portal
Timeline · 3 updates
-
investigating Apr 28, 2026, 05:31 AM 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 layer at the data centre level at CANADA-1 Region only • HyperStack UI Console is impacted, but all the API Services are operational • Internal control plane communication is unaffected, so your VMs are running normally, but external connectivity is impacted • VM-to-VM traffic within the platform is expected to be unaffected • Public internet traffic is unable to reach customer VMs beyond the default gateway We are working directly with our data centre team to restore full connectivity. A further update will be posted within once we have the fix implemented.
-
monitoring Apr 28, 2026, 06:20 AM 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 actively monitoring for any further issues. If you still encounter any issues with our services, please reach out to [email protected] for immediate help.
-
resolved Apr 28, 2026, 10:15 AM 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 connectivity has been restored. All services are back online and functioning normally for customers. We will continue to actively monitor the environment to ensure stability. If you continue to experience any issues with our services, please contact us at [email protected] for immediate assistance. Thank you for your patience and understanding.
Read the full incident report →
- Detected by Pingoru
- Mar 26, 2026, 05:40 AM UTC
- Resolved
- Mar 26, 2026, 10:03 AM UTC
- Duration
- 4h 23m
Affected: Canada 2 Datacentre
Timeline · 4 updates
-
investigating Mar 26, 2026, 05:40 AM 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.
-
identified Mar 26, 2026, 06:40 AM 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 level • Internal control plane communication is unaffected — your VMs are running normally • VM-to-VM traffic within the platform is expected to be unaffected • Public internet traffic is unable to reach customer VMs beyond the default gateway We are working directly with our data centre team to restore full connectivity. A further update will be posted within 30 minutes.
-
monitoring Mar 26, 2026, 08:40 AM 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 actively monitoring the stability across all network paths. A full Root Cause Analysis (RCA) will be conducted to prevent a recurrence of this failure.
-
resolved Mar 26, 2026, 01:16 PM 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 CANADA-2 region, please contact our support team at [email protected] and reference this incident.
Read the full incident report →
- Detected by Pingoru
- Mar 20, 2026, 09:10 AM UTC
- Resolved
- Mar 20, 2026, 01:41 PM UTC
- Duration
- 4h 30m
Affected: Canada 1 Datacentre
Timeline · 3 updates
-
investigating Mar 20, 2026, 09:10 AM 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 root cause and restore normal H100 VM provisioning. We will provide further updates as more information becomes available. If you have any further questions or queries, please contact support via [email protected]
-
identified Mar 20, 2026, 12:57 PM 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 been fully restored.
-
resolved Mar 20, 2026, 01:41 PM 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 are now operating normally. We apologise for any inconvenience this may have caused.
Read the full incident report →
- Detected by Pingoru
- Mar 05, 2026, 03:15 AM UTC
- Resolved
- Mar 05, 2026, 09:50 AM UTC
- Duration
- 6h 34m
Affected: Canada 1 Datacentre
Timeline · 3 updates
-
investigating Mar 05, 2026, 03:15 AM 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".
-
identified Mar 05, 2026, 04:04 AM UTC
The issue has been identified and a fix is being implemented.
-
resolved Mar 05, 2026, 09:50 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 10, 2026, 02:35 PM UTC
- Resolved
- Feb 10, 2026, 11:45 PM UTC
- Duration
- 9h 9m
Affected: Canada 1 Datacentre
Timeline · 4 updates
-
investigating Feb 10, 2026, 02:35 PM 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 engineering teams are actively working on mitigating the issue and restoring normal service. Existing running instances are not impacted. We will provide further updates as more information becomes available.
-
identified Feb 10, 2026, 06:01 PM 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.
-
identified Feb 10, 2026, 10:18 PM 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.
-
resolved Feb 10, 2026, 11:45 PM 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.
Read the full incident report →
- Detected by Pingoru
- Feb 03, 2026, 03:07 PM UTC
- Resolved
- Feb 04, 2026, 04:00 PM UTC
- Duration
- 1d
Affected: Canada 1 Datacentre
Timeline · 6 updates
-
investigating Feb 03, 2026, 03:07 PM 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.
-
identified Feb 03, 2026, 03:59 PM UTC
The issue has been identified as a control plane failure in CA1, and remediation efforts are underway.
-
identified Feb 04, 2026, 01:09 AM 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 expected to recover immediately following this action.
-
monitoring Feb 04, 2026, 10:27 AM 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 customer workloads. Since identification, we have had engineers working around the clock to isolate the trigger conditions and apply mitigations to stabilise the environment. These actions included controlled routing adjustments and workload rebalancing to reduce disruption while restoring normal operations.
-
monitoring Feb 04, 2026, 10:28 AM 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 recovery. While service is stable at this time, we will remain in an enhanced monitoring state and continue follow-up work to restore full resilience. Further updates will be provided as we confirm continued stability across CA1.
-
resolved Feb 04, 2026, 05:25 PM 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.
Read the full incident report →
- Detected by Pingoru
- Jan 05, 2026, 10:08 PM UTC
- Resolved
- Jan 06, 2026, 02:43 AM UTC
- Duration
- 4h 34m
Affected: US 1 DataCenter
Timeline · 2 updates
-
monitoring Jan 05, 2026, 10:08 PM 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 understanding. If you encounter any issues, please contact our support team.
-
resolved Jan 06, 2026, 02:43 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Nov 18, 2025, 10:33 PM UTC
- Resolved
- Nov 30, 2025, 11:13 PM UTC
- Duration
- 12d
Affected: Canada 1 Datacentre
Timeline · 2 updates
-
monitoring Nov 18, 2025, 10:33 PM 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.
-
resolved Nov 30, 2025, 11:13 PM UTC
Our storage expansion in CA1 has finished. Thank you for your patience.
Read the full incident report →
- Detected by Pingoru
- Nov 18, 2025, 11:58 AM UTC
- Resolved
- Nov 19, 2025, 05:39 PM UTC
- Duration
- 1d 5h
Affected: Hyperstack PortalHyperstack API
Timeline · 3 updates
-
investigating Nov 18, 2025, 11:58 AM 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 mitigate any impact on our platform. We will provide further updates as more information becomes available. Time detected: Nov 18, 2025 – 11:48 UTC
-
monitoring Nov 18, 2025, 12:20 PM 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 stability. We will provide a final update once the incident is fully resolved.
-
resolved Nov 19, 2025, 05:39 PM 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 stability tests following Cloudflare’s mitigation, and that no further impact is expected. Thank you for your patience throughout this incident. If you still face any issues, please don't hesitate to get in touch with our support via [email protected]
Read the full incident report →
- Detected by Pingoru
- Nov 13, 2025, 11:25 PM UTC
- Resolved
- Nov 14, 2025, 05:19 AM UTC
- Duration
- 5h 54m
Affected: Norway 1 Datacentre
Timeline · 2 updates
-
identified Nov 13, 2025, 11:25 PM 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.
-
resolved Nov 14, 2025, 05:19 AM UTC
The upstream network links to Norway have been restored. Thank you for your patience.
Read the full incident report →
- Detected by Pingoru
- Oct 17, 2025, 10:14 PM UTC
- Resolved
- Oct 18, 2025, 07:50 AM UTC
- Duration
- 9h 36m
Affected: US 1 DataCenter
Timeline · 2 updates
-
investigating Oct 17, 2025, 10:14 PM 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 further updates as soon as more information becomes available.
-
resolved Oct 18, 2025, 07:50 AM UTC
The issue was identified and fixed.
Read the full incident report →
- Detected by Pingoru
- Oct 13, 2025, 07:45 PM UTC
- Resolved
- Oct 14, 2025, 01:06 AM UTC
- Duration
- 5h 21m
Affected: US 1 DataCenter
Timeline · 2 updates
-
investigating Oct 13, 2025, 07:45 PM 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 information becomes available.
-
resolved Oct 14, 2025, 01:06 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Oct 09, 2025, 02:56 AM UTC
- Resolved
- Oct 09, 2025, 03:08 AM UTC
- Duration
- 11m
Affected: Hyperstack Portal
Timeline · 2 updates
-
monitoring Oct 09, 2025, 02:56 AM 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 connectivity issue between the frontend and backend. Further updates will be provided as soon as more information is available.
-
resolved Oct 09, 2025, 03:08 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Oct 07, 2025, 11:01 PM UTC
- Resolved
- Oct 07, 2025, 11:31 PM UTC
- Duration
- 30m
Affected: Hyperstack API
Timeline · 2 updates
-
identified Oct 07, 2025, 11:01 PM 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.
-
resolved Oct 07, 2025, 11:31 PM UTC
This incident has been resolved.
Read the full incident report →
Notice September 24, 2025 - Detected by Pingoru
- Sep 24, 2025, 10:31 AM UTC
- Resolved
- Sep 25, 2025, 02:33 AM UTC
- Duration
- 16h 2m
Affected: Norway 1 DatacentreCanada 1 DatacentreHyperstack PortalHyperstack API
Timeline · 2 updates
-
monitoring Sep 24, 2025, 10:31 AM 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 actively monitoring and investigating. Connectivity should be restored automatically as routing stabilises.
-
resolved Sep 25, 2025, 02:33 AM UTC
This incident has been resolved.
Read the full incident report →