Anaplan experienced a minor incident on June 10, 2026 affecting us1: Data Center - US East, lasting 53m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jun 10, 2026, 09:48 AM UTC
We are currently investigating an issue impacting customers’ ability to run Cloudworks integrations. We are working to resolve this issue as quickly as possible and will provide updates every 30 minutes or upon resolution.
- monitoring Jun 10, 2026, 10:15 AM UTC
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.
- resolved Jun 10, 2026, 10:42 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 19, 2026, 03:12 PM UTC
**Introduction** On June 10, 2026, at 09:48 UTC, customers in us1: Data Center - US East experienced slight delays in the processing and successful completion of CloudWorks™ integrations. **Root cause** During routine database patching on June 10, all regions completed without issue except for the us1: Data Center - US East region, where CloudWorks encountered an unexpected loss of database connectivity. This caused deadlocks within the scheduler service. Our investigation determined that one remote connection had been dropped while a second remained active, resulting in connection conflicts and errors. The issue was remediated by performing a rolling restart of the scheduler service and clearing the database rules. **Recovery** Upon identifying the issue, our engineering team acted quickly to initiate a rolling restart of the scheduler service across the affected region. To fully resolve the connection conflict and errors, the team cleared the internal routing and caching rules associated with the database gateway. Following this action, the database connection errors ceased immediately, and manual validation confirmed that integration scheduling had been fully restored. The issue was completely resolved by 10:42 UTC. **Corrective and preventative actions** We are implementing the following actions to prevent recurrence and improve service reliability: * We are developing enhanced system alerts to immediately detect database connectivity issues and abnormal error volumes. * We are working to replicate the scenario in non-production environments to strengthen CloudWorks' ability to recover from database disconnections. * We are currently reviewing the errors encountered, along with the relevant system settings, to determine whether any changes can be implemented to better handle this type of issue in the future. * We are reviewing and optimizing the capacity and sizing of our integration services across all regions to ensure they are robust and resilient. * We are establishing more detailed incident response runbooks and centralizing triage procedures to accelerate resolution of similar issues. * We are strengthening our platform observability and system telemetry to improve our diagnostic capabilities and detect connection issues more rapidly. 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](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.