Anaplan Status Page

May 28, 2026 · resolved May 28

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.

May 22, 2026 · resolved May 22

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.

May 9, 2026 · resolved May 9

On May 9, 2026, between 10:00 UTC and 18:07 UTC, we experienced an issue that intermittently disrupted platform workflows and related CloudWorks™ integrations in the eu4: Cloud - Europe region. During this time, customers may have noticed slower page loads, intermittent errors, or delays in their scheduled workflows.  **Root cause**  Our investigation identified that the disruption was caused by a network connectivity issue between the eu4: Cloud - Europe region and our primary data center. Specifically, intermittent packet loss on our cloud provider's network infrastructure prevented our regional servers from reliably communicating with our central services. This interruption in communication led to the intermittent workflow delays customers may have experienced.  **Recovery**  Upon detecting the initial workflow delays, our engineering team immediately restarted the affected services, which temporarily restored functionality. When the issue recurred, we identified the broader network connectivity problem. We immediately rerouted traffic away from the affected regional servers directly to our primary data center, successfully bypassing the network issue and restoring full service stability at 18:07 UTC. We also engaged our cloud provider to investigate and resolve the underlying network infrastructure problem.  **Corrective and preventative actions**  To prevent a recurrence of this issue and further strengthen our platform, we are taking the following steps:  * We are implementing early warning alerts that specifically monitor the health of these network paths so we can detect and bypass issues before they impact service.  * We are refining our automated rerouting logic to ensure that if one path fails, the system moves traffic to a healthy path without requiring manual intervention.  * We are collaborating closely with our cloud provider to ensure their network infrastructure continues to meet our high reliability standards.  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](https://www.google.com/url?q=https%3A%2F%2Fsupport.anaplan.com%2F) website. We appreciate your patience during this incident and value the trust you place in Anaplan.

May 9, 2026 · resolved May 9

On May 9, 2026, between 10:00 UTC and 18:07 UTC, we experienced an issue that intermittently disrupted platform workflows and related CloudWorks™ integrations in the eu4: Cloud - Europe region. During this time, customers may have noticed slower page loads, intermittent errors, or delays in their scheduled workflows.  **Root cause**  Our investigation identified that the disruption was caused by a network connectivity issue between the eu4: Cloud - Europe region and our primary data center. Specifically, intermittent packet loss on our cloud provider's network infrastructure prevented our regional servers from reliably communicating with our central services. This interruption in communication led to the intermittent workflow delays customers may have experienced.  **Recovery**  Upon detecting the initial workflow delays, our engineering team immediately restarted the affected services, which temporarily restored functionality. When the issue recurred, we identified the broader network connectivity problem. We immediately rerouted traffic away from the affected regional servers directly to our primary data center, successfully bypassing the network issue and restoring full service stability at 18:07 UTC. We also engaged our cloud provider to investigate and resolve the underlying network infrastructure problem.  **Corrective and preventative actions**  To prevent a recurrence of this issue and further strengthen our platform, we are taking the following steps:  * We are implementing early warning alerts that specifically monitor the health of these network paths so we can detect and bypass issues before they impact service.  * We are refining our automated rerouting logic to ensure that if one path fails, the system moves traffic to a healthy path without requiring manual intervention.  * We are collaborating closely with our cloud provider to ensure their network infrastructure continues to meet our high reliability standards.  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](https://www.google.com/url?q=https%3A%2F%2Fsupport.anaplan.com%2F) website. We appreciate your patience during this incident and value the trust you place in Anaplan.

May 7, 2026 · resolved May 7

On May 7, 2026, between 20:41 and 22:26 UTC, customers in the us7: Cloud - US region experienced degraded performance. Affected customers intermittently received internal server errors when using Anaplan XL and other add-ins, which caused some refresh actions to fail.  **Root cause** The issue occurred in the us7: Cloud - US region when the service that handles add-in requests became saturated and could not process inbound requests quickly enough. As demand exceeded available processing capacity, requests queued and then failed, resulting in internal server error responses for add-in users.  **Recovery** Our engineering team identified the issue and took immediate action by completing a rolling restart of the impacted service, which cleared the backlog and restored normal request processing. By 22:26 UTC, the issue was fully resolved.  **Corrective and preventative actions**  * We are implementing improved alerting to detect increased internal server error rates earlier.   * We are implementing additional monitoring for request queue behavior and saturation signals to prevent a backlog from building.   * We are implementing a review and tuning of request-processing capacity to better handle spikes.   * We are implementing logging improvements to speed up diagnosis and reduce recovery time for similar events.  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.