Krystal Outage History

Started Oct 21, 2026, 09:09 PM UTC· resolved Oct 23, 2026, 12:23 PM UTC

1. investigating Oct 21, 2026, 09:09 PM UTC

   We're aware of several security vulnerabilities announced today by Node.js, affecting the 22.x, 24.x and 26.x release lines. We're reviewing the impact on our services and will apply the patched versions across our servers as soon as our vendors release them. We'll update this notice as more information becomes available.

2. investigating Oct 21, 2026, 10:12 PM UTC

   Several mitigation options have been identified whilst we await patched versions from our upstream partners. These are presently being rolled out by our team. We do not detect any signs of exploitation at the time of writing. We will continue to monitor and ensure that your accounts remain secure. Your patience and cooperation are greatly appreciated.

3. investigating Oct 21, 2026, 11:24 PM UTC

   A mitigation is currently being implemented for the Brotli RCE (CVE-2026-111497). Other mitigation options are being investigated for the other CVEs, and we are awaiting publication of patched packages by upstream.

4. investigating Oct 22, 2026, 02:21 AM UTC

   The Brotli RCE (CVE-2026-111497) has been mitigated fleet-wide, and on all customer servers that are managed by our team. We will continue to work on the remaining CVEs, applying mitigations where available and awaiting fixed versions from upstream. Thank you for your patience and cooperation.

5. investigating Oct 22, 2026, 03:02 PM UTC

   Our mitigation against the Brotli-related Node.js vulnerability remains deployed across our hosting fleet and all customer servers managed by our team. We are working closely with our upstream partners, who have confirmed that patched Node.js packages are now being made available through their release channels. Our team are now working diligently to roll these updates out across our fleet. We will keep you updated.

6. identified Oct 22, 2026, 04:10 PM UTC

   We are continuing to install the available Node.js security updates on our hosting servers. Node.js will be restarted on all servers once this is complete to ensure that the new binaries are being used. Please note that patched versions of alt-nodejs v16, v18 and v20, and ea-nodejs22 are still pending from upstream. We shall continue to work with our partners to ensure that updates to these remaining versions are applied immediately once they become available. Our mitigation against Brotli-compressed requests remains in place across our hosting fleet and managed customer servers. Our upstream provider has confirmed that this reduces exposure. Our Software team are also working hard to ensure that internal applications are patched and hardened against these vulnerabilities - keeping your accounts and our systems secure is of utmost importance to us. We will continue to update you throughout the process.

7. identified Oct 22, 2026, 04:50 PM UTC

   We have completed the rollout of the available Node.js 12, 14, 22, 24 and 26 security updates across our shared hosting fleet and restarted applications using the old versions where they can restart automatically. Our customer account gateway has also been patched in production. We are now focusing on completing updates and restarts on managed customer servers. Some vendor fixes remain outstanding, so this work is not yet complete. The mitigation against Brotli-compressed requests remains in place across our hosting fleet and managed servers.

8. identified Oct 22, 2026, 06:19 PM UTC

   Security updates for the previously outstanding Node.js 16, 18 and 20 packages, and the cPanel-provided Node.js 22 package, are now available from our upstream providers. We have begun rolling these updates out across our shared hosting fleet. We are also continuing checks across managed customer servers to establish the updates and application restarts required on each server before applying the patches. This work is still in progress.

9. identified Oct 22, 2026, 08:16 PM UTC

   We have completed the rollout of all currently available alt-nodejs security updates across our shared hosting fleet. All Node.js applications on the fleet, including customer-managed processes, have now been restarted to use the updated binaries. Our final checks found no processes still using the replaced versions. The additional protection against Brotli-compressed requests remains in place across our hosting fleet and managed customer servers. Work on managed customer servers is in progress, and we are continuing to track the remaining vendor fixes. This incident remains open while that work is completed.

10. identified Oct 22, 2026, 09:07 PM UTC

    We have now applied the available Node.js security updates to managed customer servers and restarted applications using the replaced binaries. The latest audit found no outstanding package updates or processes using replaced binaries. This follows completion of the shared hosting rollout. This does not yet address every affected Node.js installation. Some older, end-of-life versions and other vendor-provided packages still have no fixes available, and customer-installed copies require separate review. Customers using their own Node.js installations should check for security updates and move unsupported versions to a patched, supported release. Our additional protection against Brotli-compressed requests remains in place, but is not a complete substitute for patched software. This incident remains open whilst we continue to monitor and await further releases from upstream.

11. monitoring Oct 23, 2026, 11:13 AM UTC

    We have completed final checks and confirmed that the available security updates for Node.js 10, 12, 14, 16, 18, 19, 20, 22, 24 and 26 have been applied across our shared hosting fleet and Managed VPS servers. We are now monitoring following the rollout. Our additional protection against Brotli-compressed requests remains in place to reduce exposure. Customers using their own Node.js installations should check for security updates and migrate unsupported versions to a patched, supported release.

12. resolved Oct 23, 2026, 12:23 PM UTC

    We have completed the rollout and final checks of all available Node.js security updates across our shared hosting fleet and Managed VPS servers. Applications using replaced binaries have been restarted, and we are closing this incident. Thank you for your patience while we completed this work.

Read the full incident report →

Started Oct 21, 2026, 08:42 AM UTC· resolved Oct 23, 2026, 12:24 PM UTC

1. investigating Oct 21, 2026, 08:42 AM UTC

   We're aware of two critical PHP security vulnerabilities announced by the PHP Security Team. Full technical details and the list of affected versions have not yet been published. Our PHP builds come from our vendors. We'll apply their patched versions across our shared hosting and Managed WordPress servers as soon as they're released. In the meantime, we're putting additional protections in place on our servers to reduce the risk until the updates are rolled out. Customers don't need to take any action. Sites will move to the patched PHP versions automatically once the updates are deployed. We'll update this notice as more information becomes available.

2. investigating Oct 21, 2026, 10:03 AM UTC

   Mitigations have been deployed fleet-wide and to customer servers that are managed by our team. We are continuing to monitor the situation closely, and are working with our upstream partners to ensure that patches are implemented as soon as they become available. We shall keep you updated throughout the process.

3. investigating Oct 21, 2026, 01:29 PM UTC

   We are continuing to monitor the situation, and are working diligently to ensure that all systems have mitigations in place in advance of applying patches released by upstream. We will share further updates in due course as and when more information is available. Thank you for your ongoing cooperation.

4. identified Oct 21, 2026, 03:08 PM UTC

   Upstream has now started releasing new versions that patch these vulnerabilities, and our team are working to get them applied to all servers and systems as soon as possible. We appreciate your ongoing cooperation and understanding, and will keep you updated.

5. identified Oct 21, 2026, 04:56 PM UTC

   Our team are continuing to roll out mitigations as quickly as possible, and we are deploying patched versions as and when they are released by upstream. Your ongoing patience and cooperation is greatly appreciated.

6. identified Oct 21, 2026, 06:33 PM UTC

   We're currently performing emergency maintenance across our fleet to make sure your sites are protected against two critical PHP vulnerabilities, CVE-2026-109618 and CVE-2026-109619. Keeping your account secure is of the utmost importance to us, so we're updating PHP on every server as fixes become available. As part of this work, we're retiring PHP 4.4, 5.1 and 5.2 with immediate effect. These versions stopped receiving security fixes many years ago and cannot be protected against these issues. If your site uses PHP 4.4, 5.1 or 5.2, it may display errors or stop working. We will do everything we can to prevent this, but ensuring the security of our customers' sites takes priority. We will contact you if you are using one of the versions of PHP that are being retired. Thanks for your patience while we keep things safe.

7. identified Oct 21, 2026, 09:27 PM UTC

   Our upstream partners have now released patched PHP binaries for all supported PHP versions. Our team are working to apply this update across the fleet. We will provide an update once this is complete. Accounts utilising unsupported PHP versions are being moved on to the next possible supported version, to ensure that they also benefit from the mitigations. Once this is complete, unsupported versions will be disabled fleet-wide.

8. identified Oct 21, 2026, 10:10 PM UTC

   Information regarding package availability for patched PHP versions was miscommunication to us by upstream, and we are still awaiting their release. In the meantime, we have applied all available mitigations across the fleet, and continue to monitor. We will keep you updated. Thank you for your patience.

9. identified Oct 21, 2026, 11:08 PM UTC

   Our upstream partners have released patches for ea-php packages for supported PHP versions, and these are now applied across our shared server fleet. We are currently in the process of applying patches for alt-php packages and we are looking to roll these out as quickly as possible.

10. identified Oct 22, 2026, 12:45 AM UTC

    Upstream have made patched PHP packages available in their testing channel, and we are working on rolling this out fleet-wide. We will provide an update here once the new PHP versions have been rolled out. Thank you for your cooperation.

11. identified Oct 22, 2026, 02:00 AM UTC

    We are continuing to deploy alt-php updates fleet-wide. ea-php is already patched. We will provide an update once the rollout is complete. Work is starting on applying the same updates to customer servers that are managed by us.

12. identified Oct 22, 2026, 05:38 AM UTC

    Our team has now completed PHP updates across our entire fleet of shared, premium and reseller servers. Patching of managed servers remains in progress, and we will update you once that is completed.

13. identified Oct 22, 2026, 06:58 AM UTC

    PHP versions across all fleet and managed servers have now been updated to versions that patch the announced CVEs. Managed WordPress (Onyx) is in progress, and we will update you in due course.

14. identified Oct 22, 2026, 08:16 AM UTC

    The security fixes have been backported into the existing PHP releases, so the version number shown in cPanel, phpinfo() or WordPress Site Health won't change. ** Patched servers will still report the same PHP version (5.2–8.5) as before, but are running the fixed build. ** ** There's no need to change your PHP version or contact us to confirm your site is protected. ** Patching on Onyx is still in progress, and we'll update this notice once it's complete.

15. identified Oct 22, 2026, 12:53 PM UTC

    cPanel/WHM users - all services have now been patched - no further action is required. Important notes below: ** Patched servers will still report the same PHP version (5.2 – 8.5) as before, but are running the fixed build. ** ** There's no need to change your PHP version or contact us to confirm your site is protected. ** Onyx Users: We are still working through the patches on Onyx. We are working as quickly as possible and appreciate your continued patience. For those checking PHP versions, some will remain the same, others will update. See the expected version changes below: 7.4.33 → 7.4.33 8.0.30 → 8.0.30 8.1.30 → 8.1.34 8.2.24 → 8.2.35 8.3.12 → 8.3.36

16. monitoring Oct 22, 2026, 03:53 PM UTC

    PHP security update status: Complete All fleet servers have had PHP security updates applied, including cPanel/WHM (Web Hosting, Reseller Hosting and Business Hosting) & Managed VPS services. The patches were backported, so the PHP version number hasn’t changed. Onyx: all available PHP versions have been patched. See our earlier update for the version changes. No action is needed on your side - all available PHP versions are now secure. We’re still seeing a high volume of support queries, so replies may be delayed. We’re working through the backlog as quickly as we can.

17. monitoring Oct 22, 2026, 04:23 PM UTC

    PHP security patching is complete across Web Hosting, Reseller Hosting, Business Hosting, Managed VPS and Managed WordPress (Onyx). We are now monitoring following the rollout. No action is required from customers for these security updates. The phpMyAdmin database management tool on Onyx remains temporarily unavailable. Its PHP update is complete, but the tool will remain offline while we move it to a new hosting environment. We are tracking this separately from the PHP security rollout and do not yet have a confirmed restoration time. We appreciate your cooperation and patience over the psat 24 hours.

18. resolved Oct 23, 2026, 12:24 PM UTC

    PHP security patching is complete across Web Hosting, Reseller Hosting, Business Hosting, Managed VPS and Managed WordPress (Onyx), and we are concluding this security update notice. No action is required from customers for these security updates. Some security fixes were backported, so the PHP version displayed by your website may remain unchanged even though the fixes are installed. Onyx phpMyAdmin remains temporarily unavailable while we move it to a new hosting environment. Its PHP security update is complete; restoration is tracked separately in our phpMyAdmin maintenance notice "phpMyAdmin maintenance notice": https://krystalstatus.uk/incidents/dbharb8c. We do not yet have a confirmed restoration time. Thank you for your patience and cooperation throughout this rollout.

Read the full incident report →

Started Oct 20, 2026, 08:18 AM UTC· resolved Oct 21, 2026, 08:10 AM UTC

1. investigating Oct 20, 2026, 08:18 AM UTC

   An issue being experienced by our third-party payment provider is currently affecting payments for accounts and causing them to fail. We are awaiting a resolution and will update again as soon as we have further information.

2. monitoring Oct 20, 2026, 03:34 PM UTC

   We're now seeing payments complete and will continue to monitor closely.

3. resolved Oct 21, 2026, 08:10 AM UTC

   All systems with our payment provider are operational

Read the full incident report →

Started Oct 09, 2026, 05:13 PM UTC· resolved Oct 09, 2026, 07:23 PM UTC

1. investigating Oct 09, 2026, 05:13 PM UTC

   We are aware of the issues on p113 which have been intermittently failing health checks. We are currently investigating the problems as a matter of priority.

2. identified Oct 09, 2026, 06:14 PM UTC

   We have identified the issue and are actively resolving it.

3. monitoring Oct 09, 2026, 06:28 PM UTC

   We have detected a large number of connections to the server which was choking the network causing the intermittent issues. These are currently being mitigated and the server now seems stable. We apologise for any issues caused by this. We believe this should be resolved and will keep the mitigations in place while we continue to monitor.

4. resolved Oct 09, 2026, 07:23 PM UTC

   The problem has now been resolved.

Read the full incident report →

Started Oct 02, 2026, 06:37 AM UTC· resolved Oct 06, 2026, 11:22 AM UTC

1. investigating Oct 02, 2026, 06:37 AM UTC

   We're aware of, and are investigating an issue affecting access to the Codebase platform. We'll provide further updates shortly.

2. identified Oct 02, 2026, 07:08 AM UTC

   We're in the process of implementing a permanent fix for the issue, but the problem is recovering.

3. monitoring Oct 02, 2026, 08:32 AM UTC

   The main issues accessing the Codebase service this morning are now fully resolved, we will continue to monitor throughout the day for any further edge-cases that have arisen from last night's maintenance. Please accept our apologies for any inconvenience that this has caused.

4. monitoring Oct 02, 2026, 01:58 PM UTC

   We're happy that the bulk of the edge-case issues that surfaced since last night are now all resolved. We will continue to monitor closely over the coming days and will roll out any fixes as necessary, but we would like to thank you for your patience whilst we completed the work.

5. resolved Oct 06, 2026, 11:22 AM UTC

   We're happy following a few edge-case fixes over the last few days, that the service is all working well since the migration. If any customers to experience issues they can reach out to us via [email protected], and we would like to thank everyone for their patience during the changes.

Read the full incident report →

Started Sep 30, 2026, 07:23 AM UTC· resolved Sep 30, 2026, 08:56 AM UTC

1. investigating Sep 30, 2026, 07:23 AM UTC

   We're currently seeing performance issues on one of the Onyx Database nodes: onyx-nlc-db-5-6 We're investigating this a priority and will provide updates as this is progressed.

2. resolved Sep 30, 2026, 08:56 AM UTC

   The issue has now been considered resolve. We thank you for your patience while we dealt with this issue.

Read the full incident report →

Started Sep 29, 2026, 12:13 PM UTC· resolved Sep 29, 2026, 12:16 PM UTC

1. investigating Sep 29, 2026, 12:13 PM UTC

   We're aware that cPanel and WHM are giving an error when accessing this server. User sites are not impacted

2. resolved Sep 29, 2026, 12:16 PM UTC

   This has been resolved

Read the full incident report →

Started Sep 25, 2026, 10:57 AM UTC· resolved Sep 25, 2026, 11:15 AM UTC

1. investigating Sep 25, 2026, 10:57 AM UTC

   We're currently investigating an issue which is impacting our shared server uranium-lon2.cloudhosting.uk "uranium-lon2.cloudhosting.uk": http://uranium-lon2.cloudhosting.uk Once we have any further news, this status will be updated.

2. resolved Sep 25, 2026, 11:15 AM UTC

   The server is now back up and services are running. We apologize for any inconvenience and appreciate your patience.

Read the full incident report →

Started Sep 24, 2026, 10:25 AM UTC· resolved Sep 24, 2026, 10:53 AM UTC

1. investigating Sep 24, 2026, 10:25 AM UTC

   We're aware of a potential issue with database connections on our Managed WordPress platform. We're investigating and will update again as soon as we're able.

2. monitoring Sep 24, 2026, 10:43 AM UTC

   A connectivity issue has been identified and resolved. Sites should now be loading as normal and we will continue to monitor for any further issues.

3. resolved Sep 24, 2026, 10:53 AM UTC

   Database connectivity for Managed WordPress sites has now been restored.

Read the full incident report →

Started Sep 19, 2026, 10:21 PM UTC· resolved Sep 23, 2026, 10:48 AM UTC

1. investigating Sep 19, 2026, 10:21 PM UTC

   We're carrying out emergency maintenance on Identity, the service that handles login and authentication for Krystal.io: http://Krystal.io and services that sign in through it. While the work is underway you may be unable to log in, and existing sessions may be signed out. Hosted services, email, websites and phone calls are unaffected and continue to run normally.

2. monitoring Sep 20, 2026, 08:10 AM UTC

   Identity access has been restored. We will continue to monitor the situation.

3. resolved Sep 23, 2026, 10:48 AM UTC

   Service was restored and users can login again.

Read the full incident report →

Started Sep 13, 2026, 03:49 PM UTC· resolved Sep 13, 2026, 04:10 PM UTC

1. investigating Sep 13, 2026, 03:49 PM UTC

   We're currently attempting to mitigate a DDOS attack against the server baltar-lon.krystal.uk: http://baltar-lon.krystal.uk Litespeed is running with "captcha Mode" enabled which may impact some bots or APIs which call to sites over http/https While the server is currently up, you'll likely notice an impact on performance.

2. resolved Sep 13, 2026, 04:10 PM UTC

   The attack has been mitigated. The Litespeed captcha service is disabled which should bring services and API calls back to normal. Thank you for your patience.

Read the full incident report →

Started Sep 12, 2026, 10:04 AM UTC· resolved Sep 12, 2026, 10:20 AM UTC

1. investigating Sep 12, 2026, 10:04 AM UTC

   We're currently seeing a large DDOS attack against the server morgan.krystal.uk "morgan.krystal.uk": http://morgan.krystal.uk We're actively looking at blocking requests, but you may experience some performance issues.

2. resolved Sep 12, 2026, 10:20 AM UTC

   The attack has been mitigated and services are now functioning normally. Thank you for your patience while that was worked on.

Read the full incident report →

Started Sep 04, 2026, 09:12 AM UTC· resolved Sep 04, 2026, 09:26 AM UTC

1. investigating Sep 04, 2026, 09:12 AM UTC

   We're aware of an update issue on the SitePro server which is generating "This plugin required Upgrade" messages on websites. For clients using this service, we suggest you Do Not Publish changes while this issue is ongoing as this will set these messages on the elements of the live website. We're working with the product vendors to get this resolved.

2. resolved Sep 04, 2026, 09:26 AM UTC

   The issue has now been resolved. You are now ok to publish sites. If you have published your site during the issue, republishing will clear these warning messages. We apologise for any issues caused by this and thank you for your patience.

Read the full incident report →

Started Sep 03, 2026, 08:33 PM UTC· resolved Sep 03, 2026, 08:41 PM UTC

1. investigating Sep 03, 2026, 08:33 PM UTC

   Our hosting Client Area requires a critical and urgent update. The client area may be briefly unavailable while we apply the update. Invoicing, payments and support tickets will continue as normal once that is complete.

2. resolved Sep 03, 2026, 08:41 PM UTC

   The upgrade has completed.

Read the full incident report →

Started Aug 28, 2026, 12:57 PM UTC· resolved Aug 28, 2026, 02:45 PM UTC

1. monitoring Aug 28, 2026, 12:57 PM UTC

   We're aware of an situation that may be affecting some customers access their Codebase account domain due to a DNS issue. Whilst the issue has already been located and resolved, if anyone does experience issues over the coming hours, they can reset their DNS cache.

2. resolved Aug 28, 2026, 02:45 PM UTC

   No further issues have been reported and we're happy that this is now fully resolved.

Read the full incident report →

Started Aug 24, 2026, 11:02 AM UTC· resolved Aug 24, 2026, 05:49 PM UTC

1. investigating Aug 24, 2026, 11:02 AM UTC

   We are seeing increased connection times to the mariadb database server on platinum-lon1.cloudhosting.net and are investigating the root cause. This may result in slower page load times or database connection timeouts.

2. monitoring Aug 24, 2026, 11:12 AM UTC

   We have identified the problem queries causing the slow down and taken mitigation steps to prevent them causing further issues. We are continuing to monitor.

3. resolved Aug 24, 2026, 05:49 PM UTC

   Following extensive monitoring we're happy to report this is now resolved. Any issues, please contact our support team.

Read the full incident report →

Started Aug 24, 2026, 07:57 AM UTC· resolved Aug 24, 2026, 08:18 AM UTC

1. investigating Aug 24, 2026, 07:57 AM UTC

   We're currently investigating an issue which is impacting our shared server endor.krystal.uk: http://endor.krystal.uk Once we have any further news, this status will be updated.

2. monitoring Aug 24, 2026, 08:04 AM UTC

   Services have now been restored. We're continuing to check services and monitor though for issues.

3. resolved Aug 24, 2026, 08:18 AM UTC

   This has been stable so we're happy to mark this as resolved. Thank you for your patience.

Read the full incident report →

Started Aug 04, 2026, 01:05 PM UTC· resolved Aug 05, 2026, 11:11 AM UTC

1. investigating Aug 04, 2026, 01:05 PM UTC

   We're aware that some inbound email is being delivered later than expected. We're investigating the cause and will provide an update shortly.

2. monitoring Aug 04, 2026, 08:11 PM UTC

   Again we would like to apologise for the issues experienced here. We have now completed our investigation and we believe the cause of this particular issue was the result of 3 unrelated problems: 1. We experienced a significant amount of inbound spam into the Spam Experts platform, this resulted in mail being delayed and queued for quite some time whilst it handled this. 2. One of the filtering nodes was out of action due to a software fault. 3. Another node was experiencing performance issues which has been identified as a hardware fault. This resulted in the cluster not only having a significant "spam attack" but it was also running 2 nodes down which also impacted performance slightly. We now have the node with the software fault back in action and for the hardware fault, this has been logged with our hardware vendor to have the required replacement part sent over as soon as possible. This unfortunately was a case of multiple events occurring at the same time which resulted in the slower filtering performance and delays in mail receipt. We can confirm that the inbound attack has stopped and the filtering cluster is now operating correctly minus the one node which we are waiting on replacement hardware for. We have also provided feedback to SpamExperts on a way to improve the software performance under such heavy load, this should improve performance significantly if such a situation ever reoccurs. For now, we are going to leave this in a monitoring status until the hardware fault has been resolved. As before, we do apologise for any disruption this has caused.

3. resolved Aug 05, 2026, 11:11 AM UTC

   The affected node is back in the filtering cluster. All nodes are online and inbound mail is being filtered and delivered at normal speed, with no backlog in the queues. We've been monitoring since the fix went in and everything has stayed stable, so we're marking this as resolved. Thanks for bearing with us, and apologies again for the delays to inbound email while this was ongoing.

Read the full incident report →

Started Jul 28, 2026, 12:24 PM UTC· resolved Jul 28, 2026, 01:20 PM UTC

1. investigating Jul 28, 2026, 12:24 PM UTC

   We are aware of a higher than normal load across our shared servers at the moment which may be leading to slower connectivity times when accessing websites. Our team is currently investigating.

2. resolved Jul 28, 2026, 12:42 PM UTC

   This has now been resolved. A firewall change rollout triggered a mass reload which inadvertently caused high load across multiple servers. We've updated our processes to avoid the issue reoccurring. We apologise for any inconvenience caused.

3. monitoring Jul 28, 2026, 01:09 PM UTC

   This issue has since been resolved, but there is a delay due to some servers having been rebooted and the applied fix to load levels on all servers returning to normal. We are working on this, and everything should be fully working as expected shortly.

4. resolved Jul 28, 2026, 01:20 PM UTC

   All services are fully restored and operating normally

Read the full incident report →

Started Jul 27, 2026, 09:34 PM UTC· resolved Jul 28, 2026, 06:24 AM UTC

1. monitoring Jul 27, 2026, 09:34 PM UTC

   Some users connecting via Virgin Media may experience difficulty accessing our services. This issue is originating from Virgin Media's network, not our infrastructure. We are monitoring the incident.

2. resolved Jul 28, 2026, 06:24 AM UTC

   No more drops overnight. This seems to be resolved.

Read the full incident report →

Started Jul 22, 2026, 08:34 AM UTC· resolved Jul 22, 2026, 10:00 AM UTC

1. investigating Jul 22, 2026, 08:34 AM UTC

   We're currently seeing a large DDOS attack against the server cuttlefish-lon.krystal.u: http://cuttlefish-lon.krystal.ukk We're actively looking at blocking requests, but you may experience some performance issues.

2. resolved Jul 22, 2026, 10:00 AM UTC

   The attack has been mitigated and services are now functioning normally. Thank you for your patience while that was worked on.

Read the full incident report →

Started Jul 20, 2026, 09:21 AM UTC· resolved Jul 20, 2026, 09:35 AM UTC

1. investigating Jul 20, 2026, 09:21 AM UTC

   We are aware of an incident causing slower than usual loading times or connection timeouts on websites hosted on our reseller servers (i.e. cloudhosting.net / cloudhosting.uk servers). We are currently investigating.

2. resolved Jul 20, 2026, 09:35 AM UTC

   We were experiencing routing issues affecting some of our servers. This has now been resolved and we apologise for any disruption caused.

Read the full incident report →

Started Jul 10, 2026, 10:46 AM UTC· resolved Jul 20, 2026, 09:29 AM UTC

1. identified Jul 10, 2026, 10:46 AM UTC

   We're investigating an ongoing attack against the Premium server lobster-lon.krystal.uk: http://lobster-lon.krystal.uk While this server is up, the high load on this may cause some instability or performance issues.

2. monitoring Jul 10, 2026, 11:01 AM UTC

   We've mitigating the attack and services are now more stable. We're still monitoring this though for any further issues or spikes.

3. resolved Jul 20, 2026, 09:29 AM UTC

   This was since resolved

Read the full incident report →

Started Jul 08, 2026, 10:17 PM UTC· resolved Jul 10, 2026, 02:59 PM UTC

1. investigating Jul 08, 2026, 10:17 PM UTC

   We are aware of an issue with cPanel's licensing service that is currently affecting multiple servers. We are awaiting an update from cPanel and hope they will have it resolved shortly. This will not affect websites loading but might cause some some logins to WHM or cPanel to be unavailable.

2. monitoring Jul 08, 2026, 10:47 PM UTC

   The issue with cPanel's licensing service is now resolved. You should now be able to log in to WHM and cPanel and any mail issues should also be resolved.

3. resolved Jul 10, 2026, 02:59 PM UTC

   This is now fully resolved.

Read the full incident report →

Started Jul 07, 2026, 08:16 AM UTC· resolved Jul 07, 2026, 10:02 AM UTC

1. investigating Jul 07, 2026, 08:16 AM UTC

   We're currently working on an issue with the reseller server haltia-lon.cloudhosting.uk: http://haltia-lon.cloudhosting.uk We're seeing high load and CPU activity but so far have been unable to determine the exact cause. Services are currently running but slow to respond which may cause timeouts. We'll provide further details as the issue is progressed.

2. monitoring Jul 07, 2026, 08:46 AM UTC

   The server is now stable. Load averages are within expected limits and services are now responding normally. We're still monitoring this though for any further spikes which might lead to further issues.

3. resolved Jul 07, 2026, 10:02 AM UTC

   This has since been resolved

Read the full incident report →