Hypernode Outage History

Hypernode is up right now

Hypernode had 28 outages in the last 2 years totaling 3h 5m of downtime — averaging 1.2 incidents per month.

There were 28 Hypernode outages since November 7, 2024 totaling 3h 5m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://www.hypernode-status.com

Minor December 16, 2024

Cloud provisioning problems

Detected by Pingoru
Dec 16, 2024, 07:30 AM UTC
Resolved
Dec 16, 2024, 09:07 AM UTC
Duration
1h 36m
Affected: Hypernode Toolset / API / Control Panel
Timeline · 3 updates
  1. investigating Dec 16, 2024, 07:46 AM UTC

    We are experiencing cloud provisioning problems with our provider Combell. Affected services: Up/down grades, Hypernode and Brancher creation

  2. monitoring Dec 16, 2024, 08:26 AM UTC

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

  3. resolved Dec 16, 2024, 09:07 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor December 6, 2024

Our third-party DNS provider is under a DDoS attack, causing intermittent disruptions to our nameservers.

Detected by Pingoru
Dec 06, 2024, 01:45 PM UTC
Resolved
Dec 06, 2024, 02:39 PM UTC
Duration
53m
Affected: Third-Party Service Providers
Timeline · 2 updates
  1. identified Dec 06, 2024, 01:45 PM UTC

    Our external DNS provider is investigating the DDoS attack causing the issue and is working to resolve it as quickly as possible.

  2. resolved Dec 06, 2024, 02:39 PM UTC

    The issue has been resolved, and our external DNS provider has confirmed that their services are fully operational.

Read the full incident report →

Minor November 7, 2024

Degraded performance for DNS servers

Detected by Pingoru
Nov 07, 2024, 09:30 AM UTC
Resolved
Nov 07, 2024, 10:06 AM UTC
Duration
35m
Affected: Hypernode Servers
Timeline · 3 updates
  1. identified Nov 07, 2024, 09:53 AM UTC

    Some of our customers are experiencing DNS related problems with their Hypernode server. The problem has been identified, our team is implementing a solution to the problem.

  2. monitoring Nov 07, 2024, 10:02 AM UTC

    A fix has been implemented, we are monitoring the problem.

  3. resolved Nov 07, 2024, 10:06 AM UTC

    This incident has been resolved.

Read the full incident report →