Incidents | NepalCloud Incidents reported on status page for NepalCloud https://status.nepalcloud.host/ en Singapore recovered https://status.nepalcloud.host/ Sat, 16 May 2026 11:10:15 +0000 https://status.nepalcloud.host/#efd4c10ca4dbe812cb3478c521f8590a6cfa5527772188a302afbeacf552a351 Singapore recovered Singapore went down https://status.nepalcloud.host/ Sat, 16 May 2026 11:08:09 +0000 https://status.nepalcloud.host/#efd4c10ca4dbe812cb3478c521f8590a6cfa5527772188a302afbeacf552a351 Singapore went down ClientArea recovered https://status.nepalcloud.host/ Wed, 13 May 2026 07:37:28 +0000 https://status.nepalcloud.host/#f0856d9572571f0001c0af730a0b440d0856e397954196ae03693d52cd0a4f82 ClientArea recovered ClientArea went down https://status.nepalcloud.host/ Wed, 13 May 2026 07:34:22 +0000 https://status.nepalcloud.host/#f0856d9572571f0001c0af730a0b440d0856e397954196ae03693d52cd0a4f82 ClientArea went down ClientArea recovered https://status.nepalcloud.host/ Wed, 13 May 2026 07:25:37 +0000 https://status.nepalcloud.host/#f22e25ea99f27799c51d3a4cc1750c26433864d883aa8946751f2db10e0c9490 ClientArea recovered ClientArea went down https://status.nepalcloud.host/ Wed, 13 May 2026 07:22:23 +0000 https://status.nepalcloud.host/#f22e25ea99f27799c51d3a4cc1750c26433864d883aa8946751f2db10e0c9490 ClientArea went down DirectAdmin (node3) recovered https://status.nepalcloud.host/ Thu, 30 Apr 2026 08:03:43 +0000 https://status.nepalcloud.host/#4d9168b430f78f588bae1d152e075656b5cddd9523035f580c1317ca011fab3f DirectAdmin (node3) recovered DirectAdmin (node3) went down https://status.nepalcloud.host/ Thu, 30 Apr 2026 08:01:20 +0000 https://status.nepalcloud.host/#4d9168b430f78f588bae1d152e075656b5cddd9523035f580c1317ca011fab3f DirectAdmin (node3) went down Shared Hosting (mars) recovered https://status.nepalcloud.host/ Sat, 18 Apr 2026 18:28:37 +0000 https://status.nepalcloud.host/#24422e1ff2fced60410df889e906b40165ebaac10a3b382a8d8f66aa7c3308e3 Shared Hosting (mars) recovered Shared Hosting (mars) went down https://status.nepalcloud.host/ Sat, 18 Apr 2026 18:26:40 +0000 https://status.nepalcloud.host/#24422e1ff2fced60410df889e906b40165ebaac10a3b382a8d8f66aa7c3308e3 Shared Hosting (mars) went down node4 recovered https://status.nepalcloud.host/ Fri, 17 Apr 2026 02:02:48 +0000 https://status.nepalcloud.host/#cdf5dc72929f7b5ede9a7749d6a79e9993035cb6e4d3586bf495a7f178d44ecd node4 recovered node4 went down https://status.nepalcloud.host/ Fri, 17 Apr 2026 01:59:45 +0000 https://status.nepalcloud.host/#cdf5dc72929f7b5ede9a7749d6a79e9993035cb6e4d3586bf495a7f178d44ecd node4 went down DirectAdmin (node3) recovered https://status.nepalcloud.host/ Wed, 08 Apr 2026 19:51:32 +0000 https://status.nepalcloud.host/#5cd79d42734bc4efba738855ae325f1929da8789f27349c33568191a76de5d34 DirectAdmin (node3) recovered DirectAdmin (node3) went down https://status.nepalcloud.host/ Wed, 08 Apr 2026 19:43:24 +0000 https://status.nepalcloud.host/#5cd79d42734bc4efba738855ae325f1929da8789f27349c33568191a76de5d34 DirectAdmin (node3) went down San Francisco, USA recovered https://status.nepalcloud.host/ Wed, 08 Apr 2026 11:34:20 +0000 https://status.nepalcloud.host/#8e3576eb5832df6569f3877b2faacc4eadc266fc8aafea6c16b19a27807c91ce San Francisco, USA recovered San Francisco, USA went down https://status.nepalcloud.host/ Wed, 08 Apr 2026 11:32:20 +0000 https://status.nepalcloud.host/#8e3576eb5832df6569f3877b2faacc4eadc266fc8aafea6c16b19a27807c91ce San Francisco, USA went down DirectAdmin (node3) recovered https://status.nepalcloud.host/ Fri, 20 Mar 2026 07:06:29 +0000 https://status.nepalcloud.host/#8b8b1c959815de31d6aadc8c59a73be408e9ab0b88ac76eb94d1c6b1ac14f39b DirectAdmin (node3) recovered DirectAdmin (node3) went down https://status.nepalcloud.host/ Fri, 20 Mar 2026 07:04:35 +0000 https://status.nepalcloud.host/#8b8b1c959815de31d6aadc8c59a73be408e9ab0b88ac76eb94d1c6b1ac14f39b DirectAdmin (node3) went down Shared Hosting (mars) Unavailable https://status.nepalcloud.host/incident/847686 Thu, 12 Mar 2026 11:42:00 -0000 https://status.nepalcloud.host/incident/847686#1e7a608815f984182eca9fbf084f7f7dc39d7e052a8f8c536739189e1fcdb265 The IP was temporarily locked by the datacenter due to spam emails detected originating from the shared hosting server. We have contacted and discussed the issue with the datacenter and worked with them to resolve the block. As a preventive step, we are strengthening our email monitoring on the server and planning to implement an outbound email relay to better control and prevent similar issues in the future.