Anaplan experienced a minor incident on September 16, 2026 affecting us5: Cloud - US East, lasting 17m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Sep 16, 2026, 12:24 PM 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 Sep 16, 2026, 12:35 PM 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 Sep 16, 2026, 12:41 PM 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 Sep 24, 2026, 06:09 PM UTC
On 16 September 2026, at 12:07 UTC, customers in our us5: Cloud - US East region experienced delays in completing CloudWorks™ integration runs. **Root cause** During a scheduled maintenance window on our underlying messaging infrastructure, active connections to the CloudWorks™ service were temporarily suspended. Due to a connection handling limitation, the service didn’t automatically recover once the maintenance was complete. This left the processing components in an unresponsive state, which prevented integration runs from completing and resulted in elevated resource consumption. **Recovery** Our engineering team identified the issue and took immediate action. We restarted and scaled the scheduling and processing components, which immediately restored normal schedule completions. By 12:36 UTC, the issue was fully resolved. **Corrective and preventative actions** We are implementing the following actions to prevent recurrence: * We are improving our connection-handling mechanisms to ensure that processing services can automatically and gracefully reconnect to messaging infrastructure during any maintenance events. * We are assessing automated recovery mechanisms to proactively detect and resolve scheduling pauses without manual intervention. 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. We appreciate your patience during this incident and value the trust you place in Anaplan.