Anaplan experienced a major incident on June 1, 2026 affecting ap1: Cloud - Japan, lasting 35m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jun 01, 2026, 02:05 AM UTC
We are currently investigating an issue resulting in some customers not being able to load or create models. We are working to resolve this issue as quickly as possible and will provide updates every 30 minutes or upon resolution.
- identified Jun 01, 2026, 02:29 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.
- resolved Jun 01, 2026, 02:40 AM 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.
- postmortem Jun 09, 2026, 10:24 PM UTC
**Introduction** On June 1, 2026, at 01:51 UTC, customers in our ap1: Cloud - Japan region reported that they were experiencing intermittent delays and difficulties accessing models, loading workspaces, and saving changes. During the incident, affected users encountered intermittent timeouts, while other platform services and regions were unaffected. **Root Cause** Our investigation identified that the issues were caused by resource contention within a backend data storage service component. When saving history logs for specific models, the storage component briefly secures exclusive access to the model's data file. Shortly before the issue occurred, a small number of save operations experienced a minor pause, which resulted in other waiting requests to time out and automatically retry. This sudden volume of retries congested the component’s processing capacity. As a result, the component lacked the processing resources required to complete and release the original save operation, keeping the file locked and causing subsequent requests to fail and overload the system. **Recovery** We investigated the issue and identified the specific, unresponsive data service component. We completed a restart to clear the backlog and restore normal operations. After the restart, we monitored the platform closely to ensure stability. Full service was restored by 02:41 UTC. **Corrective & Preventative Actions** We are implementing several measures to prevent a recurrence and continuously improve platform stability: * We have deployed automated health check probes and back-pressure controls to identify and isolate unresponsive service instances automatically. * We are implementing a mechanism to automatically cancel save operations that take abnormally long, which prevents the system from hanging and avoids prolonged lockouts for users. * We are enabling protective traffic controls and overload detection within our data storage service to manage heavy spikes in activity safely. * We are reviewing the automated retry configuration for the data saving process to improve the handling of any stalled save operations, minimizing wait times for other requests. We apologize for any impact this issue may have had on your business operations. We are strengthening our systems and procedures to avoid disruptions to your business and users. If you have further questions or concerns, please visit our [Support website](https://www.google.com/url?q=https%3A%2F%2Fsupport.anaplan.com%2F). We appreciate your patience during this incident and value the trust you place in Anaplan.