Exonet Outage History

Exonet is up right now

Exonet had 19 outages in the last 2 years totaling 718h 16m of downtime, averaging 0.8 incidents per month.

There were 19 Exonet outages since October 26, 2024 totaling 718h 16m of downtime. Each is summarised below. Incident details, duration, and resolution information.

Source: exonetstatus.com

Minor September 1, 2026

Increased latency on requests

Detected by Pingoru
Sep 01, 2026, 01:20 PM UTC
Resolved
Sep 10, 2026, 09:27 PM UTC
Duration
9d 8h
Affected: Object storage
Timeline · 4 updates
  1. investigating Sep 01, 2026, 01:20 PM UTC

    After exposing the replaced node to production workloads we noticed some increased latency in the responses.

  2. monitoring Sep 01, 2026, 01:28 PM UTC

    One of the network optics seemed to drop a tiny fraction of it's traffic causing intermittent timeouts. The redundant network path (of a redundant node) has been disabled resulting in regular response times. We will be monitoring the performance closely while we take steps to replace the faulty optic.

  3. monitoring Sep 01, 2026, 01:28 PM UTC

    We are continuing to monitor for any further issues.

  4. resolved Sep 10, 2026, 09:27 PM UTC

    During a short maintenance window, we restored network redundancy and upgraded the software to the latest versions. This incident is now fully solved.

Read the full incident report →

Minor August 26, 2026

Object Storage - Performance degradation

Detected by Pingoru
Aug 26, 2026, 12:09 PM UTC
Resolved
Sep 01, 2026, 12:12 PM UTC
Duration
6d
Affected: Object storageContainer registry
Timeline · 5 updates
  1. investigating Aug 26, 2026, 12:09 PM UTC

    Our monitoring detected increased latency on a part of our storage platform. Engineers are currently investigating the issue. Customers may experience degraded performance on some services until the issue has been resolved.

  2. identified Aug 26, 2026, 12:10 PM UTC

    The issue has been identified and a fix is being implemented.

  3. identified Aug 27, 2026, 01:23 PM UTC

    We are continuing to work on a fix for this issue.

  4. monitoring Aug 31, 2026, 09:00 AM UTC

    The underlying issue preventing the healing process from completing has been resolved. The process has since finished successfully and data redundancy is fully restored. Some background maintenance activity is still running, which is expected. We will continue to monitor the situation closely.

  5. resolved Sep 01, 2026, 12:12 PM UTC

    The last background maintenance has successfully completed.

Read the full incident report →

Major August 10, 2026

Service degradation on s3 platform

Detected by Pingoru
Aug 10, 2026, 08:19 AM UTC
Resolved
Aug 10, 2026, 09:04 AM UTC
Duration
45m
Affected: BuildsDeploymentsObject storageContainer registry
Timeline · 3 updates
  1. identified Aug 10, 2026, 08:19 AM UTC

    We are currently investigating a issue with our s3 platform which also affects our ci/cd and registry services.

  2. monitoring Aug 10, 2026, 08:38 AM UTC

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

  3. resolved Aug 10, 2026, 09:04 AM UTC

    This incident has been resolved

Read the full incident report →

Major July 6, 2026

Rate limit for builds & deployments

Detected by Pingoru
Jul 06, 2026, 08:30 AM UTC
Resolved
Jul 06, 2026, 09:55 AM UTC
Duration
1h 25m
Affected: BuildsDeployments
Timeline · 2 updates
  1. investigating Jul 06, 2026, 08:30 AM UTC

    We are currently hitting rate limits for builds & deployments that use GitHub.

  2. resolved Jul 06, 2026, 09:55 AM UTC

    This incident has been resolved.

Read the full incident report →

Major July 1, 2026

Temporary telephone service disruption

Detected by Pingoru
Jul 01, 2026, 10:46 AM UTC
Resolved
Jul 01, 2026, 02:05 PM UTC
Duration
3h 18m
Affected: Customer Service
Timeline · 5 updates
  1. investigating Jul 01, 2026, 10:46 AM UTC

    We are currently unavailable or difficult to reach by phone on both our office number and our emergency support number. For any questions or urgent matters, please contact us by email or ticket so we can follow up as soon as possible.

  2. investigating Jul 01, 2026, 11:58 AM UTC

    We are continuing to investigate this issue.

  3. investigating Jul 01, 2026, 12:12 PM UTC

    Issues have been resolved

  4. investigating Jul 01, 2026, 02:04 PM UTC

    We are continuing to investigate this issue.

  5. resolved Jul 01, 2026, 02:05 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 8, 2026

Nameservers - Performance degradation

Detected by Pingoru
Jun 08, 2026, 12:14 PM UTC
Resolved
Jun 09, 2026, 12:50 PM UTC
Duration
1d
Affected: ns1.exonet.nlns2.exonet.nlns3.exonet.eu
Timeline · 3 updates
  1. investigating Jun 08, 2026, 12:14 PM UTC

    Our monitoring has detected performance issues on our DNS nameservers. Engineers are currently investigating the issue. Initial indications point to a routing-related problem. We are actively investigating and monitoring the situation. Customers may experience degraded performance on DNS services until the issue has been resolved.

  2. monitoring Jun 08, 2026, 12:38 PM UTC

    Connectivity to ns2 seems to have stabilized. We have not observed any further issues at this time. We will continue to closely monitor the situation and provide updates if anything changes.

  3. resolved Jun 09, 2026, 12:50 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 2, 2026

Network issues due to DDoS

Detected by Pingoru
Jun 02, 2026, 08:30 PM UTC
Resolved
Jun 02, 2026, 10:15 PM UTC
Duration
1h 45m
Affected: Ede
Timeline · 4 updates
  1. investigating Jun 02, 2026, 08:30 PM UTC

    We're seeing network issues on a limited part of our network due to a DDoS. Engineers are currently investigating the issue. Customers may experience degraded performance on some services until the issue has been resolved.

  2. monitoring Jun 02, 2026, 08:56 PM UTC

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

  3. monitoring Jun 02, 2026, 08:56 PM UTC

    We are continuing to monitor for any further issues.

  4. resolved Jun 03, 2026, 10:57 AM UTC

    This incident has been resolved.

Read the full incident report →

Major June 2, 2026

Network issues

Detected by Pingoru
Jun 02, 2026, 05:45 PM UTC
Resolved
Jun 02, 2026, 06:52 PM UTC
Duration
1h 6m
Affected: EdeCompute
Timeline · 2 updates
  1. investigating Jun 02, 2026, 05:45 PM UTC

    We're seeing network issues on a limited part of our network. Engineers are currently investigating the issue. Customers may experience degraded performance on some services until the issue has been resolved.

  2. resolved Jun 02, 2026, 06:52 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 7, 2026

Deployment of mitigations for "Dirty Frag" (CVE-2026-43284)

Detected by Pingoru
May 07, 2026, 08:30 PM UTC
Resolved
May 07, 2026, 10:22 PM UTC
Duration
1h 52m
Affected: ComputeManaged Apps
Timeline · 2 updates
  1. identified May 07, 2026, 09:00 PM UTC

    We're currently deploying mitigations for the newly disclosed “Dirty Frag” (CVE-2026-43284) vulnerability. This issue affects the Linux kernel and may allow local privilege escalation to root access.

  2. resolved May 07, 2026, 10:15 PM UTC

    All mitigations have been applied, and the affected services are no longer vulnerable. A Linux kernel update is not yet available, as the embargo on this security issue was broken prematurely. We will deploy an updated kernel as soon as it becomes available. Any additional maintenance required for kernel updates will be announced by email.

Read the full incident report →

Notice April 29, 2026

Deployment of mitigations for "Copy Fail" (CVE-2026-31431)

Detected by Pingoru
Apr 29, 2026, 06:45 PM UTC
Resolved
Apr 29, 2026, 09:45 PM UTC
Duration
3h
Affected: ComputeBuildsManaged AppsDeploymentsContainer registry
Timeline · 3 updates
  1. identified Apr 29, 2026, 07:57 PM UTC

    We're currently deploying updates and mitigations for the newly disclosed “Copy Fail” (CVE-2026-31431) vulnerability. This issue affects the Linux kernel and may allow local privilege escalation to root access. Some services may experience brief interruptions while updates are being deployed.

  2. monitoring Apr 29, 2026, 09:12 PM UTC

    All updates and mitigations have been applied, and the affected services are no longer vulnerable. A Linux kernel update is not yet available, as Linux distributions were not informed in advance of this disclosure. We will deploy an updated kernel as soon as it becomes available. Any additional maintenance required for kernel updates will be announced by email.

  3. resolved May 01, 2026, 11:53 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 22, 2026

Mail delivery issues srv02.exofilter.com

Detected by Pingoru
Apr 22, 2026, 09:00 AM UTC
Resolved
May 04, 2026, 12:23 PM UTC
Duration
12d 3h
Affected: Exofilter
Timeline · 4 updates
  1. identified Apr 22, 2026, 12:24 PM UTC

    We are currently experiencing outgoing mail delivery issues from srv02.exofilter.com to Microsoft/Outlook services. Our team is investigating the problem and working on a resolution. Updates will follow as more information becomes available.

  2. identified Apr 23, 2026, 09:32 AM UTC

    Microsoft/Outlook (SNDS) has reported an issue that may result in certain IP addresses being temporarily rejected at higher rates. They are actively investigating the problem. We are exploring alternative solutions and working to contact Microsoft regarding the ongoing issues.

  3. monitoring Apr 28, 2026, 03:13 PM UTC

    We are no longer experiencing delivery issues from srv02.exofilter.com to Microsoft/Outlook services. We will be moving customers back to srv02.exofilter.com this week and we will continue to monitor the situation.

  4. resolved May 04, 2026, 12:23 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice December 10, 2025

Emergency network maintenance

Detected by Pingoru
Dec 10, 2025, 09:57 PM UTC
Resolved
Dec 11, 2025, 12:11 AM UTC
Duration
2h 13m
Timeline · 3 updates
  1. investigating Dec 10, 2025, 09:57 PM UTC

    We would like to inform you about urgent maintenance on our core network this evening. One of our core network switches is currently not functioning properly, reducing redundancy, so we will perform a controlled reboot to restore full resilience and prevent potential full outages if other components fail. This maintenance will cause an interruption of the internet connection.

  2. monitoring Dec 10, 2025, 10:42 PM UTC

    The maintenance has been completed, we are monitoring the network and situation currently.

  3. resolved Dec 11, 2025, 12:11 AM UTC

    This incident has been resolved.

Read the full incident report →

Major November 25, 2025

Container registry - Outage

Detected by Pingoru
Nov 25, 2025, 06:41 PM UTC
Resolved
Nov 25, 2025, 08:10 PM UTC
Duration
1h 29m
Affected: BuildsContainer registry
Timeline · 5 updates
  1. investigating Nov 25, 2025, 06:41 PM UTC

    We are experiencing a partial outage in our container registry infrastructure. Engineers are currently investigating the issue. Customers may experience failed builds and deployments until the issue has been resolved.

  2. investigating Nov 25, 2025, 06:42 PM UTC

    We are continuing to investigate this issue.

  3. identified Nov 25, 2025, 06:58 PM UTC

    The issue has been identified and a fix is being implemented.

  4. monitoring Nov 25, 2025, 08:03 PM UTC

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

  5. resolved Nov 25, 2025, 08:10 PM UTC

    This incident has been resolved.

Read the full incident report →

Major November 18, 2025

Cloudflare - Outage

Detected by Pingoru
Nov 18, 2025, 12:04 PM UTC
Resolved
Nov 18, 2025, 02:47 PM UTC
Duration
2h 42m
Affected: Cloudflare Amsterdam, Netherlands - (AMS)Cloudflare CDN/Cache
Timeline · 5 updates
  1. identified Nov 18, 2025, 12:04 PM UTC

    Cloudflare experiences Global Network issues. Cloudflare is aware of, and investigating an issue which potentially impacts multiple customers.

  2. identified Nov 18, 2025, 12:27 PM UTC

    Cloudflare is seeing services recover, but customers may continue to observe higher-than-normal error rates as they continue remediation efforts.

  3. identified Nov 18, 2025, 01:12 PM UTC

    Cloudflare has identified the issue and a fix is being implemented.

  4. identified Nov 18, 2025, 02:02 PM UTC

    Cloudflare is continuing working on restoring application services.

  5. resolved Nov 18, 2025, 02:47 PM UTC

    Cloudflare has implemented a fix and believes the incident is now resolved. They are continuing to monitor for errors to ensure all services are back to normal.

Read the full incident report →

Major May 26, 2025

Compute - Outage

Detected by Pingoru
May 26, 2025, 02:39 PM UTC
Resolved
May 26, 2025, 03:06 PM UTC
Duration
26m
Affected: Compute
Timeline · 4 updates
  1. investigating May 26, 2025, 02:39 PM UTC

    We are experiencing a partial outage on our virtualization platform. Engineers are currently investigating the issue. Customers may experience downtime on some services until the issue has been resolved.

  2. identified May 26, 2025, 02:43 PM UTC

    A single virtualization node has crashed. The servers on this node are now starting on another node.

  3. monitoring May 26, 2025, 02:57 PM UTC

    All affected servers have been successfully restarted. We are currently verifying that all services are functioning as expected and will continue to closely monitor the situation for any further issues.

  4. resolved May 26, 2025, 03:06 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 14, 2025

Incoming phone calls

Detected by Pingoru
May 14, 2025, 07:00 AM UTC
Resolved
May 14, 2025, 08:33 AM UTC
Duration
1h 33m
Affected: Customer Service
Timeline · 2 updates
  1. identified May 14, 2025, 07:53 AM UTC

    We are currently experiencing issues with incoming phone calls. Our team is investigating the cause in collaboration with our telecom provider. While we work to resolve this issue, you can reach us via email. We will call you back as soon as possible.

  2. resolved May 14, 2025, 08:33 AM UTC

    This incident has been resolved.

Read the full incident report →

Major January 29, 2025

Storage - Incident

Detected by Pingoru
Jan 29, 2025, 12:18 AM UTC
Resolved
Jan 29, 2025, 12:18 AM UTC
Duration
–
Timeline · 2 updates
  1. resolved Jan 29, 2025, 12:28 PM UTC

    Several servers on our platform went into a read-only state because a storage volume was full. At this moment it's unclear why that happened. The storage system did not indicate that the volume was (almost) full and a setting to automatically resize the volume was configured. After the volume was manually resized, we restarted the affected servers to prevent any further issues. We are currently investigating with our supplier how we can prevent this from happening in the future.

  2. postmortem Feb 04, 2025, 03:19 PM UTC

    Together with our supplier we’ve identified a setting to adjust in our storage cluster to prevent this issue from happening in the future. We’ve also optimized our monitoring to identify any issues like these at an earlier stage.

Read the full incident report →

Minor January 21, 2025

Storage - Failover

Detected by Pingoru
Jan 21, 2025, 01:32 PM UTC
Resolved
Jan 22, 2025, 02:01 AM UTC
Duration
12h 28m
Affected: Shared storageStorage
Timeline · 3 updates
  1. investigating Jan 21, 2025, 01:32 PM UTC

    We've identified an issue with a storage controller. Our backup controller has automatically and successfully taken over through a failover process. While there is no impact on operations, we are currently operating with reduced redundancy until the controller can be brought back online.

  2. investigating Jan 21, 2025, 01:42 PM UTC

    We are continuing to investigate this issue.

  3. resolved Jan 22, 2025, 02:01 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice October 26, 2024

Service Disruption: Email Delivery Blocked Due to Spam Filter Check Failure on cbl.abuseat.org

Detected by Pingoru
Oct 26, 2024, 08:42 AM UTC
Resolved
Oct 26, 2024, 08:42 AM UTC
Duration
–
Timeline · 1 update
  1. resolved Oct 26, 2024, 08:42 AM UTC

    Incident: Since last night, our email services have been partially unavailable due to issues with checks on cbl.abuseat.org. This resulted in both incoming and outgoing email being blocked because spam filtering could not be performed. Action Taken: This morning, after receiving reports from users who could not send or receive emails, we immediately initiated an investigation. At 10:08, the cbl.abuseat.org list was removed from the spam check in our platform, allowing all email services to resume normal functionality. Impact: Unfortunately, emails that were blocked will not be delivered retroactively. However, recipients should be notified that emails were blocked. Follow-up: If there are still issues with email, please contact us for further assistance.

Read the full incident report →