Snel.com Outage History

Started Oct 29, 2026, 07:38 AM UTC· resolved Oct 29, 2026, 11:25 AM UTC

1. investigating Oct 29, 2026, 07:38 AM UTC

   We are currently investigating this incident.

2. investigating Oct 29, 2026, 07:38 AM UTC

   We are currently investigating this incident..

3. identified Oct 29, 2026, 08:48 AM UTC

   We have identified the issue and are continuing to work on a fix for this incident..

4. identified Oct 29, 2026, 08:48 AM UTC

   We have identified the issue and are continuing to work on a fix for this incident.

5. identified Oct 29, 2026, 09:03 AM UTC

   Systems are coming back online. We expect full service to be restored within 30 minutes..

6. identified Oct 29, 2026, 09:03 AM UTC

   Systems are coming back online. We expect full service to be restored within 30 minutes.

7. identified Oct 29, 2026, 09:41 AM UTC

   Currently all hypervisors are up again, we're still working on clearing all alerts..

8. identified Oct 29, 2026, 09:41 AM UTC

   Currently all hypervisors are up again, we're still working on clearing all alerts.

9. resolved Oct 29, 2026, 11:25 AM UTC

   This incident has been resolved. All alerts are cleared. Customers with unmanaged services are advised to check that their servers and applications are running as expected. If you notice any remaining issues with your service, please contact [[email protected]](mailto:[email protected]). Our engineers are investigating the root cause. In the coming days we will prepare a Reason for Outage (RFO) report that describes what happened, how we resolved it, and what steps we are taking to prevent it from happening again. If you would like a copy of the RFO once it is available, please email [[email protected]](mailto:[email protected]) with your customer details. We apologize for the inconvenience and thank you for your patience..

10. resolved Oct 29, 2026, 11:25 AM UTC

    This incident has been resolved. All alerts are cleared. Customers with unmanaged services are advised to check that their servers and applications are running as expected. If you notice any remaining issues with your service, please contact [[email protected]](mailto:[email protected]). Our engineers are investigating the root cause. In the coming days we will prepare a Reason for Outage (RFO) report that describes what happened, how we resolved it, and what steps we are taking to prevent it from happening again. If you would like a copy of the RFO once it is available, please email [[email protected]](mailto:[email protected]) with your customer details. We apologize for the inconvenience and thank you for your patience.

Read the full incident report →

Started Sep 30, 2026, 04:07 PM UTC· resolved Sep 30, 2026, 05:40 PM UTC

1. investigating Sep 30, 2026, 04:07 PM UTC

   We are encountering an outage in rack 2 in SmartDC datacenter. This outage might result in unavailability of your services. Our data center engineers are on-site to investigate the cause of this issue. Please be assured that we will do our utmost best to keep the downtime as short as possible. **Incident start**: 2026/09/30 18:407 CEST **Impact**: Rackswitches and servers in rack 2 are down

2. investigating Sep 30, 2026, 04:07 PM UTC

   We are encountering an outage in rack 2 in SmartDC datacenter. This outage might result in unavailability of your services. Our data center engineers are on-site to investigate the cause of this issue. Please be assured that we will do our utmost best to keep the downtime as short as possible. **Incident start**: 2026/09/30 18:407 CEST **Impact**: Rackswitches and servers in rack 2 are down.

3. resolved Sep 30, 2026, 05:40 PM UTC

   Due to a defective PSU in one of our servers the circuit breaker triggered and all power was lost in Rack 2\. PSU has been replaced, all machines have been powered up..

4. resolved Sep 30, 2026, 05:40 PM UTC

   Due to a defective PSU in one of our servers the circuit breaker triggered and all power was lost in Rack 2\. PSU has been replaced, all machines have been powered up.

Read the full incident report →

Started Apr 01, 2026, 08:39 AM UTC· resolved Apr 01, 2026, 12:45 PM UTC

1. investigating Apr 01, 2026, 08:39 AM UTC

   We are currently investigating this incident..

2. monitoring Apr 01, 2026, 10:07 AM UTC

   We implemented a fix and are currently monitoring the result..

3. resolved Apr 01, 2026, 12:45 PM UTC

   This incident has been resolved..

4. investigating Apr 02, 2026, 10:16 AM UTC

   We introduced monitoring nf\_conntrack\_count and nf\_conntrack\_max and alerting at tresholds. This will help us (pro-actively) identify and with faster resolution times in the future..

Read the full incident report →

Started Mar 31, 2026, 06:50 PM UTC· resolved Mar 31, 2026, 07:06 PM UTC

1. investigating Mar 31, 2026, 06:50 PM UTC

   We are encountering an issue with hv03.snel.com..

2. resolved Mar 31, 2026, 07:06 PM UTC

   At 20:50 CEST we received our first alert regarding a hypervisor being unreachable. Upon investigation we found that the nf\_conntrack table was full. We're still investigating what the reason for this is since we have a fairly high value for nf\_conntrack\_max, and nf\_conntrack\_count is nowhere near the value of nf\_conntrack\_max. We have increased (3x) nf\_conntrack\_max and rebooted the server. At 21:31 CEST the server was rebooted and all VM's were being started..

Read the full incident report →

Started Dec 16, 2025, 06:00 PM UTC· resolved Dec 16, 2025, 08:14 PM UTC

1. investigating Dec 16, 2025, 06:00 PM UTC

   We are currently investigating this incident..

2. resolved Dec 16, 2025, 08:14 PM UTC

   Due to a defective PSU in one of our servers the circuit breaker triggered and all power was lost in Rack 12\. PSU has been replaced, all machines have been powered up..

Read the full incident report →

Started Jul 04, 2025, 11:38 AM UTC· resolved Jul 04, 2025, 12:12 PM UTC

1. investigating Jul 04, 2025, 11:38 AM UTC

   We are encountering a power outage in rack 8 in SmartDC datacenter. This power outage might result in unavailability of your services. Our data center engineers are on-site to investigate the cause of this issue. Please be assured that we will do our utmost best to keep the downtime as short as possible. **Incident start**: 04/07/2025 13:48 CEST **Impact**: Rackswitches and servers in rack 8 are down.

2. resolved Jul 04, 2025, 12:12 PM UTC

   The breaker tripped, we have restored the breaker, we will continue monitoring the situation and will do a root cause analysis..

Read the full incident report →

Started Jun 03, 2025, 07:00 AM UTC· resolved Jun 03, 2025, 08:58 AM UTC

1. investigating Jun 03, 2025, 07:00 AM UTC

   We are encountering an issue with one of our hypervisors on our Pure Performance platform (purehv07)..

2. identified Jun 03, 2025, 07:24 AM UTC

   Our data center engineers are on-site to investigate the cause of this issue. Please be assured that we will do our utmost best to keep the downtime as short as possible. We are continuing to work on a fix for this incident..

3. monitoring Jun 03, 2025, 08:55 AM UTC

   We implemented a fix and are currently monitoring the result..

4. resolved Jun 03, 2025, 08:58 AM UTC

   This incident has been resolved..

Read the full incident report →

Started Mar 12, 2025, 04:39 PM UTC· resolved Mar 12, 2025, 05:05 PM UTC

1. investigating Mar 12, 2025, 04:39 PM UTC

   We're experiencing a major outage on our Cloud VPS platform. We are currently investigating this incident..

2. resolved Mar 12, 2025, 05:05 PM UTC

   1 of our storage controllers crashed. Due to a bug in the software failover did not work correctly. We have resolved the issue with the controller and we have updated the software on both controllers which should prevent this from happening again. .

Read the full incident report →