Acquia

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-10-14 19:56 UTC

   Acquia is investigating an issue in Code Studio that is causing some jobs to fail with a connection timed out error. We will update you as soon as more information becomes available.

2. investigating 2026-10-14 20:56 UTC

   Acquia is still investigating an issue in Code Studio that is causing some jobs to fail. We will continue to keep you updated with our investigation.

3. monitoring 2026-10-14 21:20 UTC

   Acquia has identified and deployed a fix for the issue impacting Code Studio that caused some jobs to fail. We are monitoring to ensure stability.

4. resolved 2026-10-14 21:49 UTC

   Acquia has resolved the issue impacting Code Studio that caused some jobs to fail.

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

Affected: Acquia Source

Failure mode: CDN or edge layer failed or served bad content. 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-10-08 18:04 UTC

   Acquia is investigating a caching issue impacting Source CMS that is resulting in downtime for impacted sites. We will update you as more information becomes available.

2. identified 2026-10-08 19:11 UTC

   The cause has been identified and active remediation is underway. Acquia is working to restore full functionality to Source CMS. We will continue to keep you updated as more information becomes available.

3. identified 2026-10-08 20:10 UTC

   Acquia is continuing to work on remediation on the impact of sites experiencing the caching issue with Source CMS. We will continue to keep you updated as more information becomes available.

4. identified 2026-10-08 22:29 UTC

   Acquia is continuing work on remediation of the caching issue with Source CMS. We will keep you updated as we continue the work and more information becomes available.

5. identified 2026-10-08 23:48 UTC

   Acquia has mitigated most of the impact of the caching issue and is continuing work on a solution for sites still impacted. We will update as new information becomes available.

6. resolved 2026-10-09 00:42 UTC

   Acquia has resolved the caching issue impacting Source CMS. We will continue monitoring to ensure stability.

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

Affected: Assets and Templates

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-10-06 15:48 UTC

   We're currently investigating an issue where some EU hosted customers are encountering intermittent errors when searching.

2. resolved 2026-10-06 16:25 UTC

   We've resolved the issue causing intermittent errors when searching for EU hosted customers. Contact Customer Support for help on Acquia DAM Community if you continue to experience any ongoing issues.

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

Affected: Acquia Cloud Next

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-10-06 11:31 UTC

   We are currently investigating reports of site unavailability and performance issues affecting a subset of applications on Acquia Cloud Next. Our engineering and operations teams are actively analyzing the issue to determine the root cause and restore full service as quickly as...

2. investigating 2026-10-06 12:40 UTC

   We are continuing to investigate the site unavailability and performance issues affecting a subset of Acquia Cloud Next applications. Impacted customers might see intermittent 404 Not Found errors while accessing their application. Our engineering and operations teams remain...

3. identified 2026-10-06 13:02 UTC

   We have identified the root cause of the issue resulting in site unavailability and performance issues for a subset of Acquia Cloud Next applications. We are working towards implementing a fix. We will provide another update once we can verify full service restoration.

4. monitoring 2026-10-06 13:36 UTC

   A fix has been implemented to address the site unavailability and performance issues affecting a subset of Acquia Cloud Next applications. Service has been restored and intermittent 404 Not Found errors should no longer occur. We are currently monitoring system performance to...

5. resolved 2026-10-06 14:29 UTC

   We have verified that system performance has fully stabilised following the implemented fix. The site unavailability and performance issues affecting a subset of Acquia Cloud Next applications are now completely resolved, and all services are operating normally. Thank you for...

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

Affected: Acquia Search

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 low confidence (taxonomy v0.2).

1. identified 2026-10-01 22:42 UTC

   Acquia has identified a service interruption impacting Search in the US West region. We are working to resolve this interruption. We will provide additional updates when the service is restored.

2. identified 2026-10-02 04:45 UTC

   Acquia has identified a service interruption impacting Search in the US West region. We are working to resolve this interruption. We will provide additional updates when the service is restored.

3. resolved 2026-10-02 17:12 UTC

   Acquia has resolved the issue and search has restored functionality.

Excerpts are shortened. Read the full incident on Acquia'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-09-22 11:27 UTC

   We are aware of an issue affecting new domain onboarding to the Edge Standard CDN. Customers attempting to add a new domain may see the configuration remain in a “Configure Failed” state. Our team is actively investigating the issue and working to restore normal functionality as...

2. investigating 2026-09-22 11:29 UTC

   We are aware of an issue affecting new domain onboarding to the Edge Standard CDN. Customers attempting to add a new domain may see the configuration remain in a “Configure Failed” state. Our team is actively investigating the issue and working to restore normal functionality as...

3. investigating 2026-09-22 15:48 UTC

   We are continuing to investigate the Edge Standard hostname provisioning failures with the engineering team and upstream vendor. We are currently testing fresh domain provisioning to verify status and will share the next update once we have more findings.

4. investigating 2026-09-23 00:36 UTC

   Investigation into the Edge Standard hostname provisioning failures remains ongoing in coordination with our upstream vendor. There are no significant changes to report at this stage. We will share further updates as our investigation progresses.

5. investigating 2026-09-23 13:28 UTC

   We are continuing our work with the upstream vendor to implement a resolution for the Edge Standard hostname provisioning failures. Thank you for your patience while we work to restore full functionality. We will post another update as soon as we have new findings.

6. monitoring 2026-09-24 04:12 UTC

   The issue impacting Edge Standard hostname provisioning has been mitigated through a resolution implemented with our upstream vendor. Provisioning functions are operating normally, and we are continuing to monitor system performance to ensure ongoing stability.

7. resolved 2026-09-24 05:34 UTC

   The issue affecting Edge Standard hostname provisioning has been fully resolved. All domain setup and provisioning functions are operating normally, and system performance is completely stable.

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

Affected: Acquia Cloud Next, Cloud Platform Enterprise

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-09-07 10:31 UTC

   We are currently investigating an issue where some customers are experiencing timeouts and errors when attempting to initiate Pipelines jobs. Our engineering team is actively looking into the cause of these failures. We will provide another update as soon as more information...

2. monitoring 2026-09-07 11:51 UTC

   We are no longer seeing new instances of the issue affecting pipeline job starts. Our team continues to monitor the service for any recurrence. Further updates will be provided as more information becomes available.

3. resolved 2026-09-07 14:32 UTC

   The issue affecting Acquia Pipelines where jobs were failing to start or timing out for a few customers has been fully resolved. All related services are operating normally, and pipeline jobs are starting and executing as expected.

Excerpts are shortened. Read the full incident on Acquia'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: AWS.

1. monitoring 2026-09-03 23:19 UTC

   Acquia has detected a temporary service interruption impacting the Acquia Task system. This is tied to an outage in AWS US-WEST-2 Region. We are seeing early signs of recovery and continue to monitor their status for full recovery.

2. resolved 2026-09-04 02:18 UTC

   The service interruption impacting the Acquia Task system has been fully resolved. AWS US-WEST-2 operations have stabilized, and all queued tasks and system functions are operating normally.

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

Affected: Acquia Site Studio

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-09-03 23:04 UTC

   We are currently investigating an issue that is affecting multiple customers impacting site studio. We would provide an update as soon as we have one.

2. monitoring 2026-09-04 04:34 UTC

   We've resolved the issue addressing customers use of Site Studio. We're continuing to monitor the service to ensure stability

3. resolved 2026-09-04 09:39 UTC

   The issue impacting Site Studio endpoints has been fully resolved, and all systems are operational now.

Excerpts are shortened. Read the full incident on Acquia'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-09-03 16:27 UTC

   Our upstream search infrastructure partner, SearchStax, is currently experiencing an issue affecting the display of Pulse Performance Graphs; core search functionality remains fully operational and unaffected. SearchStax is actively investigating and working toward a resolution...

2. identified 2026-09-03 17:41 UTC

   Our upstream search infrastructure partner, SearchStax, has identified the root cause of the issue affecting the display of Pulse Performance Graphs. A fix is currently being implemented. Core search functionality remains fully operational and unaffected. We will continue to...

3. resolved 2026-09-04 02:04 UTC

   This incident has been resolved. Our upstream search infrastructure partner, SearchStax, has successfully implemented the fix, and Pulse Performance Graphs are now displaying as expected. Core search functionality was unaffected throughout this incident. We apologize for any...

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

Affected: Acquia DAM, Assets and Templates, Acquia DAM

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 2026-09-03 15:05 UTC

   We are currently investigating an issue with some customers ability to log in to DAM.

2. identified 2026-09-03 15:29 UTC

   We've identified the problem causing an issue with some customers ability to log into DAM and we are working on a fix.

3. monitoring 2026-09-03 15:45 UTC

   We've resolved the problem causing an issue with some customers ability to log into DAM and we are monitoring to ensure stability.

4. resolved 2026-09-03 16:24 UTC

   We've resolve the problem causing an issue with some customers ability to log into DAM. Contact Customer Support for help on Acquia DAM Community if you continue to experience any ongoing issues.

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

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. monitoring 2026-09-02 21:39 UTC

   Acquia identified an issue impacting the ability to access the dashboard in Pipelines for MEO customers. We have set forth a fix and it should no longer be impacting customers we will continue monitoring.

2. resolved 2026-09-03 00:13 UTC

   The issue impacting access to the Pipelines UI and Dashboard for MEO customers has been fully resolved. A fix was deployed and verification was completed to confirm that the Pipelines Dashboard is fully operational and performing normally.

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

Affected: Acquia DAM, Assets and Templates, Acquia DAM

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. 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-31 16:28 UTC

   We are currently investigating an issue with degraded file processing for customers hosted in the EU.

2. monitoring 2026-08-31 17:00 UTC

   A fix has been implemented and we are monitoring to ensure stability. We're also processing work that accumulated during the incident.

3. resolved 2026-08-31 17:34 UTC

   We've resolved the issue causing degraded file processing for customers hosted in the EU and have completed processing work that accumulated during the incident. Contact Customer Support for help on Acquia DAM Community if you continue to experience any ongoing issues.

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

Affected: Acquia Edge Standard

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: Akamai.

1. investigating 2026-08-24 09:29 UTC

   We are aware of an issue affecting all Edge Standard customers, where traffic peak queries are currently failing due to an issue with a vendor API. As a result, security and performance metrics are currently unavailable in the Edge Standard UI. Our team is working with the...

2. resolved 2026-08-24 11:05 UTC

   The issue affecting Edge Standard customers has been resolved. Akamai has addressed the vendor API issue, and security and performance metrics are now available in the Edge Standard UI

Excerpts are shortened. Read the full incident on Acquia'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: Akamai.

1. identified 2026-08-17 21:24 UTC

   We were informed of an emerging issue with connection drops and increased latency for services in the Miami region for customers using Edge Powered by Akamai. The cause of the issue has been identified, and the partner is working on a fix. The issue appears to have started at...

2. identified 2026-08-17 22:29 UTC

   Our partners are continuing to work on a fix for this issue. We will provide an update when more information becomes available.

3. identified 2026-08-18 04:41 UTC

   We are continuing to monitor the situation while our partner works toward a resolution. There are no new updates to report at this time, but we will share further details as soon as we receive progress from their team.

4. identified 2026-08-18 10:24 UTC

   We are continuing to monitor the ongoing incident while our partner work towards a resolution. There is no new information to share at this time, but we are actively tracking the situation. We will post further details as soon as we receive a progress update from our partner.

5. resolved 2026-08-19 22:13 UTC

   We can confirm that the issue was confirmed mitigated at 20:42 UTC on August 18, 2026 and the service has resumed normal operation.

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

Affected: Acquia Cloud Next

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

1. investigating 2026-08-11 07:40 UTC

   We are investigating an issue affecting log download functionality for some customers. Some log download requests may fail or not complete successfully. Our engineering teams are actively investigating the issue and working to restore normal functionality. Other services remain...

2. monitoring 2026-08-11 09:38 UTC

   The issue affecting log download tasks has been mitigated. The Sumo Logic team reverted the change that caused the failures, and log download tasks should now be completing successfully. We are continuing to monitor the service to ensure the issue remains resolved. Further...

3. resolved 2026-08-12 09:27 UTC

   The log download issue affecting Acquia Cloud Next and MEO customers was resolved on Aug 11 09:38 UTC, and all systems are fully operational.

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

Affected: AcquiaID

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-08-10 18:29 UTC

   We are currently investigating an issue impacting the Cloud UI portal, where users are unable to create or submit new support tickets. Affected Service: New support ticket creation in the Cloud UI portal. Unaffected Services: Access to existing tickets, general portal...

2. identified 2026-08-10 18:36 UTC

   We have identified the issue impacting the Cloud UI Portal, where some users are unable to create or submit new support tickets. If you are experiencing a critical issue that requires immediate attention and are unable to submit a ticket, please contact our support team directly...

3. monitoring 2026-08-10 19:15 UTC

   A fix was implemented for the issue impacting Cloud UI Portal, where some users were unable to submit new support tickets. We are actively monitoring the system to ensure full stability and will provide a final update once the issue is fully resolved

4. resolved 2026-08-10 19:44 UTC

   The underlying cause of this service interruption has been addressed. All services are operational at this time.

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

Affected: Acquia Cloud Next

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).

Names an upstream provider: AWS.

1. monitoring 2026-08-06 21:54 UTC

   Acquia detected a service interruption on Acquia Cloud Platform, causing delays in database backups and code deployments using the db backup cloud action. This issue was identified and remediated. We are currently monitoring to confirm full resolution. Affected customers may...

2. resolved 2026-08-06 22:48 UTC

   The underlying cause of this service interruption has been addressed. All services are operational at this time.

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

Affected: Acquia Cloud CD Pipelines

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-04 14:45 UTC

   We are currently investigating an issue where Acquia Cloud Pipelines jobs are failing to start and remaining in a "Queued" state. Users experiencing this issue may see log messages indicating that the job failed to start due to an internal system error and that Pipelines will...

2. monitoring 2026-08-04 15:32 UTC

   A fix has been implemented for the internal system error affecting Acquia Cloud Pipelines. New pipeline jobs are now processing normally, and any previously queued jobs are currently being picked up and processed based on workload. We are actively monitoring the system to ensure...

3. resolved 2026-08-04 16:21 UTC

   The issue affecting Acquia Cloud Pipelines has been resolved. Pipeline processing has returned to normal operations, and all previously queued jobs have been handled. Please note that if any of your queued jobs failed with a "system failure" message during the incident, they can...

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

Affected: SearchStax Search APIs, SearchStax Discovery APIs, SearchStax Pulse Monitoring

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. identified 2026-07-23 16:48 UTC

   We've identified an issue affecting related and popular search functionality. Our team is actively deploying a fix, and we will share further updates as progress is made.

2. monitoring 2026-07-23 17:10 UTC

   A fix has been implemented for the issue affecting related and popular search functionality and Pulse monitoring. We are actively monitoring the systems to confirm full restoration of service. We will provide a final update once stability is confirmed.

3. resolved 2026-07-23 19:35 UTC

   The issue affecting related and popular search functionality and Pulse monitoring has been fully resolved. All systems are operational. We appreciate your patience during this incident.

Excerpts are shortened. Read the full incident on Acquia'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. identified 2026-07-23 16:12 UTC

   We've identified an issue affecting related and popular search functionality. Our team is actively deploying a fix, and we will share further updates as progress is made.

2. identified 2026-07-23 16:24 UTC

   We've identified an issue affecting related and popular search functionality. Our team is actively deploying a fix, and we will share further updates as progress is made.

3. resolved 2026-07-23 19:38 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Acquia'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. identified 2026-07-21 23:08 UTC

   Investigating - We're aware of an issue affecting the availability of some sites and are actively investigating.

2. identified 2026-07-21 23:11 UTC

   We’ve identified the issue affecting the availability of some sites and are actively working on resolving the issue.

3. monitoring 2026-07-21 23:48 UTC

   A fix has been implemented and we are monitoring to ensure stability.

4. resolved 2026-07-22 01:21 UTC

   We've resolved the issue affecting the availability of some sites. Contact Customer Support for help on Acquia DAM Community if you continue to experience any ongoing issues.

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

Affected: Cloud Platform Enterprise, Acquia Cloud CD Pipelines

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: GitHub.

1. identified 2026-07-21 11:39 UTC

   Acquia Pipelines is currently facing disruptions due to an ongoing incident at GitHub (https://www.githubstatus.com/incidents/g40zcbvchny4), where some SSH connections using deploy keys are currently failing. Customers whose applications are connected to GitHub via Acquia...

2. resolved 2026-07-21 12:37 UTC

   The issue impacting Acquia Pipelines is now completely resolved. Git connectivity and pipeline processing have returned to normal operations, and we do not anticipate any further impact.

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

Affected: Acquia Edge Standard

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-17 09:41 UTC

   We are currently investigating an issue impacting CDN provisioning for Edge Standard. New domain configurations may not complete successfully during this time. Our team is actively working to resolve the issue and restore normal operations. Existing domains remain unaffected. We...

2. investigating 2026-07-17 16:08 UTC

   We are continuing to investigate an issue impacting CDN provisioning for Edge Standard. New domain configurations may fail to complete. Our engineering team is actively working to identify the root cause and restore normal operations. Existing domains and currently active CDN...

3. identified 2026-07-17 19:01 UTC

   We have identified the root cause of the issue impacting CDN provisioning for Edge Standard. New domain configurations may still fail to complete during this time. Our engineering team is engaged with our upstream provider and actively working on a fix. Existing domains and...

4. monitoring 2026-07-17 19:27 UTC

   A fix has been implemented for the issue impacting CDN provisioning for Edge Standard. We are now actively monitoring the environment to confirm full resolution. New domain configurations should begin processing normally. We will continue to monitor the fix and provide a final...

5. resolved 2026-07-17 20:06 UTC

   The issue impacting CDN provisioning for Edge Standard has been fully resolved. New domain configurations are now processing successfully, and we have confirmed stability across the environment. No further impact is expected. We apologise for any inconvenience caused and...

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

Affected: Acquia Edge CDN, Acquia Edge Security

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 2026-06-22 14:59 UTC

   Acquia Edge powered by Cloudflare services for some applications are currently interrupted. Customers connecting through North America or accessing services in Europe may see increased latencies and timeouts for applications utilizing Acquia Edge powered by Cloudflare services....

2. identified 2026-06-22 15:05 UTC

   Acquia Edge powered by Cloudflare services for some applications are currently interrupted. Customers connecting through North America or accessing services in Europe may see increased latencies and timeouts for applications utilizing Acquia Edge powered by Cloudflare services....

3. identified 2026-06-22 16:08 UTC

   Issue impacting Acquia Edge powered by Cloudflare services has been identified. Our upstream provider is continuously working to mitigate the impact. We will provide additional updates when services have been fully restored.

4. monitoring 2026-06-22 17:08 UTC

   Acquia Edge powered by Cloudflare services are recovering as our upstream provider has successfully mitigated the majority of congestion and packet drops.We are actively monitoring the recovery process and will provide additional updates once services have been fully restored.

5. resolved 2026-06-22 21:54 UTC

   The underlying cause of this interruption has been addressed. All affected services have been restored. All services are operational at this time.

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

Affected: Acquia Customer Data Platform

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-11 14:02 UTC

   Acquia has identified an issue impacting Google Ads connector processing due to the deprecation of a Google Ads API version used by certain connector workflows. As a result, some Google Ads audience and offline conversion synchronization jobs may fail to execute successfully. We...

2. identified 2026-06-11 18:36 UTC

   Acquia has identified an issue impacting Google Ads connector processing due to the deprecation of a Google Ads API version used by certain connector workflows. As a result, some Google Ads audience and offline conversion synchronization jobs may fail to execute successfully. We...

3. monitoring 2026-06-12 05:25 UTC

   The underlying cause of the recent service interruption has been successfully identified and resolved by our engineering team. All affected services have been fully restored, and core systems are operating normally. We are continuing to monitor performance closely to ensure...

4. resolved 2026-06-12 07:05 UTC

   The underlying cause of this interruption has been addressed. All affected services have been restored. All services are operational at this time.

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

Affected: Acquia Campaign Studio, Acquia Campaign Factory

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 2026-06-01 05:21 UTC

   We are currently investigating a service interruption affecting Acquia Campaign Studio and Campaign Factory, where users are experiencing login failures. Our engineering and operations teams are actively triaging the situation to identify the root cause. We treat login...

2. monitoring 2026-06-01 07:20 UTC

   We have resolved the service interruption affecting Acquia Campaign Studio and Campaign Factory, where users were experiencing login failures. Our engineering and operations teams are actively monitoring the situation to ensure platform stability and performance remain optimal....

3. resolved 2026-06-01 08:49 UTC

   The login issues affecting Acquia Campaign Studio and Campaign Factory have been completely resolved, and all systems are fully operational.

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

Affected: Acquia Cloud Next, Cloud Platform Enterprise, Acquia Site Factory, Acquia Customer Data Platform

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: AWS.

1. investigating 2026-05-08 00:16 UTC

   Acquia has detected a service interruption affecting multiple servers and balancers in AWS Availability Zone us-east-1b. Acquia is investigating the cause and working to restore full services as soon as possible.

2. investigating 2026-05-08 02:34 UTC

   We are continuing to investigate a service interruption that impacts multiple servers and balancers in AWS Availability Zone us-east-1b. Our teams are working diligently to resolve the issue. We will continue to provide updates as soon as they are available.

3. investigating 2026-05-08 03:47 UTC

   Acquia is still investigating the cause of the issue, we will provide additional updates as they become available.

4. investigating 2026-05-08 05:39 UTC

   Acquia is impacted by upstream provider. Our teams are working diligently to resolve the issue. We will continue to provide updates as soon as they are available.

5. investigating 2026-05-08 06:48 UTC

   We are continuing to work with our upstream provider to address the ongoing service interruption. Our engineering teams remain actively engaged in resolving the issue. We will provide another update as soon as more information becomes available.

6. investigating 2026-05-08 08:12 UTC

   Our teams remain actively engaged with our upstream provider to resolve the ongoing impact to our services. We are continuously monitoring the situation and will provide further updates as soon as we have new details to share.Our next scheduled update will be at 10:00 AM UTC.

7. investigating 2026-05-08 10:23 UTC

   We are maintaining close communication with our upstream provider as they work to resolve the underlying issue. Mitigation efforts are still underway, and our team is continuously monitoring the environment. We will provide our next update as soon as there is a change in status.

8. investigating 2026-05-08 11:10 UTC

   We continue to maintain close communication with our upstream provider as they work to resolve the underlying issue. During our ongoing investigation, we have identified that Acquia CDP clients on the US Prod platform are also currently impacted by this outage. Mitigation...

9. investigating 2026-05-08 13:14 UTC

   We are maintaining close communication with our upstream provider while they work to resolve the underlying issue. Mitigation efforts are still underway, and our team continues to actively monitor the environment. We will provide another update as soon as the status changes or...

10. investigating 2026-05-08 15:04 UTC

    We have successfully relaunched services & has unblocked issue for the majority of impacted Acquia Cloud platform customers. These services are currently showing signs of recovery, and we are monitoring them closely to ensure continued stability. However, the underlying issue...

11. investigating 2026-05-08 17:36 UTC

    We have successfully relaunched services & has unblocked issue for the majority of impacted Acquia Cloud platform customers. However, the underlying issue continues to impact Acquia CDP clients & few Acquia Cloud Platform customers on the US Prod platform. We are maintaining...

12. investigating 2026-05-08 19:37 UTC

    This issue continues to impact Acquia CDP clients & few Acquia Cloud Platform customers on the US Prod platform. We are maintaining close communication with our upstream provider while work is done resolve the underlying issue. Mitigation efforts are still underway, and our team...

13. investigating 2026-05-08 21:43 UTC

    This issue is impact Acquia CDP clients & few Acquia Cloud Platform customers on the US Prod platform. We are still maintaining communication with our upstream provider while work is done to resolve the underlying issue. Mitigation efforts are still underway, and our team...

14. investigating 2026-05-08 23:24 UTC

    This issue impacts Acquia CDP clients & few Acquia Cloud Platform customers on the US Prod platform. We are still maintaining communication with our upstream provider as work is done to resolve the underlying issue. Mitigation efforts are still underway, and our team continues...

15. resolved 2026-05-09 13:54 UTC

    The issue with our upstream provider has been fully resolved, and all affected services have been restored to normal operations. Thank you for your patience while we worked to address this issue.

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

Affected: Acquia DAM, Portals, Acquia DAM

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-05-05 19:43 UTC

   We are investigating an issue where some customers are encountering degraded performance when loading Portals.

2. investigating 2026-05-05 22:13 UTC

   We are still investigating an issue where some customers are encountering degraded performance when loading Portals.

3. identified 2026-05-05 23:08 UTC

   We've identified the issue causing degraded Portals performance for some customers and we are working on a fix.

4. monitoring 2026-05-05 23:21 UTC

   A fix has been implemented for the issue causing degraded Portals performance and we're monitoring to ensure stability.

5. resolved 2026-05-06 00:33 UTC

   We have resolved the issue causing degraded Portals performance for some customers. Contact Customer Support for help on Acquia DAM Community if you continue to experience any ongoing issues.

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

Affected: Acquia Cloud Next

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. resolved 2026-05-01 22:11 UTC

   We've detected a service interruption affecting the stability for your application. The issue was quickly identified and resolved. Everything is up and running now.

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

Affected: Acquia Cloud Next

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. resolved 2026-04-30 22:54 UTC

   We've detected a service interruption affecting the shared load balancers for certain customer applications. All services are operational at this time.

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

Affected: Acquia DAM

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-04-29 15:33 UTC

   We are investigating an issue where the global navigation bar is taking longer to load than expected.

2. investigating 2026-04-29 21:08 UTC

   We are continuing to investigate an issue where the global navigation bar is taking longer to load than expected.

3. identified 2026-04-29 22:40 UTC

   We have identified the issue causing the global navigation bar to take longer to load than expected, and we are working on a fix.

4. resolved 2026-04-30 00:30 UTC

   The underlying cause of this issue has been addressed. All affected services have been restored. All services are operational at this time.

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

Affected: Acquia Cloud Next, Cloud Platform Enterprise

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-21 16:41 UTC

   Acquia is currently investigating an issue impacting code deployments for a subset of customers on our Cloud Platform, where users may experience rejected git push commands. Our internal team is actively working to resolve the issue and restore full deployment functionality as...

2. investigating 2026-04-21 19:12 UTC

   We are continuing to investigate the issue impacting code deployment for a subset of customers on our cloud platform. Our engineering team remains actively engaged and are working toward a resolution, and users may continue to experience issues with Git push commands during this...

3. identified 2026-04-21 22:05 UTC

   We identified the issue impacting code deployment for a subset of customers on our cloud platform. Our engineering team remains actively engaged and are working toward a resolution, and users may continue to experience issues with Git push commands during this time. We will...

4. monitoring 2026-04-21 22:26 UTC

   We have implemented a fix for the issue impacting code deployment for a subset of customers on our cloud platform. We are actively monitoring our resolution, please let us know if you continue to experience issues with Git push commands. We will continue to keep you updated and...

5. resolved 2026-04-22 06:33 UTC

   The issue impacting code deployments for a subset of customers on our Cloud Platform has now been resolved. Our engineering team has implemented a fix and all code deployment functionalities are now restored.

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

Affected: Acquia Cloud Next, Cloud Platform Enterprise

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-04-21 04:08 UTC

   Acquia is currently investigating an issue impacting code deployments for a subset of customers on our Cloud Platform, where users may experience rejected git push commands. Our internal team is actively working to resolve the issue and restore full deployment functionality as...

2. investigating 2026-04-21 07:41 UTC

   We are continuing to investigate the issue impacting code deployment for a subset of customers on our cloud platform. Our engineering team remains actively engaged and are working toward a resolution, and users may continue to experience issues with Git push commands during this...

3. resolved 2026-04-21 10:01 UTC

   The issue impacting code deployments for a subset of customers on our Cloud Platform has now been resolved. Our engineering team has implemented a fix and all code deployment functionalities are now restored.

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

Affected: Drupal Cloud UI

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 high confidence (taxonomy v0.2).

1. investigating 2026-04-20 05:39 UTC

   We are currently investigating an issue with Two-Factor Authentication (TFA) that is preventing some users from logging into the Acquia Cloud UI. Affected users may encounter a 403 Forbidden error. Our team is working to resolve this, and we will provide further updates as they...

2. monitoring 2026-04-20 06:27 UTC

   Our engineering team has implemented a fix for the Two-Factor Authentication (TFA) issue that was preventing some users from logging into the Acquia Cloud UI. Services appear to be recovering, and we are actively monitoring the systems to ensure full stability. If you continue...

3. resolved 2026-04-20 07:12 UTC

   The issue impacting Two-Factor Authentication (TFA) and preventing logins to the Acquia Cloud UI has been fully resolved, and all systems are now fully operational. If you continue to experience any lingering issues, please reach out by filing a support ticket. Thank you for...

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

Affected: Acquia Cloud Next

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. investigating 2026-04-17 17:32 UTC

   Acquia is currently investigating an issue impacting code deployments for a subset of customers on our Cloud Platform, where users may experience rejected git push commands. Our internal team is actively working to resolve the issue and restore full deployment functionality as...

2. monitoring 2026-04-17 18:19 UTC

   Acquia has deployed a fix for the issue impacting code deployments for a subset of customers on our Cloud Platform, where users experienced rejected git push commands. Our team is currently monitoring the situation to ensure full deployment functionality is completely restored....

3. resolved 2026-04-17 20:22 UTC

   Acquia has resolved the issue impacting code deployments for a subset of customers on our Cloud Platform. Users should no longer experience rejected git push commands, as full deployment functionality has been completely restored. We sincerely apologize for the inconvenience and...

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

Affected: Acquia Cloud Next

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-04-10 18:32 UTC

   Acquia is currently investigating a performance degradation affecting Log Streaming services on the Acquia Cloud Next platform. Customers may not see any logs when attempting to use Log Streaming service. We are actively investigating the problem, and we will provide updates as...

2. identified 2026-04-10 18:53 UTC

   Acquia has identified the root cause of the performance degradation affecting Log Streaming services on the Acquia Cloud Next platform. Customers may continue to experience missing logs when attempting to use the Log Streaming service. Our engineering team is actively working to...

3. resolved 2026-04-10 20:24 UTC

   Acquia has resolved the performance degradation affecting Log Streaming services on the Acquia Cloud Next platform. Log Streaming functionality has been fully restored, and customers should now see their logs streaming normally. We appreciate your patience and apologize for any...

Excerpts are shortened. Read the full incident on Acquia'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-04-10 02:05 UTC

   We are currently investigating an issue impacting accessibility for multiple sites across the platform. At this time, the exact cause is still being determined, and our engineering team is actively working to identify and resolve the issue. Some customers may experience...

2. monitoring 2026-04-10 02:35 UTC

   The issue impacting multiple sites appears to be resolved, and affected sites are now accessible. We are continuing to monitor the platform closely. If you continue to experience any issues, please reach out via your existing support channels or respond to your open support...

3. investigating 2026-04-10 02:50 UTC

   We are observing a recurrence of the issue impacting multiple sites, and our engineering team is actively investigating.Some customers may again experience intermittent availability or degraded performance. We are working to identify the cause and restore stability as quickly as...

4. monitoring 2026-04-10 04:09 UTC

   The issue impacting multiple sites appears to be resolved, and affected sites are now accessible.We are continuing to monitor the platform closely. If you continue to experience any issues, please reach out via your existing support channels or respond to your open support...

5. resolved 2026-04-10 04:49 UTC

   The issue impacting multiple sites has been resolved, and affected sites are now accessible.We will continue to review this incident internally. If you experience any further issues, please reach out via your existing support channels or respond to your open support ticket.Thank...

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

Affected: Acquia DAM, Acquia DAM

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. 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-04-09 13:12 UTC

   We're currently investigating an issue causing degraded file processing performance for some customers.

2. identified 2026-04-09 13:45 UTC

   The issue causing degraded file processing performance for some customers has been identified and we are working on a fix.

3. identified 2026-04-09 15:56 UTC

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

4. identified 2026-04-09 18:22 UTC

   We are continuing to work on a fix for this issue, we will continue to keep you updated as we work on this.

5. monitoring 2026-04-09 19:25 UTC

   We've implemented a fix for the issue causing degraded file processing performance. We're currently processing work that accumulated during the incident, so some previews may take longer than usual to generate during this time.

6. resolved 2026-04-09 20:47 UTC

   We have completed processing the accumulated work. Contact Customer Support for help on Acquia DAM Community if you continue to experience any ongoing issues.

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

Affected: Acquia Campaign Studio

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-03-25 13:55 UTC

   Acquia has identified an issue impacting accessibility across all Campaign Studio instances. Our team is actively investigating the root cause and working to resolve it.

2. resolved 2026-03-25 15:50 UTC

   The issue impacting accessibility across all Campaign Studio instances has been fully resolved. Our internal engineering team has implemented a fix, and all systems are now operating normally.

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

Affected: Acquia Customer Data Platform

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. 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: Google Cloud.

1. investigating 2026-03-19 15:18 UTC

   We are currently experiencing a production incident in our GCP US environment causing delays to active input connectors, campaigns, and scheduled data refreshes. We are actively working to resolve the issue and will provide hourly updates until full service is restored.

2. monitoring 2026-03-19 16:06 UTC

   The GCP US environment has been stabilised, and we're currently rerunning all input connectors and data refresh workflows. We will also rerun all failed scheduled campaigns and reports when data refresh has completed. A separate notification from our Alerts team will be sent...

3. resolved 2026-03-19 16:54 UTC

   The resource contention issue within our GCP US environment has been successfully resolved. Our engineering team has proactively rerun the majority of the stopped and failed input connectors and data refresh workflows. We are currently monitoring the final batch of these...

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

Affected: Acquia Cloud Next

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-03-13 01:04 UTC

   Acquia is currently investigating an outage impacting multiple load balancers across several regions.Our engineering team is actively engaged and working to identify the issue.

2. investigating 2026-03-13 02:10 UTC

   Update: Our engineering team continues to investigate the load balancer issue. At this time, the impact appears to be limited to a subset of customer applications. Impacted customers have been contacted directly while we continue working toward resolution. Further updates will...

3. monitoring 2026-03-13 03:42 UTC

   The issue appears to be resolved and previously impacted sites are now accessible. Our engineering team will continue to monitor the environment to ensure stability. If you are still experiencing issues with your site, please respond to the support ticket opened for your...

4. resolved 2026-03-14 12:05 UTC

   Acquia has successfully addressed the service interruption impacting a specific load balancer pair. Following a period of monitoring, all associated applications are confirmed to be stable and operating normally. Thank you for your patience and understanding while we worked to...

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

Affected: Acquia Customer Data Platform

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).

Names an upstream provider: AWS.

1. investigating 2026-02-26 18:18 UTC

   We are currently investigating an issue impacting the performance and accessibility of Acquia CDP in the AWS US region (hub2.agilone.com). Our team is actively working to resolve the issue and restore normal operations as quickly as possible. We apologize for the inconvenience...

2. resolved 2026-02-26 18:52 UTC

   Acquia has resolved the issue impacting the performance and accessibility of Acquia CDP in the AWS US region (hub2.agilone.com). Normal operations have been fully restored. We apologize for the inconvenience and appreciate your patience during this time.

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

Affected: Acquia Cloud Next

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 low confidence (taxonomy v0.2).

1. investigating 2026-02-26 02:39 UTC

   We are currently investigating an issue impacting the performance and accessibility of several sites across our Cloud Next platform. Our team is actively working to resolve the issue and restore normal operations as quickly as possible. We apologize for the inconvenience and...

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

   We have identified the root cause and are currently deploying a fix to restore full performance and accessibility. We will provide further details as they become available.

3. monitoring 2026-02-26 04:18 UTC

   Acquia has implemented a solution to resolve the issue affecting performance and accessibility of sites on Acquia Cloud Next. We are closely monitoring this situation. We will continue to provide updates as more information becomes available.

4. resolved 2026-02-26 04:56 UTC

   The underlying cause of this service interruption has been addressed. All affected services have been restored. All services are operational at this time.

Excerpts are shortened. Read the full incident on Acquia'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-29 04:24 UTC

   We are currently investigating an interruption of metrics reporting within the Cloud Platform user interface. Details: Acquia has detected an issue where performance data and charts are failing to load correctly in the Cloud UI. This is due to a connectivity issue with our...

2. investigating 2026-01-29 06:24 UTC

   We are continuing to investigate the metrics interruption in the Cloud UI. There is no change in status since our last update, and we remain engaged with our provider to restore service. Additional information will be provided as it becomes available.

3. resolved 2026-01-29 10:33 UTC

   The issue affecting metrics reporting within the Cloud Platform user interface is resolved, and all systems are now operating normally. Connectivity with the backend metrics provider has been restored, with metrics ingestion working correctly and performance charts loading as...

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

Affected: Acquia Cloud Next, Acquia Source

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-01-15 11:56 UTC

   Acquia is currently investigating an interruption of service for some Applications across Acquia Cloud Next & Acquia Source platforms. Our engineering team is actively working to identify the root cause and restore full service as quickly as possible. We will provide updates as...

2. identified 2026-01-15 12:18 UTC

   Acquia has identified the root cause of the recent interruption of service affecting some Applications across Acquia Cloud Next & Acquia Source platforms. Our engineering team is actively working on implementing a solution to restore full service as quickly as possible. We will...

3. monitoring 2026-01-15 12:28 UTC

   Acquia has deployed a fix for the recent service interruption affecting some Applications across Acquia Cloud Next & Acquia Source platforms. We are currently monitoring the situation to ensure full service stability. We will continue to provide updates as we confirm the...

4. resolved 2026-01-15 12:59 UTC

   Acquia has resolved the recent service interruption affecting some Applications across Acquia Cloud Next & Acquia Source platforms. All services are now operating normally, and we are no longer observing any related issues. Thank you for your patience and understanding while we...

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

Affected: Acquia DAM

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. 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-19 20:55 UTC

   We are aware of an issue causing preview generation to be delayed for some customers, and we are actively investigating.

2. investigating 2025-12-19 22:26 UTC

   We are continuing to investigate the issue causing preview generation to be delayed for some customers.

3. identified 2025-12-19 23:11 UTC

   We've identified the issue causing preview generation to be delayed for some customers, and we are working on a fix.

4. resolved 2025-12-22 17:12 UTC

   We've resolved the issue causing preview generation to be delayed for some customers. Contact Customer Support for help on Acquia DAM Community if you continue to experience any ongoing issues.

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

Affected: Acquia Search

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 2025-12-17 15:07 UTC

   Acquia is currently investigating an interruption of service for Acquia Search which is impacting a few Search stacks. Our engineering team is actively working to identify the root cause and will restore full service as quickly as possible. We will provide updates as more...

2. identified 2025-12-17 16:12 UTC

   Acquia has successfully identified the root cause of the interruption to Acquia Search services. Our engineering team is now focused on implementing a resolution to restore full functionality. We will provide the next update as soon as additional information is available.

3. monitoring 2025-12-17 18:59 UTC

   Acquia has successfully identified the root cause of the interruption to Acquia Search services. Our engineering team has implemented a fix and is now actively monitoring the situation to ensure full functionality is restored. We will provide further updates as more information...

4. resolved 2025-12-17 21:12 UTC

   Acquia has addressed the root cause of the interruption to Acquia Search services, restoring full functionality.

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

Affected: Acquia Search

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 2025-12-16 18:26 UTC

   Acquia is currently investigating an interruption of service for Acquia Search which is impacting a few Search stacks. Our engineering team is actively working to identify the root cause and will restore full service as quickly as possible. We will provide updates as more...

2. identified 2025-12-16 20:14 UTC

   Acquia has successfully identified the root cause of the interruption to Acquia Search services. Our engineering teams are now focused on implementing a resolution to restore full functionality. We will provide the next update as soon as additional information is available.

3. identified 2025-12-16 22:47 UTC

   Acquia has identified the root cause of the interruption to Acquia Search services and continuing to implement a resolution to restore full functionality. We will provide the next update as soon as additional information is available.

4. resolved 2025-12-16 23:14 UTC

   Acquia has addressed the root cause of the interruption to Acquia Search services, restoring full functionality.

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

Affected: Acquia Customer Data Platform

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: AWS.

1. investigating 2025-12-16 05:59 UTC

   Snowflake experiencing partial outage on some regions and this is causing service interruption for Acquia Customer Data Platform tenants hosted on the AWS EU Prod. This is impacting all major processes including Data refresh jobs. Impacted customers will experience delay in...

2. investigating 2025-12-16 10:37 UTC

   Snowflake experiencing partial outage on some regions and this is causing service interruption for Acquia Customer Data Platform tenants hosted on the AWS EU Prod. This is impacting all major processes including Data refresh jobs. Impacted customers will experience delay in...

3. investigating 2025-12-16 13:45 UTC

   Snowflake is experiencing a partial outage in some regions, causing service interruptions for Acquia Customer Data Platform tenants hosted on AWS EU Prod. This is impacting all major processes, including Data refresh jobs. Impacted customers will experience delays in daily data...

4. monitoring 2025-12-16 17:08 UTC

   Snowflake partial outage impacting Acquia Customer Data Platform (CDP) tenants hosted on AWS EU Prod has been resolved. Snowflake has completed mitigation steps as of 15:59 UTC. Impacted customers may have experienced delays in daily data refreshes, as well as failures in...

5. resolved 2025-12-16 18:39 UTC

   Snowflake partial outage impacting Acquia Customer Data Platform (CDP) tenants hosted on AWS EU Prod has been fully resolved. All services are now operating normally, and we have observed stable performance since mitigation steps were completed at 15:59 UTC. No further issues...

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