Hypernode Outage History

Hypernode is up right now

Hypernode had 27 outages in the last 2 years totaling 3h 10m of downtime — averaging 1.1 incidents per month.

There were 27 Hypernode outages since September 10, 2024 totaling 3h 10m of downtime. Each is summarised below — incident details, duration, and resolution information.

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

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 →

Notice September 10, 2024

DNS Maintenance issues

Detected by Pingoru
Sep 10, 2024, 10:47 AM UTC
Resolved
Sep 10, 2024, 01:22 PM UTC
Duration
2h 34m
Affected: Hypernode Servers
Timeline · 2 updates
  1. monitoring Sep 10, 2024, 10:47 AM UTC

    This morning we performed maintenance on our internal infrastructure, in preparation for a future migration. Shortly afterwards our support team started receiving a large amount of error reports related to DNS, and we performed a rollback at 10:38 this morning. Throughout the rest of the day we still received evidence that a small amount of visitors, with specific internet providers, were having problems resolving certain DNS records.

  2. resolved Sep 10, 2024, 01:22 PM UTC

    After extensive research and testing, we learned that our DNS provider performed maintenance this morning too, at the same time as our internal maintenance. During this maintenance they shut-off a DNS server that had been decommissioned 4 weeks ago. In preparation of this, we had changed our DNS settings 4 weeks ago to indicate that this old server should not longer be used. Unfortunately, it seems that certain servers from these ISP's are not respecting the 1 day validity (TTL / Time-to-live) on these DNS records, and were still contacting this old server, even though we indicated not to use those servers anymore 4 weeks ago. We worked with our DNS provider and the decommissioned server has been restored for now. We are working on contacting the ISP's that are not following the internet standards for DNS TTL, in order to prevent this issue from returning at a later date.

Read the full incident report →