Anaplan Incident History

1. resolvedSep 10 · 18:04 UTC

   We have confirmed that the issue is now resolved. 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.

Reported by Anaplan on their status page.

1. resolvedSep 7 · 13:46 UTC

   We have confirmed that the issue is now resolved. 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.

Reported by Anaplan on their status page.

1. postmortemSep 9 · 08:38 UTC

   Introduction

   On September 3, 2026, from 14:51 UTC to 16:17 UTC, the in1: Cloud - India region was unavailable. During this period, customers were unable to access or navigate around the platform. 

   Root cause 

   On September 3, 2026, during a planned renewal of security certificates for our services in the India region, an incomplete certificate bundle was applied. This caused authentication and validation services to be unable to verify the secure connection, which resulted in the platform being inaccessible. 

   Recovery 

   Our engineering team identified the issue and took immediate action. We reverted the custom configuration to the platform's managed secure certificate service, which successfully restored connection validation. By 16:17 UTC, the issue was fully resolved. 

   Corrective and preventative actions 

   We are implementing the following actions to prevent recurrence: 

   • We are conducting a thorough audit of all security certificates across our environments to optimize and standardize our configuration management. 

   • We are transitioning to managed certificate services to minimize manual configuration requirements. 

   • We are implementing automated full-chain validation checks for all future security certificate updates to ensure complete integrity prior to deployment. 

    

   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 our Support website. We appreciate your patience during this incident and value the trust you place in Anaplan.

Reported by Anaplan on their status page.

1. postmortemSep 10 · 22:10 UTC

   On 1 September 2026, between 08:00 UTC and 12:20 UTC, customers in our us1: Data Center - US East, us2: Data Center - US West, eu1: Data Center - Netherlands, eu2: Data Center - Germany, eu4: Cloud - Europe, us5: Cloud - US East, us7: Cloud - US, and ap1: Cloud - Japan regions may have experienced delayed CloudWorks™ integrations and intermittent API errors.  

   Root cause 

   An update to our API service, designed to increase internal processing capacity, caused unusual behavior under production load. As a result of this behavior, service resource usage increased unexpectedly to its limit. This throttled request processing and led to network resolution timeouts between internal services. Consequently, integration processes and API requests were intermittently unable to connect to internal back-end components. Additionally, although reverting the update resolved the primary resource issues, doing so removed a fix for startup initialization delays. This caused temporary connection difficulties for some API requests during the recovery period. 

   Recovery 

   Our engineering team immediately initiated our incident response procedures to isolate the source of the delays and restore service. We reverted the API change, restarted internal network resolution services to clear the timeouts, and scaled up integration service capacities across the affected regions. To address the startup initialization delays re-introduced by the rollback, we managed the initialization load and implemented a fix-forward approach by separating the startup delay fix from the original update and successfully redeploying it. By 12:20 UTC, integration processing and API services had stabilized, and by 17:24 UTC, the issue was fully resolved. 

   Corrective and preventative actions 

   We are implementing the following actions to prevent recurrence: 

   • We are redeveloping our API processing code to resolve the underlying resource bottlenecks that led to this incident, ensuring we can safely optimize platform capacity under high load. 

   • We are enhancing our system startup configuration and health check parameters to prevent initialization delays from causing service interruptions. 

   • We are strengthening our network monitoring and observability metrics to provide deeper visibility into internal name resolution and network performance. 

   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 our Support website. We appreciate your patience during this incident and value the trust you place in Anaplan.

Reported by Anaplan on their status page.

1. postmortemSep 10 · 22:09 UTC

   On 1 September 2026, between 08:00 UTC and 12:20 UTC, customers in our us1: Data Center - US East, us2: Data Center - US West, eu1: Data Center - Netherlands, eu2: Data Center - Germany, eu4: Cloud - Europe, us5: Cloud - US East, us7: Cloud - US, and ap1: Cloud - Japan regions may have experienced delayed CloudWorks™ integrations and intermittent API errors.  

   Root cause 

   An update to our API service, designed to increase internal processing capacity, caused unusual behavior under production load. As a result of this behavior, service resource usage increased unexpectedly to its limit. This throttled request processing and led to network resolution timeouts between internal services. Consequently, integration processes and API requests were intermittently unable to connect to internal back-end components. Additionally, although reverting the update resolved the primary resource issues, doing so removed a fix for startup initialization delays. This caused temporary connection difficulties for some API requests during the recovery period. 

   Recovery 

   Our engineering team immediately initiated our incident response procedures to isolate the source of the delays and restore service. We reverted the API change, restarted internal network resolution services to clear the timeouts, and scaled up integration service capacities across the affected regions. To address the startup initialization delays re-introduced by the rollback, we managed the initialization load and implemented a fix-forward approach by separating the startup delay fix from the original update and successfully redeploying it. By 12:20 UTC, integration processing and API services had stabilized, and by 17:24 UTC, the issue was fully resolved. 

   Corrective and preventative actions 

   We are implementing the following actions to prevent recurrence: 

   • We are redeveloping our API processing code to resolve the underlying resource bottlenecks that led to this incident, ensuring we can safely optimize platform capacity under high load. 

   • We are enhancing our system startup configuration and health check parameters to prevent initialization delays from causing service interruptions. 

   • We are strengthening our network monitoring and observability metrics to provide deeper visibility into internal name resolution and network performance. 

   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 our Support website. We appreciate your patience during this incident and value the trust you place in Anaplan.

Reported by Anaplan on their status page.

1. postmortemSep 3 · 15:52 UTC

   On August 27, 2026, at 10:22 UTC, some customers in our ca1: Cloud - Canada region experienced intermittent issues accessing the platform. During this time, users may have encountered errors when attempting to log in. The impact varied depending on which component handled each request — some requests succeeded while others were unsuccessful. 

   Root cause 

   Following a standard system update, a single traffic-routing component in the Canada region entered an inconsistent state after a configuration reload and failed to rebuild its routing instructions correctly. The component began intermittently rejecting or misdirecting customer requests. The component's health checks verified its availability but didn’t capture the correctness of its routing configuration. As a result, it remained active and continued serving traffic. This resulted in some requests succeeding while others were unsuccessful, depending on which component handled the connection. 

   Recovery 

   Our engineering team identified the issue and took immediate action. The team isolated the issue to a single traffic-routing component and restarted it. This redistributed all incoming traffic across the remaining healthy components. By 11:08 UTC, the issue was fully resolved. 

   Corrective and preventative actions 

   We're implementing the following actions to prevent recurrence: 

   • We're hardening the health checks on our traffic-routing components to immediately isolate and automatically restart any component that fails to validate correctly after a configuration update. This prevents a degraded component from continuing to serve traffic and causing intermittent access failures for customers. 

   • We're refining our monitoring to provide more granular visibility into individual service components. This enables faster detection of localized issues before they affect more customers. 

   We apologize for the impact this issue has had on your operations. We're committed to the improvements outlined above to prevent similar disruptions. If you have questions or concerns, please contact our Support team.

Reported by Anaplan on their status page.

1. postmortemAug 25 · 16:00 UTC

   On August 15, 2026, from 03:16 UTC to 08:23 UTC, customers in our eu2: Data Center - Germany region experienced a service interruption that prevented access to the Anaplan platform. During this time, a local infrastructure failure affected the region's ability to connect to external services, resulting in a loss of platform availability. 

   Root cause 

   The disruption was caused by an environmental failure at our vendor's third-party facility in Frankfurt, Germany. A leak in the facility's cooling system led to localized overheating, which triggered automatic safety shutdowns of critical network equipment. Escaped water also damaged localized power distribution systems within the facility, disabling network devices. This combined power and cooling failure prevented the system from resolving external addresses and completing outbound requests in this region. 

   Recovery 

   Because the facility's environmental conditions made the area unsafe to enter, our vendor was delayed in assessing and repairing the affected equipment. As a result, our engineering team deployed an emergency change to reroute traffic through an alternate regional network path, bypassing the impaired facility and region. This successfully restored full external connectivity and name resolution, and platform access was fully restored by 08:23 UTC. 

   The facility’s operator and our vendor continued recovery work over the following days, with full restoration confirmed by August 18. We maintained our emergency routing throughout that period to keep service stable while the vendor completed repairs. 

   Corrective and preventative actions 

   We are implementing the following measures to strengthen resilience and reduce the risk of a similar disruption: 

   • We are adding a layer that automatically redirects traffic to alternate geographic locations during a localized outage, with no manual intervention required. 

   • We are enabling cached records to continue serving traffic when the path to external resolvers is unavailable, so a connectivity loss to external services no longer prevents platform access when a regional event occurs. 

   • We are working with our third-party facility and network providers to review their standards for critical power and cooling systems and ensure stronger preventative safeguards are in place. 

   We apologize for the impact this issue has had on your operations. We are committed to the improvements outlined above to prevent similar disruptions. If you have questions or concerns, please contact our Support team.

Reported by Anaplan on their status page.