Acquia Outage History

Acquia's Cloud Platform Enterprise experienced an issue where a subset of customers encountered rejected git push commands, preventing code deployments for 13.9 hours. The engineering team identified and implemented a fix, restoring all code deployment functionality. The incident affected the platform's deployment capabilities, disrupting development workflows for impacted users.

Acquia experienced a major issue affecting code deployments on their Cloud Platform Enterprise service, where a subset of customers encountered rejected git push commands for 6 hours. The incident prevented users from deploying code to their applications through the normal git-based workflow. Acquia's engineering team implemented a fix that restored all code deployment functionality.

Acquia experienced a Two-Factor Authentication (TFA) issue that prevented some users from logging into the Acquia Cloud UI, with affected users encountering 403 Forbidden errors. The incident impacted the Drupal Cloud UI for 1.6 hours. The engineering team implemented a fix and confirmed full resolution, with all systems returning to normal operation.

Acquia experienced an issue affecting code deployments on their Cloud Platform for a subset of customers, causing git push commands to be rejected. The incident lasted 2.9 hours before a fix was deployed and full deployment functionality was restored. The issue prevented affected users from deploying code to their applications during the outage period.

Acquia experienced a performance degradation affecting Log Streaming services on the Acquia Cloud Next platform for 1.9 hours. Customers were unable to see logs when attempting to use the Log Streaming service during this period. The issue was identified and resolved, with Log Streaming functionality fully restored and logs streaming normally again.

Acquia experienced a service interruption that impacted accessibility for multiple sites across their platform, causing customers to experience intermittent availability and degraded performance. The issue occurred twice during the 2.8-hour incident window, with an initial resolution followed by a recurrence that required additional investigation. The engineering team ultimately resolved the problem and restored full accessibility to all affected sites.

Acquia DAM experienced degraded file processing performance that affected some customers for 7.6 hours. The issue caused delays in file processing and preview generation within the digital asset management platform. The problem was identified and fixed, with all accumulated work processed and normal performance restored.

Acquia experienced a service interruption that made all Campaign Studio instances inaccessible for 2 hours. The engineering team investigated the root cause and implemented a fix to restore normal operations. All Campaign Studio systems are now functioning normally.

Acquia experienced a resource contention issue in their GCP US environment that caused processing delays for input connectors, campaigns, and scheduled data refreshes in the Customer Data Platform. The incident lasted 1.7 hours and affected active data processing workflows. The engineering team resolved the underlying issue and proactively reran the majority of stopped and failed workflows, with monitoring continuing for the final batch to ensure complete restoration.

Acquia experienced a major outage affecting multiple load balancers across several regions, which impacted a subset of customer applications and made some sites inaccessible. The incident lasted 35.1 hours before engineering teams successfully resolved the load balancer issues. All affected applications were confirmed stable and operating normally following a monitoring period.