Rootnet Outage History

Rootnet is up right now

Rootnet had 8 outages in the last 2 years totaling 129h 6m of downtime — averaging 0.3 incidents per month.

There were 8 Rootnet outages since September 9, 2025 totaling 129h 6m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://rootnet.network

Major October 12, 2026

Outgoing mail delivery issues

Detected by Pingoru
Oct 12, 2026, 07:59 AM UTC
Resolved
Oct 13, 2026, 07:54 AM UTC
Duration
23h 54m
Affected: Rootnet.email - WebmailBIT, EdeeuNetworks, AmsterdamRootnet.email - SMTP
Timeline · 8 updates
  1. investigating Oct 12, 2026, 07:59 AM UTC

    We are currently experiencing outgoing mail delivery issues. Because of this e-mails are delivered with a delay. This is currently being investigated by our upstream provider. We will provide updates as more information becomes available.

  2. investigating Oct 12, 2026, 09:06 AM UTC

    Our upstream provider is still investigating the issue.

  3. identified Oct 12, 2026, 10:41 AM UTC

    The upstream provider has identified the root cause and is working on a fix.

  4. identified Oct 12, 2026, 01:33 PM UTC

    The upstream provider is still working on a fix.

  5. identified Oct 12, 2026, 03:00 PM UTC

    The upstream provider has informed us they have created a fix and are currently deploying this fix. We are still awaiting for this fix to be deployed.

  6. identified Oct 12, 2026, 03:15 PM UTC

    We are still seeing errors on our side. We have asked our upstream provider to further investigate the issue.

  7. identified Oct 12, 2026, 10:07 PM UTC

    We are still in contact with the upstream provider. They are still investigating the issue and looking for a solution. We are still seeing a significant error and delay rate for e-mails being sent.

  8. resolved Oct 13, 2026, 07:54 AM UTC

    Our upstream provider has resolved the issue around 2:00 last night. We have continued monitoring the issue overnight to ensure everything is working correctly. All delayed mail has also been deliverd.

Read the full incident report →

Major September 8, 2026

Outage BIT

Detected by Pingoru
Sep 08, 2026, 02:55 AM UTC
Resolved
Sep 08, 2026, 03:36 AM UTC
Duration
41m
Affected: beheer.myrootnet.nlBIT, Ede
Timeline · 3 updates
  1. monitoring Sep 08, 2026, 02:55 AM UTC

    Due to an incident a subset of our VMs was down between 04:20 - 04:50. Not all VMs are affected. As of 04:40, the VMs are available again. The reason of the outage is under investigation.

  2. monitoring Sep 08, 2026, 03:20 AM UTC

    There was a partial power-outage at one of our racks in BIT. This has caused several hypervisors to reboot. These hypervisors are now running on the secondary power feed. We are currently in contact with BIT to get both power feed back online. As of 04:50 all VMs are operational again.

  3. resolved Sep 08, 2026, 03:36 AM UTC

    At approximately 04:20 power was lost at a single power feed during maintenance by the datacenter (BIT). During the failover to the secondary power feed a circuit breaker tripped causing several hypervisors to reboot. VMs were manually restarted after the reboot of the hypervisors and recovered between 04:45-04:50. All VMs were available again as of 04:50. Power of the secondary feed was restored at 05:20.

Read the full incident report →

Critical August 30, 2026

Packet loss on 185.173.20.X addresses

Detected by Pingoru
Aug 30, 2026, 03:03 PM UTC
Resolved
Aug 31, 2026, 03:11 PM UTC
Duration
1d
Affected: Internet Uplink - BIT, Ede
Timeline · 6 updates
  1. investigating Aug 30, 2026, 03:03 PM UTC

    We're seeing some packet loss on our 185.173.20.X range and we're currently investigating the cause of this. At 17.30 we will post an update or sooner if more information is available.

  2. identified Aug 30, 2026, 03:31 PM UTC

    The issue has been identified and been traced back to an ongoing DDoS attack in a neighboring network. We are in contact with the network provider to mitigate the issue.

  3. identified Aug 30, 2026, 04:22 PM UTC

    The network provider is implementing additional mitigations to lessen the pressure on their network infrastructure. We will stay in contact and update this incident once we know more.

  4. monitoring Aug 30, 2026, 05:34 PM UTC

    Both the network provider and NaWas have implemented sufficient mitigations to alleviate the pressure on their core network. There currently is no further impact on customer services, we keep monitoring the situation but expect no further issues.

  5. monitoring Aug 30, 2026, 09:34 PM UTC

    We are continuing to monitor for any further issues.

  6. resolved Aug 31, 2026, 03:11 PM UTC

    This incident has been resolved.

Read the full incident report →

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:00 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 →