Critical incident

Anaplan: Platform Alerts

Affected: us5: Cloud - US East

Current status of Anaplan: Operational — live Anaplan status

Timeline

1. Jun 3, 2026, 14:53 UTC
   investigating
   We are currently investigating an issue resulting in some customers not being able to load workspaces. We are working to resolve this issue as quickly as possible and will provide updates every 30 minutes or upon resolution.
2. Jun 3, 2026, 15:05 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 do not yet have a time to resolution. We will provide further updates in 30 minutes or upon resolution.
3. Jun 3, 2026, 15:10 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.
4. Jun 3, 2026, 15:50 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.
5. Jun 11, 2026, 22:49 UTC
   postmortem
   On 03 June 2026, between 13:56 and 15:50 UTC, customers in the us5: Cloud - US East region experienced a service disruption. During this time, users were unable to open or schedule workspaces, and workspace allocations remained unmapped, resulting in regional unavailability. **Root cause** A planned update to our cluster management infrastructure caused an unexpected increase in memory requirements for our core scheduling service. This caused the service to reach its predefined resource limits and restart repeatedly, which temporarily prevented the platform from processing workspace requests in the affected region. **Recovery** Our engineering team took immediate steps to resolve the resource constraints and restore service to the region. We applied a permanent fix to the scheduling infrastructure, which stabilized the environment and allowed all pending workspace requests to complete. Full service was restored by 15:50 UTC. **Corrective and preventative actions** * We are implementing increased memory thresholds across all regional clusters to provide additional operational headroom during management system updates. * We are prioritizing the implementation of an active-standby service configuration to eliminate single points of failure and ensure seamless, automated failovers. * We are resolving an observability gap to ensure that service performance and resource metrics remain visible even during periods of high system stress. * We are developing a dedicated runbook for resource-related interruptions to ensure faster identification and standardized remediation steps. * We are conducting a detailed investigation into the management system update to understand why the memory increase occurred and prevent similar behavior in future upgrades. 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](https://support.anaplan.com/) team.

Updates as published by Anaplan (original).