Snel.com Outage History
Snel.com is up right nowSnel.com had 9 outages in the last 2 years — averaging 0.4 incidents per month.
There were 9 Snel.com outages since August 12, 2024. Each is summarised below — incident details, duration, and resolution information.
Major outage SmartDC network
Timeline · 1 update
- resolved Apr 01, 2026, 08:39 AM UTC
Type: Incident Duration: 4 hours and 6 minutes Affected Components: Snel.com authoritative nameservers, Outgoing mail relay, Cloud VPS platform, Snel.com network infrastructure, Pure Performance VPS platform Apr 1, 12:45:36 GMT+0 - Resolved - This incident has been resolved. Apr 2, 10:16:34 GMT+0 - Postmortem - 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. Apr 1, 08:39:46 GMT+0 - Investigating - We are currently investigating this incident. Apr 1, 10:07:36 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result.
Partial outage on Cloud VPS platform
Timeline · 1 update
- resolved Mar 31, 2026, 06:50 PM UTC
Type: Incident Duration: 16 minutes Affected Components: Cloud VPS platform Mar 31, 19:06:19 GMT+0 - Resolved - 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. Mar 31, 18:50:00 GMT+0 - Investigating - We are encountering an issue with hv03.snel.com.
Power outage in Rack 12
Timeline · 1 update
- resolved Dec 16, 2025, 06:00 PM UTC
Type: Incident Duration: 2 hours and 14 minutes Affected Components: SmartDC power network, My.snel.com - client area, Cloud VPS platform, Pure Performance VPS platform Dec 16, 18:00:00 GMT+0 - Investigating - We are currently investigating this incident. Dec 16, 20:14:00 GMT+0 - Resolved - 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.
Power outage in Rack 8
Timeline · 1 update
- resolved Jul 04, 2025, 11:38 AM UTC
Type: Incident Duration: 34 minutes Affected Components: SmartDC power network Jul 4, 11:38:00 GMT+0 - Investigating - 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 Jul 4, 12:12:00 GMT+0 - Resolved - The breaker tripped, we have restored the breaker, we will continue monitoring the situation and will do a root cause analysis.
Partial outage on Pure Performance platform
Timeline · 1 update
- resolved Jun 03, 2025, 07:00 AM UTC
Type: Incident Duration: 1 hour and 58 minutes Affected Components: Pure Performance VPS platform Jun 3, 07:24:00 GMT+0 - Identified - 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. Jun 3, 07:00:00 GMT+0 - Investigating - We are encountering an issue with one of our hypervisors on our Pure Performance platform (purehv07). Jun 3, 08:55:12 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Jun 3, 08:58:12 GMT+0 - Resolved - This incident has been resolved.
Outage Cloud VPS platform
Timeline · 1 update
- resolved Mar 12, 2025, 04:39 PM UTC
Type: Incident Duration: 26 minutes Affected Components: Cloud VPS platform Mar 12, 16:39:00 GMT+0 - Investigating - We're experiencing a major outage on our Cloud VPS platform. We are currently investigating this incident. Mar 12, 17:05:00 GMT+0 - Resolved - 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.
Packet loss
Timeline · 1 update
- resolved Oct 11, 2024, 03:36 PM UTC
Type: Incident Duration: 21 hours Affected Components: Snel.com network infrastructure Oct 11, 15:57:00 GMT+0 - Resolved - On friday 11th of October 2024 we experienced packet loss in our network in SmartDC. **Incident start (CET/CEST):** 11th October 2024 17:36 CEST **Incident end (CET/CEST):** 11th October 2024 17:57 CEST Currently the situation is stable. This incident is being monitored as the investigation is still ongoing. If you still experience issues or need more information about this incident please contact us at [email protected]. Oct 11, 15:36:00 GMT+0 - Investigating - We're experiencing packet-loss in our network, currently our engineers are investigating this incident.
Power outage in Rack 1
Timeline · 1 update
- resolved Aug 12, 2024, 01:03 AM UTC
Type: Incident Duration: 1 hour and 34 minutes Affected Components: SmartDC power network, Snel.com network infrastructure Aug 12, 01:03:00 GMT+0 - Investigating - We are encountering a power outage in rack 1 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**: 12/08/2024 04:03 CEST **Impact**: Rackswitches and servers in rack 1 are down Aug 12, 02:37:00 GMT+0 - Resolved - **Root cause**: a defective PSU in one of the servers resulted in the circuit breaker to cut the power. We have disconnected this PSU permanently. We have disconnected all other devices from the power network and reset the tripped breaker at 05:30\. After this time we started connecting all devices again. At 05:37 the last of the monitored devices was online again.