Major incident

Anaplan: Platform Alerts

Affected: ca1: Cloud - Canada

Current status of Anaplan: Operational — live Anaplan status

Timeline

1. Aug 27, 2026, 10:22 UTC
   investigating
   We are currently investigating an issue impacting customers’ ability to access the Anaplan Platform in Canada. We are working to resolve this issue as quickly as possible and will provide updates every 30 minutes or upon resolution.
2. Aug 27, 2026, 10:52 UTC
   investigating
   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. Aug 27, 2026, 10:57 UTC
   identified
   We have identified the likely cause of the issue, and we are focused right now on restoring service as quickly as possible. Currently, We will provide further updates in 30 minutes or upon resolution.
4. Aug 27, 2026, 10:58 UTC
   monitoring
   Service has now been restored; you should now be able to resume normal activities. We will continue to monitor the platform to ensure no additional issues arise. If you have any questions, concerns, or continue to experience issues, please do not hesitate to contact Anaplan Support. We will provide a final update to you when we consider this situation fully resolved.
5. Aug 27, 2026, 11:08 UTC
   resolved
   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.
6. Sep 3, 2026, 15:52 UTC
   postmortem
   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](https://support.anaplan.com/) team.

Updates as published by Anaplan (original).