Kualo Outage History

Kualo is up right now

Kualo had 11 outages in the last 2 years totaling 41h 36m of downtime — averaging 0.5 incidents per month.

There were 11 Kualo outages since October 17, 2025 totaling 41h 36m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.kualo.com

Minor October 3, 2026

Partial CloudVPS Service Outage

Detected by Pingoru
Oct 03, 2026, 03:41 AM UTC
Resolved
Oct 03, 2026, 05:22 AM UTC
Duration
1h 40m
Affected: UK Cloud (London, UK)
Timeline · 2 updates
  1. identified Oct 03, 2026, 03:41 AM UTC

    Dear Clients, Approximately 50 minutes ago, we experienced a sudden and unexpected hardware failure within our London cloud environment. This has resulted in a partial outage, which is affecting a limited number of clients. Our engineering team is working to assess and resolve this at present, and we will have further updates to provide shortly. We sincerely appreciate your patience, and please accept our apologies for the inconvenience that this causes. Kind regards, Kualo Support

  2. resolved Oct 03, 2026, 05:22 AM UTC

    Dear Clients, We’re pleased to let you know that this issue is now fully resolved. Affected CloudVPS servers were migrated to alternative capacity within our cloud environment by our engineers, and we have been monitoring closely over the last hour. All servers are now operating normally. We apologise for any inconvenience caused by this outage. If you have any questions or concerns, please just let us know by raising a ticket via our helpdesk at https://my.kualo.com . Kind regards, Kualo Support

Read the full incident report →

Minor September 8, 2026

Service Outage

Detected by Pingoru
Sep 08, 2026, 10:31 AM UTC
Resolved
Sep 08, 2026, 02:32 PM UTC
Duration
4h 1m
Affected: Brutus
Timeline · 5 updates
  1. investigating Sep 08, 2026, 10:31 AM UTC

    We are currently experiencing a server wide outage on the Brutus server. We are working to resolve this as a priority and will keep you informed at all times. Our apologies for the inconvenience that this is causing

  2. identified Sep 08, 2026, 12:08 PM UTC

    The server is not responding to remote restart attempts and our investigations have identified a sudden hardware fault. On site engineers have found the server to be in a non-bootable state. Initial investigations indicate a power related hardware fault impacting the server itself. We are continuing to diagnose it and are assessing remedial options, including restoring services to alternative hardware. We do not have a restoration time yet, and faults of this nature can take some time to resolve. We will provide an update as soon as we have more information, and again once services are back online. We are sorry for the disruption that this is causing.

  3. identified Sep 08, 2026, 01:47 PM UTC

    Replacement hardware has been provisioned and engineers are now moving the drives across from the failed server in order to restore services. We expect to have further news shortly and will update this page once the migration is complete and services are back online.

  4. monitoring Sep 08, 2026, 02:19 PM UTC

    We have addressed the underlying service issues, and beleive this to be resolved, though we are continuing to monitor this closely.

  5. resolved Sep 08, 2026, 02:32 PM UTC

    The drive migration is complete and services have been restored. Sites and email hosted on Brutus are now back online. We will continue to monitor the replacement hardware closely. If you are still experiencing any issues with your services, please contact our support team. We apologise again for the disruption that this outage has caused.

Read the full incident report →

Minor September 8, 2026

Email Issues

Detected by Pingoru
Sep 08, 2026, 10:31 AM UTC
Resolved
Sep 08, 2026, 02:35 PM UTC
Duration
4h 4m
Affected: Brutus
Timeline · 3 updates
  1. investigating Sep 08, 2026, 10:31 AM UTC

    We are currently experiencing an issue with POP email on the Brutus server. We are working to resolve this as a priority and will keep you informed at all times. Our apologies for the inconvenience that this is causing

  2. monitoring Sep 08, 2026, 02:19 PM UTC

    We have addressed the underlying service issues, and beleive this to be resolved, though we are continuing to monitor this closely.

  3. resolved Sep 08, 2026, 02:35 PM UTC

    This issue is now fully resolved, though we are continuing to monitor this closely. Our sincere apologies for the inconvenience this has caused.

Read the full incident report →

Minor September 8, 2026

MySQL Outage

Detected by Pingoru
Sep 08, 2026, 10:31 AM UTC
Resolved
Sep 08, 2026, 02:47 PM UTC
Duration
4h 16m
Affected: Brutus
Timeline · 3 updates
  1. investigating Sep 08, 2026, 10:31 AM UTC

    We are currently experiencing an issue with MySQL on the Brutus server. We are working to resolve this as a priority and will keep you informed at all times. Our apologies for the inconvenience that this is causing

  2. monitoring Sep 08, 2026, 02:27 PM UTC

    We have addressed the underlying service issues, and beleive this to be resolved, though we are continuing to monitor this closely.

  3. resolved Sep 08, 2026, 02:47 PM UTC

    This issue is now fully resolved, though we are continuing to monitor this closely. Our sincere apologies for the inconvenience this has caused.

Read the full incident report →

Minor August 19, 2026

PHP Processing Issue

Detected by Pingoru
Aug 19, 2026, 07:23 PM UTC
Resolved
Aug 19, 2026, 07:44 PM UTC
Duration
21m
Affected: Viola
Timeline · 3 updates
  1. investigating Aug 19, 2026, 07:23 PM UTC

    We are currently experiencing an issue with the PHP Processing on the Viola server. We are working to resolve this as a priority and will keep you informed at all times. Our apologies for the inconvenience that this is causing

  2. monitoring Aug 19, 2026, 07:23 PM UTC

    We have addressed the underlying service issues, and beleive this to be resolved, though we are continuing to monitor this closely.

  3. resolved Aug 19, 2026, 07:44 PM UTC

    This issue is now fully resolved, though we are continuing to monitor this closely. Our sincere apologies for the inconvenience this has caused.

Read the full incident report →

Minor August 19, 2026

SSH Access Issue

Detected by Pingoru
Aug 19, 2026, 04:38 AM UTC
Resolved
Aug 19, 2026, 04:56 AM UTC
Duration
18m
Affected: Capulet
Timeline · 3 updates
  1. investigating Aug 19, 2026, 04:38 AM UTC

    We are currently experiencing an issue with SSH access on the Capulet server. We are working to resolve this as a priority and will keep you informed at all times. Our apologies for the inconvenience that this is causing

  2. monitoring Aug 19, 2026, 04:40 AM UTC

    We have addressed the underlying service issues, and beleive this to be resolved, though we are continuing to monitor this closely.

  3. resolved Aug 19, 2026, 04:56 AM UTC

    This issue is now fully resolved, though we are continuing to monitor this closely. Our sincere apologies for the inconvenience this has caused.

Read the full incident report →

Minor July 8, 2026

cPanel Licensing Error

Detected by Pingoru
Jul 08, 2026, 10:15 PM UTC
Resolved
Jul 08, 2026, 10:50 PM UTC
Duration
34m
Affected: cPanel / Web Host Manager
Timeline · 2 updates
  1. identified Jul 08, 2026, 10:15 PM UTC

    We are currently experiencing a network-wide cPanel/WHM licensing error affecting all servers. While web and email services remain fully operational, control panel logins may be temporarily unavailable. Our engineering team is actively coordinating with cPanel, awaiting a fix.

  2. resolved Jul 08, 2026, 10:50 PM UTC

    cPanel has successfully resolved their licensing server issues, restoring cPanel functionality. Our engineers, have confirmed all servers on our network have restored cPanel services, and consider this case resolved. Should you be experiencing any lingering issues, please open a support ticket.

Read the full incident report →

Minor June 23, 2026

Server Wide Issue

Detected by Pingoru
Jun 23, 2026, 10:55 AM UTC
Resolved
Jun 23, 2026, 07:46 PM UTC
Duration
8h 51m
Affected: Othello
Timeline · 5 updates
  1. identified Jun 23, 2026, 10:55 AM UTC

    This server is currently unavailable due to a physical infrastructure issue at our London data centre. Our engineers are investigating as a top priority and are working to identify and resolve the cause. We don’t yet have an estimated time for restoration. Given the nature of the issue, we want to be upfront that this may be an extended incident. Restoring service safely is our focus. We’re sorry for the disruption and appreciate your patience, we will keep you updated as work progresses.

  2. identified Jun 23, 2026, 12:40 PM UTC

    A further update on this server. We are continuing to work through all recovery options to restore service, but as this is an issue at the hardware level, it is taking some time. For context, we have experienced multiple near-concurrent hardware failures affecting different servers. Some have been recovered, while others have not yet, and each is behaving differently, so we are working through them individually to find the right recovery path. Alongside this, we are working with our data centre to understand the underlying cause. This server remains a priority and our engineers are actively working to restore it.

  3. identified Jun 23, 2026, 03:53 PM UTC

    A positive update on this server. It is now responding and has booted. Our engineers are working through some final networking and verification steps to bring it fully back into normal service, which we are hopeful will be completed shortly. We will confirm here as soon as the server is fully restored and verified. Thank you for your continued patience throughout this extended incident.

  4. monitoring Jun 23, 2026, 05:49 PM UTC

    This server is now back online, and we have verified it is fully operational and reachable. We’re sorry this was such a long incident. It stemmed from a complex hardware issue at our data centre with a number of moving parts, and our engineers have been working on it intensively throughout to bring the service back online safely. We will share a fuller update in due course. In the meantime, if you notice anything that doesn’t look right, please let us know and we will investigate. Thank you for your patience.

  5. resolved Jun 23, 2026, 07:46 PM UTC

    This issue is now fully resolved, though we are continuing to monitor this closely. Our sincere apologies for the inconvenience this has caused.

Read the full incident report →

Minor June 23, 2026

Web Service Issue

Detected by Pingoru
Jun 23, 2026, 10:22 AM UTC
Resolved
Jun 23, 2026, 12:16 PM UTC
Duration
1h 53m
Affected: UK Cloud (London, UK)
Timeline · 2 updates
  1. investigating Jun 23, 2026, 10:22 AM UTC

    We have identified an issue with the web service on UK Cloud (London, UK). We are currently investigating.

  2. resolved Jun 23, 2026, 12:16 PM UTC

    We have resolved the web service issue affecting UK Cloud (London, UK). We apologise for the inconvenience this caused you.

Read the full incident report →

Minor June 1, 2026

Network Incident Notice

Detected by Pingoru
Jun 01, 2026, 03:38 AM UTC
Resolved
Jun 01, 2026, 03:55 PM UTC
Duration
12h 17m
Affected: UK Network (London, UK)Mercutio
Timeline · 5 updates
  1. identified Jun 01, 2026, 03:38 AM UTC

    We are currently experiencing a large-scale DDoS (Distributed Denial of Service) attack targeting one of our servers. Our DDoS mitigation platform has automatically detected the attack and traffic is currently being routed through our scrubbing infrastructure to filter malicious traffic and maintain service availability. While mitigation is active, some services hosted on the affected server may experience intermittent connectivity issues, increased latency, or brief disruptions as traffic is analyzed and scrubbed. Our engineering team is actively monitoring the situation and working to ensure continued service stability. We will provide further updates as the situation develops. Thank you for your patience and understanding.

  2. monitoring Jun 01, 2026, 05:14 AM UTC

    Dear Clients, Our engineering team has been working to further mitigate this attack. At this time, although ongoing, we believe that we have been successful in mitigating its effects, and legitimate traffic appears to be flowing normally. Kind regards, Kualo Support

  3. monitoring Jun 01, 2026, 07:24 AM UTC

    Dear Clients, Our engineering team continues to actively mitigate this ongoing DDoS attack. Mitigation measures remain in place, and legitimate traffic appears to be flowing normally at this time. We will continue to monitor the situation and provide further updates as necessary. Kind regards, Kualo Support

  4. monitoring Jun 01, 2026, 08:50 AM UTC

    Dear Clients, The DDoS attack has now subsided, and services are operating normally. While no further attack activity has been observed for some time, our engineering team continues to closely monitor traffic to ensure ongoing service stability. Thank you for your patience and understanding. Kind regards, Kualo Support

  5. resolved Jun 01, 2026, 03:55 PM UTC

    Dear Clients, At this time, we have seen no further issues, and the inbound attack that we were experiencing has subsided. Accordingly, we’ll close out this issue. If you require any additional support, please reach out to our team via https://my.kualo.com/ . Kind regards, Kualo Support

Read the full incident report →