Rootnet Outage History

Rootnet is up right now

Rootnet had 6 outages in the last 2 years totaling 80h 31m of downtime — averaging 0.2 incidents per month.

There were 6 Rootnet outages since July 15, 2024 totaling 80h 31m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://rootnet.network

Minor June 3, 2026

Decreased availability 185.173.20.0/24 subnet

Detected by Pingoru
Jun 03, 2026, 07:03 PM UTC
Resolved
Jun 03, 2026, 07:57 PM UTC
Duration
54m
Affected: Internet Uplink - BIT, Ede
Timeline · 3 updates
  1. investigating Jun 03, 2026, 07:03 PM UTC

    We are currently experiencing an issue that causes packet loss for traffic to the 185.173.20.0/24 subnet. This issue is being investigated by our network provider. We will update this message as more information becomes available. We expect the next update within 30 minutes.

  2. monitoring Jun 03, 2026, 07:18 PM UTC

    The issue was caused by a DDoS attack to an upstream provider. The traffic has been re-routed to resolve the issue.

  3. resolved Jun 03, 2026, 07:57 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice January 7, 2026

Unavailability Kerio

Detected by Pingoru
Jan 07, 2026, 10:05 AM UTC
Resolved
Jan 07, 2026, 10:00 AM UTC
Duration
—
Timeline · 1 update
  1. resolved Jan 07, 2026, 10:05 AM UTC

    During a routine renewal of Kerio's SSL/TLS certificates the server did not automatically reboot. After manually restarting Kerio all services are running smoothly again. No further downtime is expected.

Read the full incident report →

Minor November 17, 2025

Reduced mail deliverability

Detected by Pingoru
Nov 17, 2025, 10:27 AM UTC
Resolved
Nov 20, 2025, 01:15 PM UTC
Duration
3d 2h
Affected: Rootnet.email - WebmailBIT, EdeeuNetworks, AmsterdamRootnet.email - SMTP
Timeline · 6 updates
  1. investigating Nov 17, 2025, 10:27 AM UTC

    We are experiencing reduced deliverability for outgoing e-mails sent through our our mail-filter to specific providers such as Microsoft (@outlook,@live,@hotmail,@office365) and Yahoo (@yahoo) due to a blacklisting. We are investigating the cause and taking actions to resolve this issue.

  2. identified Nov 17, 2025, 12:09 PM UTC

    We have determined that the issue was caused by spambots abusing a large amount of unprotected webforms of our clients. We have contacted these clients and asked them to resolve the problem on their websites. We have also contacted Microsoft and Yahoo to delist our IP-addresses from their blacklists. Microsoft has confirmed they will delist our IP-adresses within 24-48 hours. We are still waiting for a response from Yahoo.

  3. monitoring Nov 17, 2025, 04:32 PM UTC

    Since 13:10 we no longer see mail deliverability issues for mails sent to Microsoft. Mails sent to Yahoo remain throttled. We are still waiting for their response in order to fully resolve the issue.

  4. monitoring Nov 18, 2025, 04:23 PM UTC

    We are still seeing Yahoo throttling mails sent through our platform. In order to work around this we will be adding additional IP-addresses to sent these e-mails. Yahoo remains very restricted however, and a definitive solution will require their cooperation.

  5. monitoring Nov 19, 2025, 09:31 AM UTC

    We are seeing significant improvements in mail deliverability to Yahoo. We are still monitoring the situation.

  6. resolved Nov 20, 2025, 01:15 PM UTC

    No further deliverability issues have been observed. The incident is resolved.

Read the full incident report →

Notice September 28, 2025

Degraded DNS Resolution

Detected by Pingoru
Sep 28, 2025, 07:44 AM UTC
Resolved
Sep 28, 2025, 08:21 AM UTC
Duration
36m
Affected: DNS - nsauth.myrootnet.nlDNS - nsauth.myrootnet.com
Timeline · 2 updates
  1. monitoring Sep 28, 2025, 07:44 AM UTC

    Between 09:25 and 09:35 our monitoring detected a degradation of the DNS performance. This degradation was caused by a DDoS attack. As of 09:35 the query performance has been restored. We are monitoring the situation for any possible new attacks.

  2. resolved Sep 28, 2025, 08:21 AM UTC

    DNS continues to be working as expected. The incident is resolved.

Read the full incident report →

Notice September 9, 2025

Reduced availability of DNS platform

Detected by Pingoru
Sep 09, 2025, 07:07 AM UTC
Resolved
Sep 09, 2025, 11:11 AM UTC
Duration
4h 4m
Affected: DNS - nsauth.myrootnet.nlDNS - nsauth.myrootnet.com
Timeline · 3 updates
  1. investigating Sep 09, 2025, 07:07 AM UTC

    We're seeing reduced availability of the DNS platform resulting in DNS queries not receiving an answer.

  2. monitoring Sep 09, 2025, 07:20 AM UTC

    We've seen a spike in traffic due to a DDoS. This resulted in reduced reachability of services like our DNS platform and thus failing DNS queries. The attack has been mitigated for now but we're closely monitoring the network traffic for deviations.

  3. resolved Sep 09, 2025, 11:11 AM UTC

    We're no longer seeing DDoS traffic and all services work as expected.

Read the full incident report →

Major July 16, 2024

Network disruption BIT, Ede

Detected by Pingoru
Jul 16, 2024, 03:38 AM UTC
Resolved
Jul 16, 2024, 03:46 AM UTC
Duration
8m
Affected: Internet Uplink - BIT, Ede
Timeline · 2 updates
  1. investigating Jul 16, 2024, 03:38 AM UTC

    We are currently experiencing an issue causing the IP-range 185.173.22.0/24 to be unavailable for parts of the internet. We are currently investigating this issue. We will update this post before 06:15

  2. resolved Jul 16, 2024, 03:46 AM UTC

    Our networkprovider has resolved the issue. Due to this outage, the IPv4 range 185.173.22.0/24 was unavailable for parts of the internet beteen 05:14 and 05:40. This outage is related to: https://rootnet.network/incidents/ng4kvmnh7wqv We have asked our provider to investigate both outages and determine the root cause of the issue.

Read the full incident report →