Anaplan incident

Platform Alerts - Resolved

Critical Resolved View vendor source →

Anaplan experienced a critical incident on October 15, 2025 affecting us1: Data Center - US East and us2: Data Center - US West and 1 more component, lasting 6h 29m. The incident has been resolved; the full update timeline is below.

Started
Oct 15, 2025, 11:12 AM UTC
Resolved
Oct 15, 2025, 05:41 PM UTC
Duration
6h 29m
Detected by Pingoru
Oct 15, 2025, 11:12 AM UTC

Affected components

us1: Data Center - US Eastus2: Data Center - US Westeu1: Data Center - Netherlandseu2: Data Center - Germanyeu4: Cloud - Europeus5: Cloud - US Eastap1: Cloud - Japanus7: Cloud - USeu3: Cloud - Europe

Update timeline

  1. investigating Oct 15, 2025, 11:12 AM UTC

    We are currently investigating an issue impacting customers’ ability to access the Anaplan Platform. We are working to resolve this issue as quickly as possible and will provide updates every 30 minutes or upon resolution.

  2. investigating Oct 15, 2025, 11:34 AM UTC

    We are currently investigating an issue impacting customers’ ability to access the Anaplan Platform. Thank you for your patience as we continue to investigate this issue. Currently, we do not yet have a time to resolution. We will continue to provide updates every 30 minutes as we work to resolve this issue as quickly as possible.

  3. identified Oct 15, 2025, 11:38 AM UTC

    We have identified the likely cause of the issue, and we are focused right now on restoring service as quickly as possible. Currently, we do not yet have a time to resolution. We will provide further updates in 30 minutes or upon resolution.

  4. identified Oct 15, 2025, 12:10 PM UTC

    We have identified the likely cause of the issue, and are working with the third-party provider to restore service as quickly as possible. Currently, we do not yet have a time to resolution. We will provide further updates in 30 minutes or upon resolution.

  5. identified Oct 15, 2025, 12:41 PM UTC

    We have identified the likely cause of the issue, and continue to work closely with the third-party provider to restore service as quickly as possible. Currently, we do not yet have a time to resolution. We will provide further updates in 30 minutes or upon resolution.

  6. identified Oct 15, 2025, 12:58 PM UTC

    We have confirmed the outage was caused by a power issue at our data center vendor. Power is being steadily restored, and our engineering teams are actively working to bring all systems back online safely. We do not have a specific time for full resolution yet, but we will provide another update in 30 minutes or as soon as we have more information. Thank you for your continued patience.

  7. identified Oct 15, 2025, 01:26 PM UTC

    Our teams are making steady progress and services are gradually recovering. We are focused on restoring the platform quickly and safely for all users. While we cannot provide a specific time for full resolution yet, we are committed to providing an update in 30 minutes or sooner if there is a significant development. Thank you for your continued patience.

  8. identified Oct 15, 2025, 01:43 PM UTC

    Services are continuing to come back online, but the platform is not yet fully stable. Some features may be slow or temporarily unavailable as we work to complete the full recovery. While we cannot provide a specific time for resolution, we are committed to providing an update in 30 minutes or sooner if there is a significant development. Thank you for your continued patience.

  9. identified Oct 15, 2025, 02:12 PM UTC

    Our restoration efforts are progressing, and we are seeing continued improvement across the platform. However, performance is not yet fully restored, so some features may still be slow or intermittently available. Our teams remain focused on achieving a full and stable recovery. We will provide our next update within 30 minutes, or sooner if the situation changes significantly. We appreciate your ongoing patience.

  10. identified Oct 15, 2025, 02:41 PM UTC

    We have made significant progress in our AP1 and EU4 regions, and most services are now available. However, the Cloudworks integration service in these regions remains unavailable. Our teams are actively working on restoring it. For all other regions, platform recovery is still underway. While services are returning, some features may remain slow or intermittently available as we work toward a full and stable recovery for all users. We will provide another update in 30 minutes or sooner if there is a significant development. Thank you for your continued patience.

  11. identified Oct 15, 2025, 03:01 PM UTC

    We have made significant progress, and most services are now available in our AP1, EU4, US5, and US7 regions. However, the Cloudworks integration service remains unavailable in these regions for the time being as our teams continue to work on restoring it. For all other regions, platform recovery is still underway. While services are returning, some features may remain slow or intermittently available as we work toward a full and stable recovery for all users. We will provide another update in 30 minutes or sooner if there is a significant development. Thank you for your continued patience.

  12. identified Oct 15, 2025, 03:18 PM UTC

    We have made significant progress, and most services are now available in our AP1, EU1, EU3, EU4, US2, US5, and US7 regions. However, the Cloudworks integration service remains unavailable in these regions for the time being as our teams continue to work on its restoration. For all other regions, platform recovery is still underway. While services are returning, some features may remain slow or intermittently available as we work toward a full and stable recovery for all users. We will provide another update in 30 minutes or sooner if there is a significant development. Thank you for your continued patience.

  13. identified Oct 15, 2025, 03:34 PM UTC

    Service has now been restored across all regions. Cloudworks is online and actively processing the backlog of integrations that accumulated during the outage. New tasks may experience a delay until this backlog is cleared. We will provide another update every 30 minutes or upon resolution. If you have any questions, concerns, or continue to experience issues, please do not hesitate to contact Anaplan Support.

  14. identified Oct 15, 2025, 04:01 PM UTC

    Cloudworks is actively processing the backlog of integrations that accumulated during the outage. As the system works through this queue, you may notice a delay in the processing of new integration tasks. Our teams are monitoring performance as it returns to normal. We will provide our next update in 60 minutes or or upon resolution. We appreciate your ongoing patience.

  15. identified Oct 15, 2025, 05:13 PM UTC

    Service has now been restored across all regions and Cloudworks is fully operational. Our system is continuing to actively process the backlog of integrations that accumulated during the outage. Consequently, new tasks may experience a delay until this backlog is cleared. We will continue to provide an update in 60 minutes or upon full resolution. Should you have any questions or continue to experience issues, please do not hesitate to contact Anaplan Support.

  16. resolved Oct 15, 2025, 05:41 PM UTC

    We have confirmed service has now been restored across all regions and Cloudworks is fully operational. The backlog of integrations continues to process and we have not seen any further issues. We will monitor this internally to ensure integrations continue successfully. We deeply apologize for any impact this issue may have caused. We appreciate your patience and partnership as we worked through this issue. We will follow up within 7 business days with a detailed root cause analysis (RCA) that will be shared on our Status Page. If you have any question or concerns, please do not hesitate to contact us at Anaplan Support.

  17. postmortem Oct 24, 2025, 10:25 AM UTC

    On October 15, 2025, starting at 10:53 UTC, Anaplan experienced a major service disruption. The incident began with a period of complete service unavailability for a subset of Anaplan regions, followed by a period of degradation as our teams worked to restore full functionality. The table below details the impact for each region. During the degradation period, the platform was available, but some services, such as CloudWorks™ integrations, processed at a slower rate than usual. **Region:** US1 – Data Center \(US East\) **Unavailability \(UTC\):** 10:53 – 15:18 **Degradation \(UTC\):** 15:18 – 15:34 **Region:** US2 – Data Center \(US West\) **Unavailability \(UTC\):** 10:53 – 15:18 **Degradation \(UTC\):** 15:18 – 15:34 **Region:** EU1 – Data Center \(Netherlands\) **Unavailability \(UTC\):** 10:53 – 15:18 **Degradation \(UTC\):** 15:18 – 15:34 **Region:** EU2 – Data Center \(Germany\) **Unavailability \(UTC\):** 10:53 – 15:18 **Degradation \(UTC\):** 15:18 – 15:34 **Region:** AP1 – Cloud \(Japan\) **Unavailability \(UTC\):** 10:53 – 14:41 **Degradation \(UTC\):** 14:41 – 15:34 **Region:** EU4 – Cloud \(Europe\) **Unavailability \(UTC\):** 10:53 – 14:41 **Degradation \(UTC\):** 14:41 – 15:34 **Region:** US5 – Cloud \(US East\) **Unavailability \(UTC\):** 10:53 – 15:01 **Degradation \(UTC\):** 15:01 – 15:34 **Region:** US7 – Cloud \(US\) **Unavailability \(UTC\):** 10:53 – 15:18 **Degradation \(UTC\):** 15:18 – 15:34 **Root Cause** The incident was triggered by a utility power failure at a data center facility operated by one of our infrastructure providers. This facility hosts a hub providing critical, shared services that our regional spokes depend on. Our data centers are designed with multiple layers of power redundancy, including Uninterruptible Power Supplies \(UPS\) and on-site backup generators. During this incident, our provider's backup power system failed to operate as designed. A malfunction in their power transfer equipment prevented the generators from taking on the electrical load. **Our Response** Our foremost commitment is to the integrity of our customers' data. Upon detecting the power failure, our global engineering teams and the partner responded immediately. Faced with the choice between a longer recovery with potential data loss \(by invoking our Disaster Recovery plan\) against a faster, direct restoration of the physically intact facility, we chose the path that guaranteed data protection and minimized the overall recovery time. **Recovery Timeline** Once power was stabilized at 13:08 UTC, we initiated a systematic, multi-phased recovery to safely restore services and ensure data integrity. All core functionality was restored by 15:34 UTC. Customers using CloudWorks would have continued to experience a level of degradation on these integrations as the service processed a large backlog of tasks. By 17:41 UTC, all platform services were stable, and the integration backlog was fully cleared. **Corrective and Preventative Actions** We are taking immediate and long-term actions to prevent a recurrence and strengthen the resilience of our platform. * **Immediate provider and facility actions:** In partnership with our infrastructure provider, we have completed a rigorous root cause analysis. Our provider has replaced the faulty equipment and audited their facility. We are conducting our own independent verification of these corrective actions. We are also deploying enhanced monitoring to provide earlier warnings of potential power-related issues at any of our provider facilities. * **Anaplan led resilience program:** This incident has highlighted a key architectural dependency. To address this, we are accelerating our long-term strategy to re-architect our platform for greater resilience. This program will reduce dependencies on any single facility and is designed to prevent a localized issue from having a cascading impact. Furthermore, we have initiated a comprehensive audit of power failover mechanisms across all our data centers to identify and mitigate similar risks. We apologize for any impact this issue may have had on your business operations. We are continuously strengthening our systems and procedures to ensure we avoid future disruptions to your business and users. If you have further questions or concerns, please visit the Anaplan Support website. Thank you for your patience during this situation and thank you for being an Anaplan customer.