Cloudways

Affected: Cloudways Home

1. identified 2026-10-21 16:26 UTC

   Affected service: Cloudways Website and Affiliate Portal Update: Our team is still actively working on applying the PHP security patches, and the Cloudways website and affiliate portal is currently unavailable as a result. The work is taking slightly longer than initially...

Excerpts are shortened. Read the full incident on Cloudways's status page.

Affected: Cloudways Cloud Platform Console, Cloudways Cloud Platform Service

1. identified 2026-10-21 09:16 UTC

   Cloudways Security is closely monitoring the situation and implementing interim mitigations (that may cause a short service disruption) to strengthen the security of affected PHP environments while awaiting the release of official patches from the PHP Group. The PHP Group has...

2. identified 2026-10-21 16:43 UTC

   Today, the PHP Group disclosed critical Remote Code Execution (RCE) vulnerabilities affecting PHP. Because PHP powers a significant share of the web, including WordPress, Drupal, Laravel, and custom applications, we notified all customers this morning. To follow up on our...

Excerpts are shortened. Read the full incident on Cloudways's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-10-20 07:29 UTC

   Some Cloudways Autonomous applications hosted in the London region may be experiencing temporary connectivity issues due to a partial disruption. Our team is actively working with the infrastructure provider to restore full stability as quickly as possible.

2. identified 2026-10-20 10:05 UTC

   The issue has been identified as originating from our upstream provider in the London region. We are in close coordination with their team as they work on a resolution. We will provide further updates here as more information becomes available. We apologize for any inconvenience...

3. resolved 2026-10-21 07:15 UTC

   We apologize for the inconvenience. The issue has been resolved. If you continue to experience any related issues, please contact our support team

Excerpts are shortened. Read the full incident on Cloudways's status page.

Affected: Rackspace Email

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-12 05:00 UTC

   We are currently aware of an issue affecting Rackspace email services. Users may experience difficulty logging into their email accounts via the webmail portal or third-party email clients, as well as errors when creating new mailboxes. The Rackspace team has identified the root...

2. resolved 2026-10-13 11:58 UTC

   We have confirmed that the upstream Rackspace email service issue has been fully resolved. All services, including webmail portal logins, third-party email clients, and mailbox creation, are now functioning normally. Thank you for your patience during this time.

Excerpts are shortened. Read the full incident on Cloudways's status page.

Affected: Cloudways Cloud Platform Service, Vultr

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-10-01 06:50 UTC

   We are currently investigating an issue impacting upstream API requests to Vultr. As a result, server management operations involving Vultr instances including launching new servers, cloning existing servers, and executing reboots may time out or fail. Active, running Vultr...

2. resolved 2026-10-14 11:53 UTC

   We have confirmed that the upstream Vultr API performance degradation has been fully resolved. All server management operations including launching new instances, cloning existing servers, and executing reboots are now fully restored and functioning normally. Thank you for your...

Excerpts are shortened. Read the full incident on Cloudways's status page.

Affected: Elastic Email

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-09-01 07:42 UTC

   We are aware of an ongoing upstream issue with Elastic Email that is temporarily impacting email delivery for affected Cloudways accounts. Upstream engineers are actively investigating, and our team is closely following their progress. Further updates will be posted here...

2. monitoring 2026-09-01 07:47 UTC

   Service has been restored for the Elastic Email add-on, and delivery systems are returning to normal operations. We are actively monitoring performance to guarantee full stability. Thank you for your patience while we verify complete restoration.

3. resolved 2026-09-02 01:20 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cloudways's status page.

Affected: DNS Made Easy

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-08-30 10:52 UTC

   We are currently encountering an issue with adding domains and the records in DNS Made Easy addon. As a result, customers may face difficulties managing their DNS configurations or adding new records or domains. Please rest assured that existing DNS records are resolving...

2. monitoring 2026-08-31 06:48 UTC

   The issue with adding new domains and DNS records in the DNS Made Easy add-on has been resolved. We are monitoring the add-on to ensure stability.

3. resolved 2026-09-03 09:15 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cloudways's status page.

Affected: DigitalOcean

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-24 18:36 UTC

   Our DigitalOcean Engineering team is investigating an issue affecting the DigitalOcean Public API. As a result, customers may experience increased response times for API requests, including actions such as server restarts, disk attachments, and server provisioning. The team is...

2. monitoring 2026-08-24 22:04 UTC

   Our DigitalOcean Engineering team has implemented mitigation measures to address the issue affecting the DigitalOcean public API and Cloud Control Panel. We are seeing requests succeed, and users should now be able to access the Cloud Control Panel and issue/receive API requests...

3. resolved 2026-08-25 08:30 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cloudways's status page.

Affected: Cloudways Cloud Platform Service

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-08-20 10:24 UTC

   We have identified an issue causing fatal errors (500 error) on WordPress applications running WordPress 7.1 alongside the WP Rocket plugin. The WP Rocket team has confirmed the issue and is actively working on a resolution. You can monitor their progress and view real-time...

2. monitoring 2026-08-20 10:52 UTC

   The WP Rocket team has released hotfix version v3.23.2.2, which addresses and resolves the issue. Users experiencing this issue are advised to update to WP Rocket v3.23.2.2. Detailed information regarding this issue is available on the WP Rocket Status Page...

3. resolved 2026-08-20 12:25 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cloudways's status page.

Affected: Cloudways Cloud Platform Service

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

1. investigating 2026-08-11 18:18 UTC

   We are currently experiencing an outage with the Google Cloud servers in multiple regions. We are closely coordinating with the team & actively working to resolve this issue. We will share additional updates as we have more information.

2. identified 2026-08-11 20:39 UTC

   We are still working on the outages affecting Google Cloud servers across multiple regions. Our engineering team is actively coordinating with the relevant infrastructure teams to identify the root cause and is working toward resolution. We will share the next update as soon as...

3. monitoring 2026-08-11 21:43 UTC

   The services are being restored, and our team is closely monitoring progress. We anticipate things returning to normal within a few hours and will update you as soon as we have more information.

4. resolved 2026-08-11 23:46 UTC

   The issue has been fully resolved and all services are now back to normal operation. We apologize for any inconvenience caused and thank you for your patience.

Excerpts are shortened. Read the full incident on Cloudways's status page.

Affected: DigitalOcean

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-08-08 21:33 UTC

   We have identified an issue with our service provider, DigitalOcean, affecting their servers. Customers may experience failures when creating new servers and performing Disaster Recovery operations. The issue is limited to DigitalOcean servers. Their team is working to fix the...

2. resolved 2026-08-09 07:11 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cloudways's status page.

Affected: Cloudways Cloud Platform Console

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-08-08 07:18 UTC

   We have just conducted an important platform maintenance to deploy a new feature—Per-Application PHP Version Selection—during the following window. To ensure full platform stability and a seamless rollout, our engineering team is taking extra care during this process. Original...

2. resolved 2026-08-08 14:54 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cloudways's status page.

Affected: Rackspace Email

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-03 14:41 UTC

   We are experiencing issues when adding or deleting Rackspace mailboxes, or updating mailbox passwords, through our Platform. This is resulting in errors for affected users. We are working with the Rackspace team to resolve this issue and will update you as soon as possible. We...

2. monitoring 2026-08-04 06:56 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-08-04 06:56 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cloudways's status page.

Affected: Cloudways Support

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-03 14:23 UTC

   Our team is aware and investigating the issue with our support chat tool, impacting the Inbox, and Messenger. As a result, customers may encounter errors while reporting support issues through chat during this period. You can reach out to us for immediate assistance on ticket...

2. resolved 2026-08-03 22:29 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cloudways's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-23 17:34 UTC

   We are aware that https://feedback.cloudways.com/ is currently inaccessible for our users. Our engineering team is actively investigating the issue and working to restore access as quickly as possible. We apologize for the inconvenience and appreciate your patience while we work...

2. monitoring 2026-07-24 06:36 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-07-24 06:36 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cloudways's status page.

Affected: DigitalOcean

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-07-19 08:24 UTC

   We are investigating a connectivity issue with DigitalOcean in Bangalore. During this time, users may experience connection timeouts and errors for all services deployed in this data center. We will share additional updates as we have more information.

2. resolved 2026-07-19 10:21 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cloudways's status page.

Affected: Rackspace Email

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-07-16 20:57 UTC

   We are experiencing issues when adding or deleting Rackspace mailboxes, or updating mailbox passwords, through our Platform. This is resulting in errors for affected users. We are working with the Rackspace team to resolve this issue and will update you as soon as possible. We...

2. resolved 2026-07-17 13:33 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cloudways's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-14 10:08 UTC

   Some Cloudways Autonomous applications hosted in the London region may experience temporary connectivity issues due to a partial disruption. Our team is actively working with the infrastructure provider to restore full stability as quickly as possible.

2. monitoring 2026-07-14 13:19 UTC

   The majority of applications have resumed normal operation and services are largely restored. Our team continues to closely monitor the situation to ensure full stability.

3. resolved 2026-07-15 08:18 UTC

   The issue has been resolved. Please contact our support if you continue to experience any related issues.

Excerpts are shortened. Read the full incident on Cloudways's status page.

Affected: Vultr

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-07-13 12:26 UTC

   Our upstream provider VULTR has reported that an outage or maintenance window is affecting a subset of users in the Frankfurt region. We will continue to monitor the situation and share further updates as they become available.

2. monitoring 2026-07-13 15:38 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-07-13 15:49 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cloudways's status page.

Affected: Cloudways Cloud Platform Console

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-01 09:38 UTC

   We are currently investigating an issue with the Cloudways Platform Console. Some users may experience intermittent performance issues, loading errors, or frequent, unexpected logouts while navigating the dashboard. Our engineering team is actively diagnosing the root cause to...

2. monitoring 2026-07-01 10:26 UTC

   We have identified the root cause affecting the Platform Console UI and have deployed a fix. Users should now be able to log in and navigate the dashboard normally without experiencing unexpected logouts. We are closely monitoring the platform's stability to ensure performance...

3. resolved 2026-07-01 14:52 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cloudways's status page.

Failure mode: Hardware, power, cooling or another physical failure. Root cause: Hardware or facility. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-30 12:36 UTC

   We are currently experiencing an infrastructure issue caused by a storage malfunction in USSC Region. This may result in degraded performance or service disruptions for some users. Our team is actively investigating and working to resolve the issue as quickly as possible. We...

2. monitoring 2026-06-30 15:53 UTC

   We are seeing positive signs of recovery following the storage malfunction in the USSC Region. The majority of applications have resumed normal operation and services are largely restored. Our team continues to closely monitor the situation to ensure full stability. We will...

3. resolved 2026-07-01 09:35 UTC

   The issue has been resolved. Please contact our support if you continue to experience any related issues.

Excerpts are shortened. Read the full incident on Cloudways's status page.

Affected: Vultr

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-06-22 09:56 UTC

   Our upstream provider, Vultr, is currently experiencing a partial outage at their Frankfurt, Germany location. Their engineering team is actively working to resolve the issue as soon as possible. We regret any inconvenience this may cause.

2. resolved 2026-06-23 02:41 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cloudways's status page.

Affected: Vultr

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-06-06 00:37 UTC

   Our upstream provider Vultr is currently experiencing a partial outage in their Chicago - United States location. Their engineering team is actively working to resolve the issue as soon as possible. We regret any inconvenience this may cause.

2. resolved 2026-06-06 05:04 UTC

   Our upstream provider, Vultr, has resolved the network connectivity issue affecting their Chicago location.

Excerpts are shortened. Read the full incident on Cloudways's status page.

Affected: Cloudflare Enterprise

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Cloudflare.

1. investigating 2026-06-01 15:21 UTC

   Cloudflare is currently investigating issues related to the SaaS Custom Hostname API. Customers may experience slow responses when adding new domains, and newly added domains may also encounter SSL-related errors. Existing domains or applications using Cloudflare remain...

2. monitoring 2026-06-02 17:37 UTC

   A fix has been implemented by the Cloudlfare and they are monitoring the results.

3. resolved 2026-06-03 06:50 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cloudways's status page.

Affected: Rackspace Email

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-25 13:04 UTC

   We are currently receiving multiple reports from customers who are unable to add mailboxes or log in to their Rackspace mailboxes. The issue has already been identified by the Rackspace team, and they are actively working toward a resolution. We will update our status page with...

2. resolved 2026-05-28 12:26 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cloudways's status page.

Affected: DigitalOcean

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-20 01:31 UTC

   We are observing an issue with some of the Block Storage Volume Performance in the New York region on Digital Ocean. During this time, users may experience degraded write performance and intermittent impact to services dependent on the affected storage infrastructure. Our...

2. monitoring 2026-05-20 02:48 UTC

   DO team has implemented mitigation measures for the infrastructure issue affecting Block Storage Volumes in the NYC3 region. The team is monitoring the situation, and we will share another update once the issue is fully resolved

3. resolved 2026-05-20 12:40 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cloudways's status page.

Affected: Vultr

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-05-19 14:21 UTC

   Our upstream provider, Vultr, is currently experiencing a partial outage at their Seoul, Korea location. Their engineering team is actively working to resolve the issue as soon as possible. We regret any inconvenience this may cause.

2. resolved 2026-05-19 17:58 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cloudways's status page.

Affected: Cloudways Cloud Platform Console

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-05-16 09:47 UTC

   We are running a mandatory maintenance activity across a few of our customers’ servers regarding infrastructure stability upgrades. This will require us to restart the servers which will introduce a brief service interruption. We are expecting the Cloudways Platform to remain...

2. identified 2026-05-16 09:49 UTC

   We are continuing to work on a fix for this issue.

3. identified 2026-07-11 07:07 UTC

   The mandatory maintenance is still underway. Our engineering team is actively working to complete the activity as quickly as possible. We appreciate your patience and cooperation in this regard.

4. resolved 2026-08-27 12:10 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cloudways's status page.

Affected: Cloudways Cloud Platform Service

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-05-08 20:08 UTC

   We have Identified that Let's Encrypt experiencing API service outage. Their team is currently investigating the issue. We will provide updates as soon as more information becomes available. We sincerely apologize for any inconvenience this may cause

2. resolved 2026-05-09 01:15 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cloudways's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-08 05:45 UTC

   We are currently experiencing service disruption affecting Cloudways customers hosted on VULTR infrastructure in the Sydney and Melbourne regions. The VULTR team is actively investigating the issue, and we are closely monitoring the situation. We will share further updates as...

2. monitoring 2026-05-08 08:07 UTC

   The service disruption affecting Cloudways customers hosted on VULTR infrastructure in the Sydney and Melbourne regions has now been resolved by the VULTR team. We are continuing to monitor the situation closely to ensure services remain stable. Further updates will be shared if...

3. resolved 2026-05-08 11:54 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cloudways's status page.

Affected: Vultr

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-04-29 21:58 UTC

   Our upstream provider Vultr is currently experiencing a partial outage in their Seoul - Korea location. Their engineering team is actively working to resolve the issue as soon as possible. We regret any inconvenience this may cause.

2. resolved 2026-04-30 08:32 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cloudways's status page.

Affected: Cloudways Cloud Platform Console

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-04-29 19:37 UTC

   We are currently investigating an issue related to the Cloudways Platform dashboard. While our servers remain fully operational and all hosted websites are working fine, some users may experience slow loading times or temporary errors when accessing their account or platform...

2. monitoring 2026-04-29 19:46 UTC

   We have implemented a fix for this issue and are currently monitoring the results. We will provide a final update once the resolution is confirmed.

3. resolved 2026-04-29 23:27 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cloudways's status page.

Affected: Linode

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-04-20 12:33 UTC

   Our upstream provider Linode is currently investigating an emerging service issue affecting connectivity in their Frankfurt (DE-FRA-2) region. We will share further updates as soon as more information becomes available from the provider.

2. monitoring 2026-04-20 14:51 UTC

   A fix has been implemented by the cloud provider team and they are monitoring the results.

3. resolved 2026-04-21 02:15 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cloudways's status page.

Affected: Cloudways Support

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-04-14 12:33 UTC

   We are currently experiencing a service disruption with our chat tool, which is impacting conversations. Our chat tool team is actively investigating the issue and working towards a resolution. We will provide updates here as more information becomes available.

2. resolved 2026-04-14 15:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cloudways's status page.

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-04-04 06:00 UTC

   We’re aware of an issue causing some processes to become stuck in the UI. Our team is actively investigating and working to resolve it as quickly as possible. We regret any inconvenience caused and appreciate your patience.

2. monitoring 2026-04-04 06:58 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-04-04 08:01 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cloudways's status page.

Affected: Vultr

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-04-02 13:58 UTC

   Our upstream provider, Vultr, is currently experiencing a partial outage in their Sydney location. Their network engineers are actively working to restore connectivity as quickly as possible. We regret any inconvenience caused and appreciate your patience.

2. resolved 2026-04-06 18:35 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cloudways's status page.

Affected: Linode

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-03-20 11:42 UTC

   Our upstream provider, Linode, is currently experiencing a partial outage in their Jakarta region. Their engineering team is actively working to resolve the issue as soon as possible. We regret any inconvenience this may cause.

2. monitoring 2026-03-20 18:18 UTC

   Linode has confirmed that the connectivity issues in their Jakarta region have been addressed. Their team will continue to monitor the situation to ensure stability.

3. resolved 2026-03-25 15:30 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cloudways's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-03-16 21:06 UTC

   Some Cloudways Autonomous applications hosted in the US region may experience temporary connectivity issues due to a partial disruption in the underlying storage service. Our team is actively working with the infrastructure provider to restore full stability as quickly as...

2. monitoring 2026-03-16 22:37 UTC

   Storage service is stable and fully restored. Our team continues to monitor system performance.

3. resolved 2026-03-17 09:20 UTC

   The issue has been resolved. Please contact our support if you continue to experience any related issues.

Excerpts are shortened. Read the full incident on Cloudways's status page.

Affected: AWS

Failure mode: A zone, region or data center became unavailable. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

Started during AWS: Multiple services (Bahrain): Region Availability.

Started during AWS: Multiple services (UAE): Region Availability.

1. identified 2026-03-02 08:05 UTC

   Our upstream provider, Amazon Web Services (AWS), is currently experiencing a connectivity and power outage in the Bahrain region, impacting instances hosted in the ME-SOUTH-1 region. Their technical teams are actively investigating the issue and working to restore services as...

2. identified 2026-03-02 18:28 UTC

   AWS is currently experiencing a power outage affecting two of its three data centers in Bahrain. The remaining center is currently over capacity, leading to widespread service failures. Since backups are hosted in the same region, recovery is dependent on AWS restoring local...

3. identified 2026-03-09 19:11 UTC

   We are still working closely with AWS to resolve this issue. AWS services remain impacted, and our team continues to monitor the situation and coordinate with AWS for a resolution. We will share further updates on this status page as more information becomes available. We...

4. resolved 2026-08-28 19:25 UTC

   Following the ongoing AWS outage in the ME-SOUTH-1 (Bahrain) region, we have disabled server provisioning in this region. If you currently have active workloads in ME-SOUTH-1, please migrate them to an alternative region of your choice. Our support team is available if you need...

Excerpts are shortened. Read the full incident on Cloudways's status page.

Affected: AWS

Failure mode: A zone, region or data center became unavailable. Root cause: Hardware or facility. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

Started during AWS: Multiple services (UAE): Region Availability.

1. investigating 2026-03-01 13:53 UTC

   Our upstream provider, Amazon Web Services (AWS), is currently experiencing a connectivity and power outage in the UAE region, impacting instances hosted in the ME-CENTRAL-1 region. Their technical teams are actively investigating the issue and working to restore services as...

2. identified 2026-03-02 18:30 UTC

   AWS is reporting a power outage affecting two Availability Zones in the UAE region. The massive load on the remaining zone is causing widespread disruptions. As backups are localized to this region, they are also impacted. We are tracking AWS updates closely and will notify you...

3. identified 2026-03-09 19:10 UTC

   We are still working closely with AWS to resolve this issue. AWS services remain impacted, and our team continues to monitor the situation and coordinate with AWS for a resolution. We will share further updates on this status page as more information becomes available. We...

4. resolved 2026-08-28 19:26 UTC

   Following the ongoing AWS outage in the ME-Central-1 (UAE) region, we have disabled server provisioning in this region. If you currently have active workloads in ME-Central-1, please migrate them to an alternative region of your choice. Our support team is available if you need...

Excerpts are shortened. Read the full incident on Cloudways's status page.

Affected: Cloudways Cloud Platform Console

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-02-12 14:43 UTC

   Some Cloudways Autonomous applications hosted in the London region may experience temporary connectivity issues due to a partial disruption in the underlying storage service. Our team is actively working with the infrastructure provider to restore full stability as quickly as...

2. investigating 2026-02-12 14:48 UTC

   We are continuing to investigate this issue.

3. monitoring 2026-02-12 22:47 UTC

   Storage service is stable and fully restored. Our team continues to monitor system performance.

4. resolved 2026-02-13 07:16 UTC

   The issue has been resolved. Please contact our support if you continue to experience any related issues.

Excerpts are shortened. Read the full incident on Cloudways's status page.

Affected: Vultr

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-01-28 13:04 UTC

   Our upstream provider Vultr is currently experiencing a partial outage in their Singapore region. Their engineering team is actively working to resolve the issue as soon as possible. We regret any inconvenience this may cause.

2. resolved 2026-01-28 15:34 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cloudways's status page.

Affected: Elastic Email

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-01-19 10:07 UTC

   Our SMTP Add-on Service (Elastic Email) is currently experiencing performance issues, leading to delayed outbound emails for some accounts. We are in active communication with the Elastic Email team to investigate and resolve the root cause. We appreciate your patience and will...

2. monitoring 2026-01-20 10:51 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-01-21 08:20 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cloudways's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-01-19 09:12 UTC

   We are currently investigating an issue where users are experiencing significant delays in receiving two-factor authentication (2FA) codes via email. This issue has been traced to a service degradation with one of our upstream email delivery providers. We are in contact with...

2. resolved 2026-01-19 10:01 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cloudways's status page.

Affected: Cloudways Support

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-01-09 19:48 UTC

   We have identified an issue with our support chat tool that is affecting communication with our customers. As a result, there may be delays when reporting support issues via chat during this period. For immediate assistance, please reach out to us by submitting a support ticket....

2. resolved 2026-01-09 20:54 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cloudways's status page.

Affected: Cloudways Support

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-01-05 14:24 UTC

   We have identified an issue with our support Chat tool, impacting our communication with the customers. As a result, customers may encounter delays while reporting support issues through chat during this period. You can reach out to us on tickets support for immediate...

2. resolved 2026-01-05 15:50 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cloudways's status page.

Affected: Cloudways Cloud Platform Console

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-12-30 12:01 UTC

   We are investigating an ongoing issue affecting backend operations that may lead to temporary performance degradation and issues with server visibility on accessing Cloudways platform. Our team is actively investigating the issue and will prioritize the fix as soon as it is...

2. identified 2025-12-30 13:27 UTC

   Our team is still actively investigating the ongoing issue. We want to assure you that all servers are operating normally and your websites remain fully accessible. We appreciate your continued patience and will provide further updates as soon as more information is available.

3. monitoring 2025-12-30 13:53 UTC

   The fix has been successfully implemented. Our team is now actively monitoring the results to ensure everything is functioning smoothly. We appreciate your patience and will provide further updates if needed.

4. resolved 2025-12-30 15:09 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cloudways's status page.

Affected: Rackspace Email

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-12-29 17:34 UTC

   Rackspace is currently facing issues with webmail login access resulting in unable to log in or use key features at this time. Their engineers are actively investigating the issue. More details will be posted as it becomes available.

2. resolved 2025-12-30 06:20 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cloudways's status page.

Affected: Cloudflare Enterprise

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Cloudflare.

1. identified 2025-12-19 12:14 UTC

   Cloudflare is currently investigating intermittent issues with network performance. Customers may observe unexpected errors while accessing websites that are proxied through Cloudflare or using the Cloudways Cloudflare Add-on. Our engineering team is actively monitoring the...

2. resolved 2025-12-21 19:03 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cloudways's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Cloudflare.

1. investigating 2025-12-05 09:05 UTC

   We are aware of an ongoing Cloudflare network issue that may cause intermittent 5xx errors, connection timeouts, or degraded performance for applications using the Cloudways Cloudflare Add-on or any site proxied through Cloudflare directly. This aligns with the active incident...

2. monitoring 2025-12-05 09:16 UTC

   we have been informed that a fix has been deployed for the issue that was causing intermittent 5xx errors and connectivity disruptions on websites proxied through Cloudflare. Our team is closely monitoring the situation along with Cloudflare to ensure full service stability. If...

3. resolved 2025-12-05 17:18 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cloudways's status page.

Affected: Rackspace Email

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-11-24 13:44 UTC

   We are currently facing a technical issue that is preventing new Rackspace Addon users from creating mailboxes in Rackspace's email service. Our team is working on resolving this matter. We apologize for any inconvenience this may cause and appreciate your patience.

2. investigating 2025-11-24 13:44 UTC

   We are continuing to investigate this issue.

3. resolved 2025-12-05 02:40 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cloudways's status page.