Anaplan outage history

We are currently investigating an issue impacting customers’ ability to access the Anaplan Platform. We are working to resolve this issue as quickly as possible and will provide updates every 30 minutes or upon resolution.

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.

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.

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.

We are currently investigating an issue impacting customers’ ability to access the Anaplan Platform. We are working to resolve this issue as quickly as possible and will provide updates every 30 minutes or upon resolution.

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.

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.

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.

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.

Thank you for your patience as we continue to investigate this issue. Currently, we do not yet have a time to resolution. We will continue to provide updates every 30 minutes as we work to resolve this issue as quickly as possible.

Thank you for your continued patience while we investigate this issue. We have confirmed a problem affecting CloudWorks integrations across multiple regions. This remains a top priority, and we do not yet have an estimated time to resolution. We will continue to share updates every 30 minutes as we work to resolve this as quickly as possible.

Thank you for your continued patience while we investigate this issue. We have observed CloudWorks integrations starting and completing successfully across all regions; however, we continue to monitor the situation closely. We will share further updates every 30 minutes as we work to resolve this as quickly as possible.

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.

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.

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.

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.

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.

We are currently investigating an issue impacting customers’ ability to access the Anaplan Platform in Canada. We are working to resolve this issue as quickly as possible and will provide updates every 30 minutes or upon resolution.

Thank you for your patience as we continue to investigate this issue. Currently, we do not yet have a time to resolution. We will continue to provide updates every 30 minutes as we work to resolve this issue as quickly as possible.

We have identified the likely cause of the issue, and we are focused right now on restoring service as quickly as possible. Currently, We will provide further updates in 30 minutes or upon resolution.

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.

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.

On August 27, 2026, at 10:22 UTC, some customers in our ca1: Cloud - Canada region experienced intermittent issues accessing the platform. During this time, users may have encountered errors when attempting to log in. The impact varied depending on which component handled each request — some requests succeeded while others were unsuccessful.  **Root cause**  Following a standard system update, a single traffic-routing component in the Canada region entered an inconsistent state after a configuration reload and failed to rebuild its routing instructions correctly. The component began intermittently rejecting or misdirecting customer requests. The component's health checks verified its availability but didn’t capture the correctness of its routing configuration. As a result, it remained active and continued serving traffic. This resulted in some requests succeeding while others were unsuccessful, depending on which component handled the connection.  **Recovery**  Our engineering team identified the issue and took immediate action. The team isolated the issue to a single traffic-routing component and restarted it. This redistributed all incoming traffic across the remaining healthy components. By 11:08 UTC, the issue was fully resolved.  **Corrective and preventative actions**  We're implementing the following actions to prevent recurrence:  * We're hardening the health checks on our traffic-routing components to immediately isolate and automatically restart any component that fails to validate correctly after a configuration update. This prevents a degraded component from continuing to serve traffic and causing intermittent access failures for customers.  * We're refining our monitoring to provide more granular visibility into individual service components. This enables faster detection of localized issues before they affect more customers.  We apologize for the impact this issue has had on your operations. We're 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.

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.

We are currently investigating an issue impacting customers’ ability to access the Anaplan Platform, which is also impacting CloudWorks integrations We are working to resolve this issue as quickly as possible and will provide updates every 30 minutes or upon resolution.

Thank you for your patience as we continue to investigate this issue. Currently, we do not yet have a time to resolution. We will continue to provide updates every 30 minutes as we work to resolve this issue as quickly as possible.

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.

We have escalated this issue with the third-party provider to mitigate the issue.  Currently, we do not yet have a time to resolution. We will provide further updates in 30 minutes or upon resolution.

We are continuing to work closely with our vendor to resolve the access issue affecting the EU2 region, which remains our highest priority. Through our investigation, we have identified connectivity issues to the EU-CENTRAL-1 region as the underlying cause. Beginning at 7:33 PM PDT on August 14, our vendor began experiencing increased packet loss impacting connectivity for customers in the EU-CENTRAL-1 region. The affected location has been identified as Equinix, Frankfurt. While progress has been made, connections to this location remain impaired. We continue to prioritise resolution steps with our vendor. However, full recovery is expected to be multiple hours away. We will provide an update every 60 minutes as we work to restore service as quickly as possible, or sooner if additional information becomes available.

We are continuing to work with our vendor to resolve the access issue affecting the eu2 region as our top priority. We are also exploring multiple paths to restore service as quickly as possible. Collaboration with our vendor is ongoing; however, full recovery is expected to be multiple hours away. We will provide an update every 60 minutes as we work to restore service as quickly as possible, or sooner if additional information becomes available

We have completed the re-route of traffic out of the impacted area and are now in a monitoring phase. A further update will be provided in 30 minutes, or sooner if additional information becomes available.

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.

On August 15, 2026, from 03:16 UTC to 08:23 UTC, customers in our eu2: Data Center - Germany region experienced a service interruption that prevented access to the Anaplan platform. During this time, a local infrastructure failure affected the region's ability to connect to external services, resulting in a loss of platform availability.  **Root cause**  The disruption was caused by an environmental failure at our vendor's third-party facility in Frankfurt, Germany. A leak in the facility's cooling system led to localized overheating, which triggered automatic safety shutdowns of critical network equipment. Escaped water also damaged localized power distribution systems within the facility, disabling network devices. This combined power and cooling failure prevented the system from resolving external addresses and completing outbound requests in this region.  **Recovery**  Because the facility's environmental conditions made the area unsafe to enter, our vendor was delayed in assessing and repairing the affected equipment. As a result, our engineering team deployed an emergency change to reroute traffic through an alternate regional network path, bypassing the impaired facility and region. This successfully restored full external connectivity and name resolution, and platform access was fully restored by 08:23 UTC.  The facility’s operator and our vendor continued recovery work over the following days, with full restoration confirmed by August 18. We maintained our emergency routing throughout that period to keep service stable while the vendor completed repairs.  **Corrective and preventative actions**  We are implementing the following measures to strengthen resilience and reduce the risk of a similar disruption:  * We are adding a layer that automatically redirects traffic to alternate geographic locations during a localized outage, with no manual intervention required.  * We are enabling cached records to continue serving traffic when the path to external resolvers is unavailable, so a connectivity loss to external services no longer prevents platform access when a regional event occurs.  * We are working with our third-party facility and network providers to review their standards for critical power and cooling systems and ensure stronger preventative safeguards are in place.  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 team.

We are currently investigating an issue impacting customers’ ability to access the Anaplan Platform. We are working to resolve this issue as quickly as possible and will provide updates every 30 minutes or upon resolution.

We are currently investigating an issue impacting customers’ ability to access the Anaplan Platform. Thank you for your patience as we continue to investigate this issue. Currently, we do not yet have a time to resolution. We will continue to provide updates every 30 minutes as we work to resolve this issue as quickly as possible.

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.

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.

On July 29, 2026, between 10:57 UTC and 11:53 UTC, customers in our us1: Data Center - US East, us2: Data Center - US West, eu1: Data Center - Netherlands, eu2: Data Center - Germany, eu4: Cloud - Europe, us5: Cloud - US East, us7: Cloud - US, and ap1: Cloud - Japan regions experienced degraded performance. This resulted in delayed model and workspace access, slow page load times, and slower logins across the platform, as well as delayed execution of CloudWorks™ integrations. All other regions were unaffected during this time.  **Root Cause**  The incident was triggered by an automated security software update deployed across our platform servers. This simultaneous update caused an unexpected, short-lived spike in storage activity that temporarily exceeded the storage systems' processing capacity. The resulting latency disrupted communication between internal metadata services and core system servers, causing the service connection pools to become unresponsive and preventing them from automatically recovering.  **Recovery**  Our engineering team identified the issue and took immediate action. We performed rolling restarts of the affected metadata services to clear the unresponsive connection pools and stabilize the systems. By 11:30 UTC, affected systems had recovered. Following this, the CloudWorks™ scheduler was restarted to process and clear the backlog of integration tasks. The issue was fully resolved by 11:53 UTC.  **Corrective & Preventative Actions**  We are implementing the following actions to prevent recurrence:  * We are implementing enhanced storage performance tiers and traffic-prioritization controls to isolate key platform workloads from other background system activities.  * We are updating our internal service connection frameworks to automatically detect and gracefully recover from unexpected system connection interruptions.  * We are refining our security software deployment processes to stagger rollouts and limit simultaneous resource utilization.  * We are enhancing our synthetic monitoring dashboards to improve visibility of regional service performance deviations.  * We are conducting rigorous connection-recovery and system testing in our lower environments to validate application resilience under loaded states.  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.

We are currently investigating an issue resulting in some customers not being able to load models. We are working to resolve this issue as quickly as possible and will provide updates every 30 minutes or upon resolution.

Thank you for your patience as we continue to investigate this issue. Currently, we do not yet have a time to resolution. We will continue to provide updates every 30 minutes as we work to resolve this issue as quickly as possible.

Thank you for your patience as we continue to investigate this issue. Our support teams continue to investigate this issue, however we do not yet have a time to resolution. We will continue to provide updates every 30 minutes as we work to resolve this issue as quickly as possible.

Thank you for your patience as we continue to investigate this issue. This issue has been escalated to our senior engineering and leadership teams, who are actively investigating the situation and evaluating all necessary next steps to restore full operations. While we do not have specific technical details to share at this moment, please be reassured that resolving this incident is our highest priority. We sincerely apologize for the disruption and appreciate your patience. We will continue to provide updates every 30 minutes, or sooner if new details emerge, as we work to resolve this issue as quickly as possible.

We have identified potential remediation paths and are currently progressing active mitigation activities to restore service stability. While we do not have a firm Estimated Time to Recovery (ETA) to share at this stage, please be assured that our primary focus remains on safely and swiftly resolving this issue. We are closely monitoring the impact of our current mitigation steps. We apologize for the ongoing inconvenience. Our next update will be published in 30 minutes, or sooner as key milestones are achieved.

We understand the disruption this has caused and want to assure you that resolving this as quickly as possible remains our top priority. Our team is actively engaged in remediation, and the measures put in place are showing meaningful progress toward full service restoration. We recognize your patience throughout this process and do not take it for granted. We are monitoring our systems closely and will provide a further update within 30 minutes, or sooner should there be a significant development to share.

We are continuing to execute and validate our remediation plans. We are seeing sustained progress as recovery efforts move forward systematically. To ensure a safe and complete recovery, we are progressing carefully and are not yet in a position to share specific technical milestones. Please be assured that our entire response team remains fully dedicated to resolving this incident. Thank you for your continued patience. Our next update will be published in 30 minutes, or sooner as soon as we have further progress to report.

We are currently conducting emergency maintenance on the Canada region. Access to the platform has been temporarily restricted while our team works to complete remediation and validate full service restoration. We are actively monitoring the environment and making progress. We appreciate your patience and understand the impact this has on your work. Further updates will be provided every 30 minutes, or sooner if there is a significant development to share. We apologize for the inconvenience and remain committed to restoring service as quickly as possible.

Our team remains actively engaged in remediation efforts. Work is progressing across multiple workstreams and we continue to make forward movement toward full service restoration. We will provide a further update within 30 minutes, or sooner if there is a meaningful development to share. We appreciate your continued patience.

We are currently performing emergency maintenance on the Canada region. Our team is actively engaged in remediation efforts in coordination with our vendor, and the issue has been contained. Customer access to the Canada environment remains temporarily restricted while we complete validation and restoration efforts. We appreciate your patience and will provide a further update within 1 hour, or sooner if there is a significant development to share.

Our team continues to work through emergency maintenance on the Canada region in close coordination with our vendor. The issue has been contained and restoration efforts are actively underway. Access to the Canada environment remains temporarily restricted as we complete the necessary validation steps prior to service restoration. We recognize the impact this has on your work and appreciate your continued patience. Our next update will be provided within 1 hour, or sooner should a significant development occur.

Our team continues to work through emergency maintenance on the Canada region in close coordination with our vendor. The issue has been contained, however, due to the complexity and scope of the recovery process, we expect restoration to be an extended effort that will take several  hours to complete. Access to the Canada environment will remain restricted for the duration of the recovery. We recognize the significant impact this has on your work and sincerely appreciate your patience. Our next update will be provided within one hour, or sooner should a significant development occur.

Our team and vendor partners continue to make progress through the complex recovery process for the Canada region during this emergency maintenance. We are systematically executing our recovery protocols and validating system integrity at each stage. As noted previously, due to the scope of this effort, this remains an extended recovery process, and access to the Canada environment will continue to be restricted as we work toward a safe and complete service restoration. We remain fully aware of the impact this service interruption has on your operations and are doing everything possible to expedite these steps. Our next update will be provided within one hour, or sooner should a significant development occur.

Our engineering and vendor teams continue to actively execute the recovery steps for the Canada region under emergency maintenance. There are no new technical details or changes to share at this time, as our focus remains entirely on the systematic and safe restoration of services. Access to the Canada environment remains restricted while these recovery activities are underway. We appreciate your continued patience and partnership as we work through this extended effort. Our next update will be provided within one hour, or sooner should a significant development occur.

Our engineering teams and vendor partners continue to progress through the recovery steps for the Canada region under emergency maintenance. We are making positive headways and are getting closer to re-enabling the region for the majority of workspaces. Access to the Canada environment remains temporarily restricted while we execute and complete these crucial final validation steps to ensure service stability. We sincerely appreciate your patience and partnership as we enter these final stages of the recovery process. Our next update will be provided within one hour, or sooner should a significant development occur.

We are continuing to systematically execute our recovery steps for the Canada region under emergency maintenance. Our engineering teams and vendor partners remain focused on the final validation phases, and we continue to get closer to enabling the region for the majority of customers. Access to the Canada environment remains restricted for the time being to ensure we maintain system stability during these critical final steps. We are immensely grateful for your ongoing patience and partnership. Our next update will be provided within one hour, or sooner should a significant development occur.

Our engineering teams and vendor partners continue to systematically progress through the final stages of validation for the Canada region under emergency maintenance. We remain focused on verifying system stability, which keeps us on a steady path toward enabling the region for the majority of customers. Access to the Canada environment remains restricted for the time being to ensure these critical safety and stability checks are fully completed. We are incredibly grateful for your continued patience and partnership as we complete this extended effort. Our next update will be provided within one hour, or sooner should a significant development occur.

Our engineering and vendor teams are entering the final preparation phases of our recovery plan for the Canada region under emergency maintenance. As we prepare to restore access, our plan is to enable all services in the region with the exception of Bring Your Own Key (BYOK) configurations. Additionally, a small number of workspaces will remain disabled initially upon general service restoration. For these specific remaining workspaces, we will be executing a highly controlled, systematic restoration plan to recover each environment individually to guarantee complete stability and data integrity. Access to the Canada environment remains restricted at this time while we complete these final pre-enablement validation steps. We recognize the ongoing impact this has on your operations and sincerely appreciate your continued patience. Our next update will be provided within one hour, or sooner should a significant development occur.

We're currently restoring the platform . Our engineering and vendor teams are actively working to restore services as quickly as possible. As part of our recovery plan, we will be restoring all services in the region with the exception of Bring Your Own Key (BYOK) configurations. Additionally, a small number of workspaces will remain temporarily disabled upon initial service restoration. For these specific workspaces, we will be executing a highly controlled, systematic restoration process to recover each environment individually and guarantee complete stability and data integrity. Access to the Canada environment remains restricted at this time We recognize the significant impact this has on your operations and sincerely appreciate your continued patience. Our next update will be provided within one hour, or sooner should a significant development occur.

Our Engineering team is actively working to restore platform stability across the Canada (CA1) region through a carefully phased recovery. We will initially restore general services, with the exception of Bring Your Own Key (BYOK) configurations. To guarantee a stable and secure environment, a small number of workspaces may remain temporarily disabled while we perform controlled restorations. Overall access to the Canada environment remains restricted at this time as we complete these critical restoration measures. We deeply recognize the significant impact this situation has on your operations and sincerely appreciate your continued patience as we work through these safety measures. Our next update will be provided within one hour, or sooner should a significant development occur.

We have enabled general customer access to the Canada region. All services within the region are now being brought online, with the exception of Bring Your Own Key (BYOK) configurations. Additionally, a small, specific number of customer workspaces will remain temporarily disabled. For these remaining workspaces, our engineering teams are executing a highly controlled, systematic restoration plan to safely recover each environment individually to ensure complete data integrity. We sincerely appreciate your ongoing patience and partnership as we execute these final, precise recovery steps. Our next update will be provided within one hour, or sooner should a significant development occur.

We sincerely apologize for the disruption this has caused and deeply appreciate your patience. General customer access to the Canada region has been restored, and services are coming back online. Bring Your Own Key configurations and a small number of workspaces remain temporarily offline while we complete careful, individualized restoration to ensure full data integrity. We will provide a further update within one hour, or sooner if there is a significant development to share.

General customer access to the Canada region has been restored. Workspaces using Bring Your Own Key (BYOK) encryption will remain temporarily offline while we complete individualized restoration for each affected workspace. We will provide a further update on BYOK restoration status at 09:00 UTC on July 26, 2026. We apologize for the disruption and thank you for your patience.

We are writing to provide a high-level update on the service disruption affecting Canada (CA1) region access that began on Friday, 24 July at 20:35 UTC. Through the dedicated coordination of our engineering teams and vendor partners, general access to the Canada region was successfully re-enabled on Saturday, 25 July at 17:24 UTC. The vast majority of our customers can now access their workspaces and models normally. Current Status and Next Steps While general region access has been fully restored, workspaces utilizing Bring Your Own Key (BYOK) encryption remain temporarily offline. Our primary focus is currently on successfully reproducing the technical disruption within a controlled environment. The insights gained from this reproduction phase are critical, as they will directly influence and determine the safest, most effective recovery path for the remaining BYOK workspaces. Proceeding with this systematic investigation ensures we maintain the highest standards of system stability and data integrity. We expect to provide our next targeted update regarding BYOK workspace restoration by 11:00 UTC. We sincerely apologize for the disruption and the impact this has had on your operations. Our Support teams remain fully available to assist you with any questions or immediate needs.

We are writing to provide a high-level update on the service disruption affecting Canada (CA1) region access that began on Friday, 24 July at 20:35 UTC. Through the dedicated coordination of our engineering teams and vendor partners, general access to the Canada region was successfully re-enabled on Saturday, 25 July at 17:24 UTC. The vast majority of our customers can now access their workspaces and models normally. Current Status and Next Steps While general region access has been fully restored, workspaces utilizing Bring Your Own Key (BYOK) encryption remain temporarily offline. Our primary focus is currently on successfully reproducing the technical disruption within a controlled environment. The insights gained from this reproduction phase are critical, as they will directly influence and determine the safest, most effective recovery path for the remaining BYOK workspaces. Proceeding with this systematic investigation ensures we maintain the highest standards of system stability and data integrity. We expect to provide our next targeted update regarding BYOK workspace restoration by 13:00 UTC. We sincerely apologize for the disruption and the impact this has had on your operations. Our Support teams remain fully available to assist you with any questions or immediate needs.

While general access to the Canada (CA1) region has been fully restored as of Saturday, 25 July at 17:24 UTC, workspaces utilizing Bring Your Own Key (BYOK) encryption remain temporarily offline. Our primary focus to reproduce the disruption within a controlled environment is still ongoing with our vendor. This is a critical phase, as it will directly influence and determine the safest, most effective recovery path for the remaining BYOK workspaces while ensuring system stability and data integrity. We expect to provide our next targeted update regarding BYOK workspace restoration by 15:00 UTC. We sincerely apologize for the disruption and the impact this has had on your operations. Our Support teams remain fully available to assist you with any questions or immediate needs.

General access to the CA1 region remains fully restored for the majority of customers. Workspaces utilizing Bring Your Own Key (BYOK) encryption remain temporarily offline while we finalise safe recovery, validation, and root-cause analysis. We are actively collaborating with our third-party encryption partner to understand the cause and potential fix.

General access to the CA1 region continues to remain fully restored for the majority of customers. Workspaces utilizing Bring Your Own Key (BYOK) encryption remain temporarily offline while we finalize safe recovery, validation, and root-cause analysis. We are actively collaborating with our third-party encryption partner to understand the cause and potential fix.

General access to the Canada (CA1) region remains fully restored. However, workspaces utilizing Bring Your Own Key (BYOK) encryption will remain temporarily offline. We will provide a further update on the BYOK restoration status at 10:00 UTC on July 27, 2026. We apologize for this disruption and thank you for your continued patience.

We are writing to provide a status update on the ongoing recovery efforts for Bring Your Own Key (BYOK) workspaces within the Canada (CA1) region. General services for the region remain fully restored and are operating normally. Current Investigation Status Our engineering and vendor teams are continuing their deep-dive investigation into the root cause of the recent service disruption. We are currently focusing our efforts on replicating the issue within a dedicated, non-production environment. This controlled replication is a critical step, as the technical findings will directly allow us to identify and validate the most effective recovery path for the remaining BYOK workspaces. By ensuring we thoroughly understand the behavior of the system under these specific conditions in non-production first, we can guarantee the absolute safety, stability, and integrity of your data during the final restoration phase. We sincerely appreciate your patience and partnership as we execute these meticulous validation steps. Our next update will be provided within two hours, or sooner should a significant milestone be reached.

We are continuing our active investigation and recovery planning for Bring Your Own Key (BYOK) workspaces within the Canada (CA1) region. General services for the region remain fully restored and continue to operate normally. Our engineering teams and vendor partners are continuing to focus their efforts on replicating the disruption within a controlled, non-production environment. Replicating the scenario under these safe conditions remains our highest priority, as it is the critical step that will allow us to identify and confirm the most effective recovery path for the remaining BYOK workspaces. We are proceeding methodically to ensure that the restoration process, once initiated, preserves system stability and data integrity. We appreciate your continued patience and partnership while this deep-dive technical validation continues. Our next update will be provided within two hours, or sooner should we have new progress to share.

We are continuing our active efforts to restore Bring Your Own Key (BYOK) workspaces in the Canada (CA1) region. General services across the region remain fully restored and are operating normally. To expedite the resolution, our engineering teams and vendor partners are pursuing multiple lines of investigation concurrently. This multi-faceted approach is critical to guaranteeing that our restoration plan is fully validated and preserves the integrity of your environment. We sincerely appreciate your patience and partnership as we execute these concurrent efforts. Our next update will be provided within two hours, or sooner should we achieve a significant breakthrough.

We are continuing our active efforts to restore Bring Your Own Key (BYOK) workspaces in the Canada (CA1) region. General services across the region remain fully restored and are operating normally. Our engineering teams and vendor partners are concurrently pursuing multiple lines of investigation. This parallel approach is being executed deliberately to validate and finalize the most effective recovery path for the remaining BYOK workspaces, ensuring we restore services safely and with the highest level of stability. We appreciate your continued patience as our teams work through these necessary steps. Our next update will be provided within two hours, or sooner should we achieve a significant breakthrough.

While general services across the Canada (CA1) region remain fully restored and operating normally, we are continuing our dedicated focus on the recovery of Bring Your Own Key (BYOK) workspaces. Our teams are systematically moving forward with multiple parallel workstreams. Executing these efforts concurrently allows us to thoroughly analyze all outcomes, ensuring we validate and implement the most effective recovery path for the remaining BYOK workspaces, ensuring we restore services safely and with the highest level of stability. We appreciate your ongoing partnership and patience as we execute these critical recovery steps. We will provide a further update on BYOK restoration status at 09:00 UTC (10:00 BST) on July 28, 2026.

General services in the Canada (CA1) region remain fully restored and operating normally. For the remaining Bring Your Own Key (BYOK) workspaces, our teams continue to execute multiple parallel workstreams. This concurrent approach is being carried out deliberately to validate the most effective recovery path for the remaining BYOK workspaces while ensuring absolute system stability. We appreciate your ongoing patience. Our next update will be provided within two hours, or sooner should we reach a significant milestone.

General services within the Canada (CA1) region continue to operate normally and remain fully stable. Our engineering and vendor teams are continuing to progress through multiple concurrent workstreams to address the remaining Bring Your Own Key (BYOK) workspaces. This parallel approach remains our active focus, allowing us to systematically validate and implement the most effective recovery path for the remaining BYOK workspaces with the highest level of safety. We appreciate your ongoing patience and support. Our next update will be provided within two hours, or sooner should we reach a significant milestone.

General services within the Canada (CA1) region remain fully restored, stable, and continue to operate normally. Our engineering teams and vendor partners are continuing to move forward with multiple concurrent workstreams to address the remaining Bring Your Own Key (BYOK) workspaces. This parallel strategy remains our active focus, allowing us to systematically validate and implement the most effective recovery path for the remaining BYOK workspaces. We sincerely appreciate your ongoing patience as we work through these deliberate steps. Our next update will be provided within two hours, or sooner should we reach a significant milestone.

General services within the Canada (CA1) region remain fully restored, stable, and continue to operate normally. Our engineering teams and vendor partners are actively maintaining their focus on the remaining Bring Your Own Key (BYOK) workspaces through multiple parallel workstreams. We appreciate your ongoing patience and partnership as we complete these critical validation phases. Our next update will be provided within two hours, or sooner should we reach a significant milestone.

While general services across the Canada (CA1) region remain fully restored and operating normally, we are continuing our dedicated focus on the recovery of Bring Your Own Key (BYOK) workspaces. Our teams are systematically moving forward with multiple parallel workstreams. Executing these efforts concurrently allows us to thoroughly analyze all outcomes, ensuring we validate and implement the most effective recovery path for the remaining BYOK workspaces, ensuring we restore services safely and with the highest level of stability. We appreciate your ongoing partnership and patience as we execute these critical recovery steps. We will provide a further update on BYOK restoration status at 09:00 UTC (10:00 BST) on July 29, 2026.

While general services across the Canada (CA1) region remain fully restored and operating normally, we are continuing our dedicated focus on the recovery of Bring Your Own Key (BYOK) workspaces. Our teams are continuing to progress systematically through multiple parallel workstreams. Executing these efforts concurrently allows us to thoroughly analyze all technical outcomes, ensuring we validate and implement the safest and most stable recovery path for the remaining BYOK workspaces. We appreciate your ongoing partnership and patience as we execute these critical recovery steps. Our next update will be provided within two hours, or sooner should we reach a significant milestone.

While general services across the Canada (CA1) region remain fully restored and operating normally, we are continuing our dedicated focus on the recovery of Bring Your Own Key (BYOK) workspaces. Our teams are still continuing to progress systematically, through multiple parallel workstreams. Executing these efforts concurrently allows us to thoroughly analyze all technical outcomes, ensuring we validate and implement the safest and most stable recovery path for the remaining BYOK workspaces. We appreciate your ongoing partnership and patience as we execute these critical recovery steps. Our next update will be provided within two hours, or sooner should we reach a significant milestone.

General services across the Canada (CA1) region remain fully restored and continue to operate normally. Our engineering and operations teams are maintaining their dedicated, concentrated focus on recovering the remaining Bring Your Own Key (BYOK) workspaces. To ensure the safest possible restoration, we are actively advancing multiple parallel recovery workstreams. Running these efforts concurrently allows us to rigorously analyze technical outcomes in real-time, ensuring we validate and implement the most stable and secure path forward for the remaining BYOK workspaces. We sincerely appreciate your ongoing patience and partnership as we systematically execute these critical recovery steps. Our next update will be provided within two hours, or sooner should we reach a significant milestone.

While general services across the Canada (CA1) region remain fully restored and operating normally, we are continuing our dedicated focus on the recovery of Bring Your Own Key (BYOK) workspaces. Our teams are systematically moving forward with multiple parallel workstreams. Executing these efforts concurrently allows us to thoroughly analyze all outcomes, ensuring we validate and implement the most effective recovery path for the remaining BYOK workspaces, ensuring we restore services safely and with the highest level of stability. We appreciate your ongoing partnership and patience as we execute these critical recovery steps. We will provide a further update on BYOK restoration status at 09:00 UTC (10:00 BST) on July 30, 2026.

While general services across the Canada (CA1) region continue to operate normally with full stability, our technical teams maintain their dedicated focus on the recovery of the remaining Bring Your Own Key (BYOK) workspaces. We are continuing to advance multiple parallel workstreams to validate and execute the safest possible restoration path. Running these efforts concurrently allows us to thoroughly analyze all technical outcomes, ensuring we restore services with the highest level of security and stability for all outstanding BYOK workspaces. We appreciate your continued patience and partnership as we systematically work through these critical recovery steps. We will provide a further update on the BYOK restoration progress in two hours.

While general services across the Canada (CA1) region continue to operate normally with full stability, our technical teams maintain their dedicated focus on the recovery of the remaining Bring Your Own Key (BYOK) workspaces. We are continuing to advance multiple parallel workstreams to validate and execute the safest possible restoration path. Running these efforts concurrently allows us to thoroughly analyze all technical outcomes, ensuring we restore services with the highest level of security and stability for all outstanding BYOK workspaces. We appreciate your continued patience and partnership as we systematically work through these critical recovery steps. We will provide a further update on BYOK restoration status at 09:00 UTC (10:00 BST) on July 31, 2026, or sooner should we reach a significant milestone.

While general services across the Canada (CA1) region continue to operate normally with full stability, our technical teams maintain their dedicated focus on the recovery of the remaining Bring Your Own Key (BYOK) workspaces. We are continuing to advance multiple parallel workstreams to validate and execute the safest possible restoration path. Running these efforts concurrently allows us to thoroughly analyze all technical outcomes, ensuring we restore services with the highest level of security and stability for all outstanding BYOK workspaces. We appreciate your continued patience and partnership as we systematically work through these critical recovery steps. We will provide a further update on BYOK restoration status at 09:00 UTC (10:00 BST) on August 3rd, 2026, or sooner should we reach a significant milestone.

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.

**Summary**  On July 24, 2026, at 20:22 UTC, our engineering team began investigating an issue affecting customers in our ca1: Cloud — Canada region. Customers with affected workspaces were unable to open their models. As a precaution, while we validated the scope of the issue, we restricted access to the region behind a maintenance page at 02:18 UTC on July 25. General access to CA1 was restored at 17:24 UTC on July 25. Bring Your Own Key \(BYOK\) workspaces remained offline for additional safeguards, and were re-enabled progressively as those safeguards were validated. The incident was fully resolved on July 31, 2026, at 13:47 UTC.  **Root cause**  The disruption was caused by a defect in a third-party component used within our BYOK service. The defect only surfaced under a very specific combination of events occurring in a particular order on the same host. When a BYOK workspace was unloaded, the component failed tofully clear one of its local resources, leaving behind a stale reference. When a BYOK workspace was subsequently loaded onto the same host, the component attempted to clean up that stale reference before proceeding. During this step, it incorrectly executed a removal that extended beyond the stale reference and deleted files that were still in active use.   The affected files were captured in our regular backups. Once our engineering team identified the source of the activity, isolated it, and applied protective controls to stop any further impact, restoration became a controlled process of returning each affected file to its most recent backup.  **Recovery**  Our engineering team identified the issue and isolated it at its source, then worked systematically to restore the affected files. This allowed us to bring non-BYOK workspaces back online in a controlled sequence, and general access to CA1 was restored at 17:24 UTC on July 25.  We deliberately kept BYOK workspaces offline while our team worked with the third-party vendor to reproduce the trigger in a controlled, non-production environment. This reproduction gave us the diagnostic evidence the vendor needed to build a fix and to confirm the exact cause. It also allowed us to develop and validate our own temporary safeguards — targeted changes to how BYOK workspaces are scheduled — that eliminated the specific combination of conditions required to trigger the defect. These safeguards act as compensating controls to bring BYOK workspaces back online while the third party completes the permanent fix to the underlying component. We re-enabled BYOK workspaces once those safeguards were validated, ensuring the trigger conditions couldn't recur. The incident was fully resolved on July 31, 2026, at 13:47 UTC.  **Corrective and preventative actions**  Our corrective actions follow two complementary tracks. The first removes the specific combination of conditions required to trigger the defect, using controls we have developed and deployed ourselves as compensating safeguards. The second is the permanent fix to the underlying component itself, which the third party is delivering. Together, these tracks address both the trigger and the defect, so that neither can produce another incident of this kind. We are implementing the following actions to prevent recurrence:  * We have deployed changes that prevent the specific combination of conditions required to trigger the defect. This is a temporary but effective control that removes the trigger today, ahead of the permanent fix.  * We are working with the third party to deploy their validated fix. This removes the defect at its source and closes the underlying cause of this incident.  * We are strengthening how we validate BYOK third-party components in non-production before they reach production, including reproducing a wider range of workspace lifecycle scenarios and event sequences. This gives us stronger assurance to surface these types of issues in non-production and are addressed before they can affect customers.  * We have deployed dedicated alerting on the specific event pattern that triggered this incident and are actively reviewing additional file-level alerting. These alerts provide an additional safety net and earlier warning, enabling faster preventative action before customers are affected.  **Closing**  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.

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.

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.

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.

On July 21, 2026, between 14:15 UTC and 14:50 UTC, the us5: Cloud - US East region experienced a disruption to scheduled CloudWorks™ integrations. During this window, automated workflows could not be triggered, and users may have experienced difficulties accessing integration services.  **Root cause**   The issue was triggered by a brief interruption in the underlying storage systems following a system release rollback. This led to a loss of connectivity within the integration scheduler system, which prevented scheduled tasks from being successfully queued or triggered.  **Recovery**   Our engineering team identified the issue and took immediate action. We verified system connectivity as the underlying services recovered automatically, and we executed test integrations to validate scheduled workflows. These validation checks confirmed that all scheduling mechanisms had safely resumed normal operations without requiring a system restart. By 14:50 UTC, the issue was fully resolved.  **Corrective and preventative actions**  * We are conducting a deep-dive investigation into system performance during rollback operations to ensure stability under high-load conditions.  * We are implementing enhanced health checks for the integration scheduler to ensure it reaches a "ready" state before traffic is routed during rollbacks.  * We are updating our deployment processes to include automated validation of task queue depth immediately following any regional update or rollback.  * We are updating our resource sizing documentation for this service with recommended request/limit values to ensure sufficient capacity for deployment and rollback operations.  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](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.

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.

We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon.

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.

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.

On July 14, 2026, at 19:55 UTC, customers in our us7: Cloud - US West region experienced delays and failures in CloudWorks™ integration job processing. Integration jobs that were scheduled to run in this region did not complete as expected, resulting in a processing backlog that was cleared once service was fully restored.  Root cause   A back-end component supporting the CloudWorks™ service temporarily exhausted its available memory, leading to a brief connectivity disruption. Although the database recovered immediately, the CloudWorks™ processing components retained inactive connections and were unable to automatically reconnect. This prevented integration jobs from completing and caused a queue of scheduled tasks to accumulate.  Recovery   Our engineering team identified the issue and took immediate action. The team restarted the CloudWorks™ processing components to clear all stale and inactive connections. To quickly clear the backlog of pending integration jobs, we temporarily increased the processing capacity of the components. After verifying that integration jobs were completed normally and the backlog had been fully processed, we returned the system to its original capacity. By 21:14 UTC, the issue was fully resolved.  Corrective and preventative actions   We are implementing the following actions to prevent recurrence:   * **Memory allocation increase:** We are increasing the memory allocation for the back-end component in us7. This reduces the likelihood of a similar memory pressure event occurring in the future.  * **Background process optimization:** We've disabled certain background metric collection processes that were contributing unnecessary load to the back-end component. This further lowers the risk of memory pressure building over time.  * **Resilience testing:** Our engineering teams are running controlled tests in non-production environments to better understand how the CloudWorks™ service behaves during brief connectivity disruptions. This work will help us improve the service's ability to recover automatically — without requiring manual intervention — should a similar event occur in the future.  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 [Support](https://support.anaplan.com/).

We are currently investigating an issue impacting customers’ ability to access the Anaplan Platform. We are working to resolve this issue as quickly as possible and will provide updates every 30 minutes or upon resolution.

Thank you for your patience as we continue to investigate this issue. We are currently experiencing a critical service disruption causing full unavailability within the affected regions. Users attempting to access services in these regions will encounter connection timeouts and failure to load resources. Currently, we do not yet have a time to resolution. We will continue to provide updates every 30 minutes as we work to resolve this issue as quickly as possible.

We're investigating an issue affecting login and platform access for customers in our ME1 and EU5 regions. Initial investigation points to a disruption in the authentication path for those regions. Resolving this is our highest priority, and our engineering teams are actively working to restore normal operations. We don't have an ETA yet. We'll provide another update within 30 minutes, or sooner if we have significant new information.

Our investigation into the login and platform access issue affecting ME1 and EU5 regions is ongoing. We have engaged our vendor for additional support as we work to identify and resolve the root cause. Resolving this remains our highest priority. No ETA yet. We'll provide our next update within 30 minutes, or sooner if we have significant new information.

Our investigation into the login and platform access issue affecting ME1 and EU5 regions is ongoing. Our engineering teams have narrowed the investigation and are actively pursuing several lines of enquiry, in collaboration with our infrastructure partner. Restoring service remains our highest priority. No ETA yet. We'll provide our next update within 30 minutes, or sooner if we have significant new information.

We are investigating an issue affecting login and platform access for customers in our ME1 and EU5 regions. The issue began at approximately 23:52 UTC on 1 July 2026. In coordination with our infrastucture partner, we have successfully narrowed down the potential causes and are currently focusing our engineering efforts on isolating the issue to initiate targeted mitigation. Our team remains fully dedicated to resolving this issue as quickly as possible. We will provide our next update within 30 minutes, or sooner if we have significant new information.

We are continuing to investigate the issue affecting login and platform access for customers in our ME1 and EU5 regions. We have identified the potential cause and are actively progressing mitigation steps to address the issue and restore full service. We will continue to provide updates as remediation advances. We will provide our next update within 30 minutes, or sooner if we have significant new information.

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.

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.

On July 1, 2026, at approximately 23:52 UTC, our monitoring systems detected a service disruption impacting customers in the me1: Cloud – Middle East and eu5: Cloud — Europe regions. During this time, affected customers were unable to log in to the platform. Service was restored at 03:21 UTC **Root cause**  The disruption originated from a planned network configuration change to our internal name resolution infrastructure. A misconfiguration was introduced as part of the change that left an underlying routing conflict in place. This caused return traffic for internal name lookups to take an incorrect path during routine network activity. As a result, internal name resolution began failing for the two affected regions. This prevented the authentication flow from completing and stopped customers from logging in.  **Recovery**  On detection at 23:52 UTC, our engineering team and our infrastructure partner began investigating in parallel. Because internal name resolution issues can present themselves in several diverse ways, the team worked through multiple lines of inquiry before isolating the specific routing conflict responsible. Once identified, we rolled back the recent change to restore the previous known-good routing configuration. Connectivity recovered progressively as the rollback propagated, and by 03:21 UTC, authentication was fully restored for both affected regions.   **Corrective and preventative actions**  We are implementing the following actions to prevent a recurrence:  * We are adding pre-change validation that specifically detects the class of routing conflict responsible for this incident. This closes off the underlying configuration issue before any similar change can reach the environment.  * We are re-architecting the affected routing setup to prevent this class of misconfiguration from being introduced again. This removes the underlying issue at the source.  * We are improving our monitoring for the internal name resolution paths between our cloud environments. This shortens the time to detect and resolve this class of issue. **Closing**  We apologize for the impact this disruption has had on your operations. The corrective actions above are focused on preventing a recurrence of any similar issue in the future. If you have questions or concerns, please contact [Support](https://support.anaplan.com/).

We are currently investigating an issue resulting in some customers not being able to load models. We are working to resolve this issue as quickly as possible and will provide updates every 30 minutes or upon resolution.

Thank you for your patience as we continue to investigate this issue. Currently, we do not yet have a time to resolution. We will continue to provide updates every 30 minutes as we work to resolve this issue as quickly as possible.

We are actively investigating a service disruption currently affecting customers' ability to open Models. This issue is also affecting CloudWorks Integrations. Our engineering teams are prioritizing this issue and evaluating immediate mitigation steps to restore full service as quickly and safely as possible. We do not yet have an estimated time to resolution, but will provide progress updates every 30 minutes or sooner.

We are progressing with active mitigation steps to resolve the disruption affecting Model opening and CloudWorks integrations. Initial reports indicate positive outcomes from these activities. Our engineering teams are closely monitoring system stability while we complete the remaining mitigation steps to ensure a full and durable recovery. We will continue to provide updates every 30 minutes as we work to bring all systems back to standard operations.

We are currently proceeding with the final remediation steps while continuing our investigation into the root cause. Customers should now be able to open models, though some may still encounter temporary delays; however, CloudWorks integrations are not yet completing. We are monitoring these recovery steps closely to ensure full system stability and will continue to provide updates every 30 minutes.

We are pleased to report that all issues affecting model loading have been fully resolved, and normal access has been restored. Additionally, CloudWorks integrations are running again, and our teams are currently processing the accumulated backlog of queued jobs. We are monitoring the queue progression closely to ensure all delayed integrations complete successfully. We will provide our next update in 30 minutes or once the backlog is fully cleared.

Our teams confirm that the CloudWorks integration backlog is actively processing and recovering. Access to opening models remains fully restored and stable. We are continuing to monitor the integration queues closely as jobs complete, and we will provide our next status update in 30 minutes.

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.

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.

On June 22, 2026, at 07:20 UTC, we became aware of an issue affecting our us7: Cloud – US region. Customers experienced difficulties loading models, with impact beginning at approximately 05:12 UTC. CloudWorks™ integrations in the region were also unable to run during this period. Customers with active workspace sessions weren't affected. However, any workspace that was unloaded during this time couldn't be loaded until service was restored. Full service was restored at 10:21 UTC.  **Root cause**  A component that manages active workspace resources in the us7 region encountered an unexpected fault and restarted. On restart, the component entered a state where it appeared to be operating normally but couldn't process new workspace requests. Our systems normally recover automatically from this kind of state, but in this case the fault wasn't detected by our recovery processes. We intervened manually and performed a corrective restart of the component, which restored normal operation.  **Recovery**  We conducted a thorough investigation of the platform and identified the source of the issue. We performed a targeted reset of the resource scheduling services to clear the pending connections and restore normal communication. Once communication was re-established at 08:48 UTC, the platform began successfully assigning resources and loading models.  To handle the accumulated backlog of scheduled integrations, we scaled up the processing capacity for CloudWorks™. By 10:21 UTC, the backlog had finished processing, and the issue was fully resolved.  **Corrective and preventative actions**  We're implementing the following actions to prevent recurrence:  * We're deploying enhanced automated monitoring specifically designed to detect the condition seen in this incident, where a component appears operational but isn't processing requests. This closes the detection gap that extended the impact of this issue.  * We're developing automated self-healing for the resource scheduling component, so that a corrective restart can be performed automatically without engineering intervention. This directly addresses the failure mode that caused this incident.  * We're streamlining our scaling procedures for CloudWorks™, so that integration processing capacity can be expanded more rapidly during recovery. This shortens the time to clear integration backlogs following incidents like this one.  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://support.anaplan.com/) website. We appreciate your patience during this incident and value the trust you place in Anaplan.

We are currently investigating an issue resulting in some customers not being able to load models. We are working to resolve this issue as quickly as possible and will provide updates every 30 minutes or upon resolution.

Thank you for your patience as we continue to investigate this issue. Currently, we do not yet have a time to resolution. We will continue to provide updates every 30 minutes as we work to resolve this issue as quickly as possible.

Thank you for your patience as we continue to investigate this issue. Our technical teams are fully engaged, and restoring normal service operations as quickly and safely as possible is our absolute priority. Currently, we do not yet have a time to resolution. We will continue to provide updates every 30 minutes as we work to resolve this issue as quickly as possible.

Thank you for your patience as we continue to investigate this issue. Our coordinated technical response has made progress in narrowing down the scope of our investigation. We have isolated the primary area of concern to our storage configuration layer and are evaluating mitigation steps to alleviate the issue. Currently, we do not yet have a time to resolution. We will continue to provide updates every 30 minutes as we work to resolve this issue as quickly as possible.

We have identified the likely cause of the issue, and we are focused right now on restoring service as quickly as possible. We have identified mitigation steps to alleviate the issue and initial reports indicate positive outcomes of these activities. Currently, we do not yet have a time to resolution. We will provide further updates in 30 minutes or upon resolution.

We are pleased to report a significant milestone in our resolution efforts. Our cross-functional engineering teams have successfully validated a targeted configuration adjustment to restore access to the affected workspaces. We have initiated a phased deployment of this mitigation across the region to safely and systematically restore full access to all affected workspaces. Currently, we do not yet have a time to resolution. We will provide further updates in 30 minutes or upon resolution.

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.

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.

On June 17, 2026, at 06:50 UTC, we became aware of an issue affecting a subset of workspaces in our eu4: Cloud - Europe region. Customers with affected workspaces were unable to load models, seeing persistent loading screens or errors when opening their work. CloudWorks™ integrations in the region also experienced a period of degradation, from approximately 05:20 UTC to 06:26 UTC, because of the same underlying issue. The impact was limited to a specific subset of workspaces — all other regions, and many workspaces in eu4: Cloud - Europe, continued to operate normally. Full service for the affected workspaces was restored at 10:00 UTC.   Root cause  The affected workspaces ran on a previous storage configuration in the eu4 region. Over time, a storage directory used by these workspaces accumulated a large number of small temporary files. The directory reached its operational limit and could no longer accept new file operations. This prevented models from loading for customers whose workspaces were running on this configuration.  Recovery  Our engineering team cleared the accumulated temporary files, which provided immediate relief. We then moved all affected workspaces from the old configuration to the new configuration through an automated process. We checked that model loading was restored through testing. By 10:00 UTC, the issue was fully resolved. On the same day, we implemented a change across the eu4 region to make sure no workspace can be directed to the old configuration.  Corrective and preventative actions  We've taken the following actions to address this incident and prevent it from happening again:  1. We've deployed an update across all regions that prevents any workspace from being directed to the older storage configuration. This eliminates the specific configuration condition that caused this incident.  2. We're decommissioning the older storage configuration. This permanently removes the configuration that caused this incident.  3. We’re strengthening our automated validation checks to confirm that workspaces are running on the correct configuration. This catches any configuration mismatch before it can cause customer impact.  4. We're implementing automated cleanup rules for the temporary files involved in this incident. This prevents storage directories from reaching operational limits and supports faster automatic recovery.  Closing  We apologize for the impact this issue has had on your operations. We're committed to the improvements outlined above to prevent similar disruptions. If you have questions or concerns, please contact [Support](https://support.anaplan.com/).

We are currently investigating an issue impacting customers’ ability to access the Anaplan Platform. We are working to resolve this issue as quickly as possible and will provide updates every 30 minutes or upon resolution.

We want to sincerely apologize to our customers for the continued disruption to the Anaplan Platform today. We understand how critical access to Anaplan is for your business, and we deeply regret the impact this is having on your teams. Our engineers have identified the root cause of this issue and are actively working to restore service. We are currently executing remediation steps and will continue to provide updates here every 30 minutes until full service is restored.

We want to start by offering our sincere apologies to every customer affected by today's disruption to the Anaplan Platform. We know your teams rely on Anaplan to do critical work. Our engineering team has identified the root cause and is fully focused on resolution. Active remediation steps are underway, and we are committed to keeping you informed with updates every 30 minutes — or sooner if there is meaningful progress to share.

We are pleased to share that the core Anaplan Platform has successfully recovered and all primary services are fully operational. Our engineering teams are actively monitoring platform stability while corrective actions to address the underlying root cause continue to advance. We sincerely apologize for the disruption today and recognize that this has been a difficult week for many of our customers. Restoring your trust and ensuring platform stability remains our highest priority. Next update: In 30 minutes or sooner

Our engineering team has successfully implemented a targeted infrastructure patch and completed a controlled failover to the updated version. All primary services are fully restored and accessible to customers. Our teams remain in active monitoring as we continue to validate the patch and advance corrective work across the remaining infrastructure. We do not anticipate further disruption at this time, and we will continue to monitor platform performance closely over the next several hours. We sincerely apologize for the impact today's incidents have had on your teams. A full incident summary will be published once our corrective actions are complete.

The issue impacting access to the Anaplan Platform across all affected regions has been mitigated. The platform is stable and all services have returned to normal operation. Corrective measures to prevent recurrence are actively advancing and will continue to be applied to ensure this issue does not reoccur. We are continuing to monitor the platform to confirm stability. We do not anticipate any further customer impact from these activities. We appreciate your patience and partnership. If you have any questions or concerns, please do not hesitate to contact us at Anaplan Support.

We would like to provide you with the latest update regarding the recent service disruption affecting our platform. Working in close collaboration with our vendor, our engineering team were able to identify a software bug in our network infrastructure that was causing temporary connection instability. To resolve the instability, we applied the fix recommended by the Vendor for the software bug, then successfully moved platform traffic to updated infrastructure at 18:17 UTC on 11 June. All connections stabilised with no disruption observed post the transition. Since then, the platform has remained stable and our engineering teams have continued to monitor this closely. This is our final update on this incident. We will provide a thorough Root Cause Analysis (RCA) within 7 business days. Thank you for your patience and understanding throughout this incident.

**June 8–12, 2026 Platform Disruptions** On June 8, 2026, at 11:05 UTC, our monitoring detected a brief drop in incoming traffic across the Anaplan platform, with automated monitoring checks failing across all affected regions \(us1: Data Center - US East, us2: Data Center - US West, eu1: Data Center - Netherlands, eu2: Data Center - Germany, eu4: Cloud - Europe, us5: Cloud - US East, us7: Cloud - US, and ap1: Cloud - Japan\). Over the four days, a series of related disruptions affected the same regions. Customers experienced intermittent difficulties logging in, opening models, and running integrations. The platform was fully stabilized on June 11, 2026, at 18:12 UTC. These disruptions are linked to our previously communicated infrastructure modernization program. On the weekend of June 6, we migrated our control plane, the part of the platform that directs how traffic is routed between services. This was the most complex of the planned migration weekends, and it was completed successfully, as had the two previous migration weekends. The issues described in this report emerged in the days following that migration. This report covers the seven linked incidents that occurred between June 8 and June 11, 2026. **Root cause** As part of our infrastructure modernization program, on the weekend of June 6, we completed a successful migration of our control plane. In the days that followed, we observed two discrete network-hardware issues that interacted to drive these disruptions. _Issue 1: Media Access Control \(MAC\) flapping \(June 8–9\)_ Every device on a network has a MAC address, a unique hardware identifier that network switches use to route traffic to the correct destination. In our environment, the MAC addresses involved are virtual — assigned to logical network gateways rather than to fixed physical hardware — which allows them to legitimately move between hosts as part of normal operation. MAC flapping occurs when a switch sees the same MAC address appearing on two different physical ports in rapid succession, forcing it repeatedly to update its routing tables. This briefly slows or interrupts traffic. For customers, this surfaced as a brief, self-recovering instability. Short bursts of load and intermittent errors appeared and cleared on their own within minutes. The trigger for this behavior was the specific way live production traffic interacted with the new post-migration network. To resolve the issue, we scaled capacity, engaged our vendor, and deployed configuration changes to contain the impact. _Issue 2: network card driver defect \(June 10–11\)_ Once the first set of mitigations were in place, we identified a second issue: A defect in the network card driver, which is the software that controls how a network card sends and receives data. The defect affected fewer than 0.005% of the cards in our estate. Those cards failed randomly and unpredictably, dropping traffic while still appearing healthy to our monitoring systems. This is known as a "gray failure" condition, because the affected components don’t flag themselves as broken. The cards sat in the part of the network that routes traffic between the regions impacted. This resulted in failures that cascaded across the platform and drove disruptions on June 10 and June 11. The defect hadn't been observed in previous migrations or in any other environment, and there were no indicators in pre-deployment testing. The gray failure pattern was also what initially masked the defect as a load issue, until further investigation pointed us to the driver itself. We engaged our vendor, who confirmed the defect. Working closely with them, we rapidly prepared, tested, and deployed the patch to the affected hosts on the evening of June 11, UTC. After that, the platform stabilized. **Recovery** From the first occurrence on June 8 through to permanent resolution on June 11, our engineering team led a continuous, round-the-clock response, working closely with our vendor to identify, diagnose, and resolve the underlying defect. We deployed configuration mitigations, repeatedly rerouted traffic between hosts and across alternative network paths, and scaled out capacity to restore service to customers as quickly as possible while the underlying defect was being addressed. The seven linked incidents and their impact windows were: * **June 8, 2026, 11:00–11:20 UTC** — A short network disruption from the initial MAC flapping event caused intermittent login failures and slow page loads. For most customers, this appeared as a brief 6-minute blip and recovered automatically. Some basic authentication users experienced a longer impact and needed to start a new browser session, with full recovery by 11:20 UTC. * **June 9, 2026, 11:05–11:29 UTC** — A recurrence of the same MAC flapping condition caused a similar brief disruption. Again, most customers experienced only a short blip of around 6 minutes, with basic authentication users seeing a longer impact. We applied scaling changes to address the issue. * **June 10, 2026, 11:02–12:40 UTC** — Customers across all affected regions experienced a loss of access to the platform for approximately 98 minutes. We worked with the vendor and applied configuration changes to address the issue. * **June 10–11, 2026, 23:06–00:04 UTC** — A disruption of approximately 58 minutes, caused when the network card defect affected the backup host that traffic had been moved to. We restored connectivity by moving traffic onto an alternative network path. * **June 11, 2026, 03:43–05:20 UTC** — A disruption of approximately 97 minutes, as the next backup host was affected by the same defect. We restored connectivity by moving traffic onto an alternative network path. * **June 11, 2026, 11:10–13:02 UTC** — A further recurrence of the network traffic surge caused customers to experience slow or failed access to the platform. We restored service by applying an underlying configuration change. * **June 11, 2026, 17:04–17:48 UTC** — A final disruption of approximately 44 minutes during which we moved traffic to a host running the updated network card driver. The platform was fully stabilized at 18:12 UTC on June 11, 2026, once traffic was successfully moved to a host running the updated network card driver. We then applied the same update to a second host for resilience. Monitoring continued through to midday Friday before the incident was closed. CloudWorks™ experienced a backlog of queued jobs during and immediately after each disruption. Our engineering team scaled out CloudWorks capacity to accelerate processing, and the backlog was fully cleared shortly after each recovery. **Corrective and preventative actions** The control plane migration that preceded these disruptions was a one-time, foundational piece of work. The actions below reflect the learnings we are carrying forward from the event to further strengthen the platform. 1. The updated network card driver has been rolled out across all hosts matching the affected hardware profile, in every region. This removes the underlying defect from our infrastructure, even though it hasn't been observed in any other region. 2. The conditions that allowed MAC flapping to surface as customer-visible instability have been addressed at multiple layers. Configuration changes have been deployed in the affected regions. The underlying network configuration has been standardized across the wider production estate, and we have tuned the network behavior that triggered the initial event. 3. During the incident, our engineering team deployed dedicated alerting in real time for the specific network conditions causing the disruptions, enabling faster detection and intervention throughout the response. We are continuing to strengthen proactive monitoring and early-warning detection across post-release windows, so that emerging anomalies are surfaced and investigated before they escalate into customer-visible disruptions. 4. The remaining infrastructure update that supports the network card fix is being completed across our other environments. This brings the full benefit of the fix to every part of our infrastructure. **What's next** One final migration weekend is scheduled for June 20, 2026. After this, the migration phase of the infrastructure modernization program is complete. **Closing** We apologize for the impact this issue has had on your operations. We're committed to the improvements outlined above to prevent similar disruptions. If you have questions or concerns, please contact [Support](https://support.anaplan.com/).

We are currently investigating an issue impacting customers’ ability to access the Anaplan Platform. We are working to resolve this issue as quickly as possible and will provide updates every 30 minutes or upon resolution.

Thank you for your patience as we continue to investigate this issue. Currently, we do not yet have a time to resolution. We will continue to provide updates every 30 minutes as we work to resolve this issue as quickly as possible.

The symptoms currently being observed are similar to the platform issue experienced earlier today. Our engineering and operations teams have been immediately mobilized and are actively diagnosing the root cause. We treat any recurrence with the utmost urgency and priority. We sincerely apologize for this disruption, we treat any recurrence with the utmost urgency and priority. We will provide another update in 30 minutes, or sooner as we obtain more actionable technical details.

We are beginning to see signs of platform recovery, and primary services are starting to stabilize. As systems come back online, a backlog of queued CloudWorks jobs has accumulated and is currently processing. Our engineering teams are closely monitoring the stability of the platform and tracking the queue clearance velocity. We will provide our next update in 30 minutes, or sooner as we confirm continued stability.

The platform has successfully recovered and is exhibiting stable performance. We are now focused on clearing the accumulated backlog of CloudWorks jobs. Our engineering teams are actively managing and verifying the processing queue to ensure all delayed jobs complete as quickly and safely as possible. We will continue to supervise the queue clearance and will provide our next update in 30 minutes, or sooner as we approach full restoration. 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.

The platform remains stable and fully operational. We are continuing to process the remaining backlog of CloudWorks jobs. Our engineering teams are actively overseeing the processing queues to ensure all jobs complete successfully and system performance remains steady. We appreciate your continued patience as we work through this remaining queue. We will provide our next update in 30 minutes, or sooner as queue clearance nears completion.

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.

We want to keep you informed with the latest update on the service disruption affecting our platform. What we've done We have identified the source of the instability and are actively working to resolve it. Our engineering team, in collaboration with our vendor, has already implemented a configuration change that has reduced the frequency of errors. We are monitoring the platform closely and have seen improvement as a result. We are aware that some customers are experiencing delays and interruptions with their CloudWorks integrations as a direct result of this incident. Our engineering team is actively identifying and resolving any affected integration jobs. Current status The platform is operational. Integration processing is being actively monitored and remediated. We will not consider this incident closed until we are fully satisfied that the platform is stable, all integration jobs are running normally, and the risk of recurrence has been addressed. We will now provide updates every 2 hours, as our investigation progresses and we work with our Vendor. We understand the impact this has had on your operations and we appreciate your patience.

We want to keep you informed with the latest update on the service disruption affecting our platform. After collaboration with our Vendor, we have identified two fixes to our underlying infrastructure. The first fix has now been implemented successfully without further disruption and initial monitoring is proving positive. We are continuing to liaise with our Vendor for the secondary fix, to ensure no further disruption is caused. The platform remains stable and all Cloudworks integrations are working as expected and the backlog has been cleared. The incident will remain open and we will provide updates every 2 hours or sooner, as we continue to investigate and have full resolution. We understand the impact this has had on your operations and we appreciate your patience

We want to provide you with the latest update regarding the recent service disruption affecting our platform. All agreed-upon fixes have been successfully implemented across our underlying infrastructure. Our ongoing monitoring shows that system performance remains stable and positive. Our engineering teams will continue to monitor the platform closely to ensure continued stability. Additionally, we are conducting thorough Root Cause Analysis (RCA) and this will be provided within 7 business days. We sincerely understand the impact this disruption has had on your daily operations, and we deeply appreciate your patience and continued partnership as we work to ensure a reliable experience.

**June 8–12, 2026 Platform Disruptions** On June 8, 2026, at 11:05 UTC, our monitoring detected a brief drop in incoming traffic across the Anaplan platform, with automated monitoring checks failing across all affected regions \(us1: Data Center - US East, us2: Data Center - US West, eu1: Data Center - Netherlands, eu2: Data Center - Germany, eu4: Cloud - Europe, us5: Cloud - US East, us7: Cloud - US, and ap1: Cloud - Japan\). Over the four days, a series of related disruptions affected the same regions. Customers experienced intermittent difficulties logging in, opening models, and running integrations. The platform was fully stabilized on June 11, 2026, at 18:12 UTC. These disruptions are linked to our previously communicated infrastructure modernization program. On the weekend of June 6, we migrated our control plane, the part of the platform that directs how traffic is routed between services. This was the most complex of the planned migration weekends, and it was completed successfully, as had the two previous migration weekends. The issues described in this report emerged in the days following that migration. This report covers the seven linked incidents that occurred between June 8 and June 11, 2026. **Root cause** As part of our infrastructure modernization program, on the weekend of June 6, we completed a successful migration of our control plane. In the days that followed, we observed two discrete network-hardware issues that interacted to drive these disruptions. _Issue 1: Media Access Control \(MAC\) flapping \(June 8–9\)_ Every device on a network has a MAC address, a unique hardware identifier that network switches use to route traffic to the correct destination. In our environment, the MAC addresses involved are virtual — assigned to logical network gateways rather than to fixed physical hardware — which allows them to legitimately move between hosts as part of normal operation. MAC flapping occurs when a switch sees the same MAC address appearing on two different physical ports in rapid succession, forcing it repeatedly to update its routing tables. This briefly slows or interrupts traffic. For customers, this surfaced as a brief, self-recovering instability. Short bursts of load and intermittent errors appeared and cleared on their own within minutes. The trigger for this behavior was the specific way live production traffic interacted with the new post-migration network. To resolve the issue, we scaled capacity, engaged our vendor, and deployed configuration changes to contain the impact. _Issue 2: network card driver defect \(June 10–11\)_ Once the first set of mitigations were in place, we identified a second issue: A defect in the network card driver, which is the software that controls how a network card sends and receives data. The defect affected fewer than 0.005% of the cards in our estate. Those cards failed randomly and unpredictably, dropping traffic while still appearing healthy to our monitoring systems. This is known as a "gray failure" condition, because the affected components don’t flag themselves as broken. The cards sat in the part of the network that routes traffic between the regions impacted. This resulted in failures that cascaded across the platform and drove disruptions on June 10 and June 11. The defect hadn't been observed in previous migrations or in any other environment, and there were no indicators in pre-deployment testing. The gray failure pattern was also what initially masked the defect as a load issue, until further investigation pointed us to the driver itself. We engaged our vendor, who confirmed the defect. Working closely with them, we rapidly prepared, tested, and deployed the patch to the affected hosts on the evening of June 11, UTC. After that, the platform stabilized. **Recovery** From the first occurrence on June 8 through to permanent resolution on June 11, our engineering team led a continuous, round-the-clock response, working closely with our vendor to identify, diagnose, and resolve the underlying defect. We deployed configuration mitigations, repeatedly rerouted traffic between hosts and across alternative network paths, and scaled out capacity to restore service to customers as quickly as possible while the underlying defect was being addressed. The seven linked incidents and their impact windows were: * **June 8, 2026, 11:00–11:20 UTC** — A short network disruption from the initial MAC flapping event caused intermittent login failures and slow page loads. For most customers, this appeared as a brief 6-minute blip and recovered automatically. Some basic authentication users experienced a longer impact and needed to start a new browser session, with full recovery by 11:20 UTC. * **June 9, 2026, 11:05–11:29 UTC** — A recurrence of the same MAC flapping condition caused a similar brief disruption. Again, most customers experienced only a short blip of around 6 minutes, with basic authentication users seeing a longer impact. We applied scaling changes to address the issue. * **June 10, 2026, 11:02–12:40 UTC** — Customers across all affected regions experienced a loss of access to the platform for approximately 98 minutes. We worked with the vendor and applied configuration changes to address the issue. * **June 10–11, 2026, 23:06–00:04 UTC** — A disruption of approximately 58 minutes, caused when the network card defect affected the backup host that traffic had been moved to. We restored connectivity by moving traffic onto an alternative network path. * **June 11, 2026, 03:43–05:20 UTC** — A disruption of approximately 97 minutes, as the next backup host was affected by the same defect. We restored connectivity by moving traffic onto an alternative network path. * **June 11, 2026, 11:10–13:02 UTC** — A further recurrence of the network traffic surge caused customers to experience slow or failed access to the platform. We restored service by applying an underlying configuration change. * **June 11, 2026, 17:04–17:48 UTC** — A final disruption of approximately 44 minutes during which we moved traffic to a host running the updated network card driver. The platform was fully stabilized at 18:12 UTC on June 11, 2026, once traffic was successfully moved to a host running the updated network card driver. We then applied the same update to a second host for resilience. Monitoring continued through to midday Friday before the incident was closed. CloudWorks™ experienced a backlog of queued jobs during and immediately after each disruption. Our engineering team scaled out CloudWorks capacity to accelerate processing, and the backlog was fully cleared shortly after each recovery. **Corrective and preventative actions** The control plane migration that preceded these disruptions was a one-time, foundational piece of work. The actions below reflect the learnings we are carrying forward from the event to further strengthen the platform. 1. The updated network card driver has been rolled out across all hosts matching the affected hardware profile, in every region. This removes the underlying defect from our infrastructure, even though it hasn't been observed in any other region. 2. The conditions that allowed MAC flapping to surface as customer-visible instability have been addressed at multiple layers. Configuration changes have been deployed in the affected regions. The underlying network configuration has been standardized across the wider production estate, and we have tuned the network behavior that triggered the initial event. 3. During the incident, our engineering team deployed dedicated alerting in real time for the specific network conditions causing the disruptions, enabling faster detection and intervention throughout the response. We are continuing to strengthen proactive monitoring and early-warning detection across post-release windows, so that emerging anomalies are surfaced and investigated before they escalate into customer-visible disruptions. 4. The remaining infrastructure update that supports the network card fix is being completed across our other environments. This brings the full benefit of the fix to every part of our infrastructure. **What's next** One final migration weekend is scheduled for June 20, 2026. After this, the migration phase of the infrastructure modernization program is complete. **Closing** We apologize for the impact this issue has had on your operations. We're committed to the improvements outlined above to prevent similar disruptions. If you have questions or concerns, please contact [Support](https://support.anaplan.com/).

We are currently investigating an issue impacting customers’ ability to access the Anaplan Platform. We are working to resolve this issue as quickly as possible and will provide updates every 30 minutes or upon resolution.

Thank you for your patience as we continue to investigate this issue. Currently, we do not yet have a time to resolution. We will continue to provide updates every 30 minutes as we work to resolve this issue as quickly as possible.

We are starting to observe the first initial signs of platform recovery. Our engineering teams are proceeding with extreme caution and are closely monitoring system stability and telemetry as services begin to stabilize. We remain actively engaged in verifying that this early recovery is sustained. We will provide our next update in 30 minutes, or sooner if we detect any changes in performance.

The core platform has successfully recovered, and all primary services are fully operational. We are currently processing a backlog of queued jobs within Cloudworks resulting from the incident. While this backlog is being processed, some customers may experience delays in processing times. We will continue to track performance and will provide our next update in 30 minutes, or sooner as the backlog clears.

We are pleased to report that the CloudWorks backlog is actively processing, and we are now seeing jobs successfully and steadily completing. System throughput has returned to normal operational levels as the queue continues to clear. Our engineering teams remain focused on monitoring the queue velocity until the backlog is fully exhausted and all services have returned to a completely nominal state. We will provide our next update in 30 minutes, or sooner once queue clearance is complete.

We are currently processing a backlog of queued jobs within Cloudworks for US1 and US2 region. While this backlog is being processed, some customers may experience delays in processing times. We will continue to track performance and will provide our next update in 30 minutes, or sooner as the backlog clears.

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.

**June 8–12, 2026 Platform Disruptions** On June 8, 2026, at 11:05 UTC, our monitoring detected a brief drop in incoming traffic across the Anaplan platform, with automated monitoring checks failing across all affected regions \(us1: Data Center - US East, us2: Data Center - US West, eu1: Data Center - Netherlands, eu2: Data Center - Germany, eu4: Cloud - Europe, us5: Cloud - US East, us7: Cloud - US, and ap1: Cloud - Japan\). Over the four days, a series of related disruptions affected the same regions. Customers experienced intermittent difficulties logging in, opening models, and running integrations. The platform was fully stabilized on June 11, 2026, at 18:12 UTC. These disruptions are linked to our previously communicated infrastructure modernization program. On the weekend of June 6, we migrated our control plane, the part of the platform that directs how traffic is routed between services. This was the most complex of the planned migration weekends, and it was completed successfully, as had the two previous migration weekends. The issues described in this report emerged in the days following that migration. This report covers the seven linked incidents that occurred between June 8 and June 11, 2026. **Root cause** As part of our infrastructure modernization program, on the weekend of June 6, we completed a successful migration of our control plane. In the days that followed, we observed two discrete network-hardware issues that interacted to drive these disruptions. _Issue 1: Media Access Control \(MAC\) flapping \(June 8–9\)_ Every device on a network has a MAC address, a unique hardware identifier that network switches use to route traffic to the correct destination. In our environment, the MAC addresses involved are virtual — assigned to logical network gateways rather than to fixed physical hardware — which allows them to legitimately move between hosts as part of normal operation. MAC flapping occurs when a switch sees the same MAC address appearing on two different physical ports in rapid succession, forcing it repeatedly to update its routing tables. This briefly slows or interrupts traffic. For customers, this surfaced as a brief, self-recovering instability. Short bursts of load and intermittent errors appeared and cleared on their own within minutes. The trigger for this behavior was the specific way live production traffic interacted with the new post-migration network. To resolve the issue, we scaled capacity, engaged our vendor, and deployed configuration changes to contain the impact. _Issue 2: network card driver defect \(June 10–11\)_ Once the first set of mitigations were in place, we identified a second issue: A defect in the network card driver, which is the software that controls how a network card sends and receives data. The defect affected fewer than 0.005% of the cards in our estate. Those cards failed randomly and unpredictably, dropping traffic while still appearing healthy to our monitoring systems. This is known as a "gray failure" condition, because the affected components don’t flag themselves as broken. The cards sat in the part of the network that routes traffic between the regions impacted. This resulted in failures that cascaded across the platform and drove disruptions on June 10 and June 11. The defect hadn't been observed in previous migrations or in any other environment, and there were no indicators in pre-deployment testing. The gray failure pattern was also what initially masked the defect as a load issue, until further investigation pointed us to the driver itself. We engaged our vendor, who confirmed the defect. Working closely with them, we rapidly prepared, tested, and deployed the patch to the affected hosts on the evening of June 11, UTC. After that, the platform stabilized. **Recovery** From the first occurrence on June 8 through to permanent resolution on June 11, our engineering team led a continuous, round-the-clock response, working closely with our vendor to identify, diagnose, and resolve the underlying defect. We deployed configuration mitigations, repeatedly rerouted traffic between hosts and across alternative network paths, and scaled out capacity to restore service to customers as quickly as possible while the underlying defect was being addressed. The seven linked incidents and their impact windows were: * **June 8, 2026, 11:00–11:20 UTC** — A short network disruption from the initial MAC flapping event caused intermittent login failures and slow page loads. For most customers, this appeared as a brief 6-minute blip and recovered automatically. Some basic authentication users experienced a longer impact and needed to start a new browser session, with full recovery by 11:20 UTC. * **June 9, 2026, 11:05–11:29 UTC** — A recurrence of the same MAC flapping condition caused a similar brief disruption. Again, most customers experienced only a short blip of around 6 minutes, with basic authentication users seeing a longer impact. We applied scaling changes to address the issue. * **June 10, 2026, 11:02–12:40 UTC** — Customers across all affected regions experienced a loss of access to the platform for approximately 98 minutes. We worked with the vendor and applied configuration changes to address the issue. * **June 10–11, 2026, 23:06–00:04 UTC** — A disruption of approximately 58 minutes, caused when the network card defect affected the backup host that traffic had been moved to. We restored connectivity by moving traffic onto an alternative network path. * **June 11, 2026, 03:43–05:20 UTC** — A disruption of approximately 97 minutes, as the next backup host was affected by the same defect. We restored connectivity by moving traffic onto an alternative network path. * **June 11, 2026, 11:10–13:02 UTC** — A further recurrence of the network traffic surge caused customers to experience slow or failed access to the platform. We restored service by applying an underlying configuration change. * **June 11, 2026, 17:04–17:48 UTC** — A final disruption of approximately 44 minutes during which we moved traffic to a host running the updated network card driver. The platform was fully stabilized at 18:12 UTC on June 11, 2026, once traffic was successfully moved to a host running the updated network card driver. We then applied the same update to a second host for resilience. Monitoring continued through to midday Friday before the incident was closed. CloudWorks™ experienced a backlog of queued jobs during and immediately after each disruption. Our engineering team scaled out CloudWorks capacity to accelerate processing, and the backlog was fully cleared shortly after each recovery. **Corrective and preventative actions** The control plane migration that preceded these disruptions was a one-time, foundational piece of work. The actions below reflect the learnings we are carrying forward from the event to further strengthen the platform. 1. The updated network card driver has been rolled out across all hosts matching the affected hardware profile, in every region. This removes the underlying defect from our infrastructure, even though it hasn't been observed in any other region. 2. The conditions that allowed MAC flapping to surface as customer-visible instability have been addressed at multiple layers. Configuration changes have been deployed in the affected regions. The underlying network configuration has been standardized across the wider production estate, and we have tuned the network behavior that triggered the initial event. 3. During the incident, our engineering team deployed dedicated alerting in real time for the specific network conditions causing the disruptions, enabling faster detection and intervention throughout the response. We are continuing to strengthen proactive monitoring and early-warning detection across post-release windows, so that emerging anomalies are surfaced and investigated before they escalate into customer-visible disruptions. 4. The remaining infrastructure update that supports the network card fix is being completed across our other environments. This brings the full benefit of the fix to every part of our infrastructure. **What's next** One final migration weekend is scheduled for June 20, 2026. After this, the migration phase of the infrastructure modernization program is complete. **Closing** We apologize for the impact this issue has had on your operations. We're committed to the improvements outlined above to prevent similar disruptions. If you have questions or concerns, please contact [Support](https://support.anaplan.com/).

We are currently investigating an active incident that may affect Basic Authentication access. If you encounter issues when attempting to access the platform please use the following workaround while we resolve the issue: - Close your current session— Close the active browser tab or open a new Incognito/Private window. - Re-authenticate— Navigate to the portal and log in again with your credentials to establish a fresh session. We are actively monitoring the platform and will continue to do so until the issue is fully resolved. If you are still experiencing difficulties or have any questions, please reach out to Anaplan Support

Since our last update, we have detected a further degradation in general platform performance. Our engineering teams are actively investigating the root cause with the highest priority, and we will provide further updates as the situation develops Currently, we do not yet have a time to resolution. We will continue to provide updates every 30 minutes as we work to resolve this issue as quickly as possible.

Following our previous notification, the ongoing performance issues have escalated, resulting in broader platform-wide degradation. Our senior engineering teams have successfully identified the root cause of the issue and are currently executing targeted remediation steps to restore normal operations as our absolute highest priority. Currently, we do not yet have a time to resolution. We will continue to provide updates every 30 minutes as we work to resolve this issue as quickly as possible.

Our engineering teams continue to actively investigate the incident while simultaneously implementing targeted remediation steps to stabilize the platform. We are closely monitoring the system's response to these actions and will provide our updates every 30 minutes as we work to resolve this issue as quickly as possible.

The general platform has successfully recovered and is operating normally; however, we are actively addressing a residual issue impacting Cloudworks that is currently preventing integration jobs from completing. Our technical teams remain focused on resolving this remaining component to restore full service across all integrations 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.

We are pleased to report that integration jobs are now successfully completing, and our systems are actively processing the accumulated backlog across all regions. To accelerate this recovery, we have scaled out our service capacity, with a particular focus on the us7: Cloud - US region to expedite the clearance of its more significant backlog. We will provide further updates in 30 minutes or upon resolution.

We are pleased to report that integration processing has returned to normal operational levels across all global regions, with the sole exception of us7: Cloud - US. The us7: Cloud - US region continues to steadily work through its remaining queue utilizing our expanded capacity, and we are monitoring progress closely to ensure a complete return to baseline performance. Currently, we do not yet have a time to resolution. We will provide further updates in 30 minutes or upon resolution.

As we continue our active recovery efforts, we have identified localized capacity constraints in the us1: Data Center - US East region that may intermittently affect customers attempting to load models. Our engineering teams are addressing this resource bottleneck to restore full service. The CloudWorks backlog in us7: Cloud - US has finished processing, and the service has returned to normal operations. While an estimated time to resolution is not yet established, our teams are treating this with the highest urgency. We will provide our next update in 30 minutes, or sooner if a resolution is reached.

Our investigation indicates that the backend connectivity issues in US1, stemming from a localized network disruption, are specifically isolated to the loading of large models in excess of 200GB. Customers attempting to load smaller models should experience normal performance and remain unaffected as our network engineering teams actively work to restore stable pathways for larger model payloads. Currently, we do not yet have a time to resolution. We will continue to provide updates every 30 minutes as we work to resolve this issue as quickly as possible.

Our network engineering teams continue to actively implement remediation steps to address the localized network issue in the us1: Data Center - US East region. We remain focused on resolving the backend connectivity disruptions affecting the loading of larger models, while smaller models continue to perform normally. We are closely monitoring system behavior as we deploy these targeted fixes and will provide our next update in 30 minutes, or sooner if significant progress is made. Currently, we do not yet have a time to resolution. We will provide further updates in 30 minutes or upon resolution.

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.

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.

**June 8–12, 2026 Platform Disruptions** On June 8, 2026, at 11:05 UTC, our monitoring detected a brief drop in incoming traffic across the Anaplan platform, with automated monitoring checks failing across all affected regions \(us1: Data Center - US East, us2: Data Center - US West, eu1: Data Center - Netherlands, eu2: Data Center - Germany, eu4: Cloud - Europe, us5: Cloud - US East, us7: Cloud - US, and ap1: Cloud - Japan\). Over the four days, a series of related disruptions affected the same regions. Customers experienced intermittent difficulties logging in, opening models, and running integrations. The platform was fully stabilized on June 11, 2026, at 18:12 UTC. These disruptions are linked to our previously communicated infrastructure modernization program. On the weekend of June 6, we migrated our control plane, the part of the platform that directs how traffic is routed between services. This was the most complex of the planned migration weekends, and it was completed successfully, as had the two previous migration weekends. The issues described in this report emerged in the days following that migration. This report covers the seven linked incidents that occurred between June 8 and June 11, 2026. **Root cause** As part of our infrastructure modernization program, on the weekend of June 6, we completed a successful migration of our control plane. In the days that followed, we observed two discrete network-hardware issues that interacted to drive these disruptions. _Issue 1: Media Access Control \(MAC\) flapping \(June 8–9\)_ Every device on a network has a MAC address, a unique hardware identifier that network switches use to route traffic to the correct destination. In our environment, the MAC addresses involved are virtual — assigned to logical network gateways rather than to fixed physical hardware — which allows them to legitimately move between hosts as part of normal operation. MAC flapping occurs when a switch sees the same MAC address appearing on two different physical ports in rapid succession, forcing it repeatedly to update its routing tables. This briefly slows or interrupts traffic. For customers, this surfaced as a brief, self-recovering instability. Short bursts of load and intermittent errors appeared and cleared on their own within minutes. The trigger for this behavior was the specific way live production traffic interacted with the new post-migration network. To resolve the issue, we scaled capacity, engaged our vendor, and deployed configuration changes to contain the impact. _Issue 2: network card driver defect \(June 10–11\)_ Once the first set of mitigations were in place, we identified a second issue: A defect in the network card driver, which is the software that controls how a network card sends and receives data. The defect affected fewer than 0.005% of the cards in our estate. Those cards failed randomly and unpredictably, dropping traffic while still appearing healthy to our monitoring systems. This is known as a "gray failure" condition, because the affected components don’t flag themselves as broken. The cards sat in the part of the network that routes traffic between the regions impacted. This resulted in failures that cascaded across the platform and drove disruptions on June 10 and June 11. The defect hadn't been observed in previous migrations or in any other environment, and there were no indicators in pre-deployment testing. The gray failure pattern was also what initially masked the defect as a load issue, until further investigation pointed us to the driver itself. We engaged our vendor, who confirmed the defect. Working closely with them, we rapidly prepared, tested, and deployed the patch to the affected hosts on the evening of June 11, UTC. After that, the platform stabilized. **Recovery** From the first occurrence on June 8 through to permanent resolution on June 11, our engineering team led a continuous, round-the-clock response, working closely with our vendor to identify, diagnose, and resolve the underlying defect. We deployed configuration mitigations, repeatedly rerouted traffic between hosts and across alternative network paths, and scaled out capacity to restore service to customers as quickly as possible while the underlying defect was being addressed. The seven linked incidents and their impact windows were: * **June 8, 2026, 11:00–11:20 UTC** — A short network disruption from the initial MAC flapping event caused intermittent login failures and slow page loads. For most customers, this appeared as a brief 6-minute blip and recovered automatically. Some basic authentication users experienced a longer impact and needed to start a new browser session, with full recovery by 11:20 UTC. * **June 9, 2026, 11:05–11:29 UTC** — A recurrence of the same MAC flapping condition caused a similar brief disruption. Again, most customers experienced only a short blip of around 6 minutes, with basic authentication users seeing a longer impact. We applied scaling changes to address the issue. * **June 10, 2026, 11:02–12:40 UTC** — Customers across all affected regions experienced a loss of access to the platform for approximately 98 minutes. We worked with the vendor and applied configuration changes to address the issue. * **June 10–11, 2026, 23:06–00:04 UTC** — A disruption of approximately 58 minutes, caused when the network card defect affected the backup host that traffic had been moved to. We restored connectivity by moving traffic onto an alternative network path. * **June 11, 2026, 03:43–05:20 UTC** — A disruption of approximately 97 minutes, as the next backup host was affected by the same defect. We restored connectivity by moving traffic onto an alternative network path. * **June 11, 2026, 11:10–13:02 UTC** — A further recurrence of the network traffic surge caused customers to experience slow or failed access to the platform. We restored service by applying an underlying configuration change. * **June 11, 2026, 17:04–17:48 UTC** — A final disruption of approximately 44 minutes during which we moved traffic to a host running the updated network card driver. The platform was fully stabilized at 18:12 UTC on June 11, 2026, once traffic was successfully moved to a host running the updated network card driver. We then applied the same update to a second host for resilience. Monitoring continued through to midday Friday before the incident was closed. CloudWorks™ experienced a backlog of queued jobs during and immediately after each disruption. Our engineering team scaled out CloudWorks capacity to accelerate processing, and the backlog was fully cleared shortly after each recovery. **Corrective and preventative actions** The control plane migration that preceded these disruptions was a one-time, foundational piece of work. The actions below reflect the learnings we are carrying forward from the event to further strengthen the platform. 1. The updated network card driver has been rolled out across all hosts matching the affected hardware profile, in every region. This removes the underlying defect from our infrastructure, even though it hasn't been observed in any other region. 2. The conditions that allowed MAC flapping to surface as customer-visible instability have been addressed at multiple layers. Configuration changes have been deployed in the affected regions. The underlying network configuration has been standardized across the wider production estate, and we have tuned the network behavior that triggered the initial event. 3. During the incident, our engineering team deployed dedicated alerting in real time for the specific network conditions causing the disruptions, enabling faster detection and intervention throughout the response. We are continuing to strengthen proactive monitoring and early-warning detection across post-release windows, so that emerging anomalies are surfaced and investigated before they escalate into customer-visible disruptions. 4. The remaining infrastructure update that supports the network card fix is being completed across our other environments. This brings the full benefit of the fix to every part of our infrastructure. **What's next** One final migration weekend is scheduled for June 20, 2026. After this, the migration phase of the infrastructure modernization program is complete. **Closing** We apologize for the impact this issue has had on your operations. We're committed to the improvements outlined above to prevent similar disruptions. If you have questions or concerns, please contact [Support](https://support.anaplan.com/).

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.

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.

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.

**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.

We are currently investigating an active incident that may affect Basic Authentication access. If you encounter errors when attempting to log in please do the following: - Close your current session— Close the active browser tab or open a new Incognito/Private window. - Re-authenticate— Navigate to the portal and log in again with your credentials to establish a fresh session. We are actively monitoring the platform and will continue to do so until the issue is fully resolved. If you are still experiencing difficulties or have any questions, please reach out to Anaplan Support We are working to resolve this issue as quickly as possible and will provide updates every 30 minutes or upon resolution.

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.

**June 8–12, 2026 Platform Disruptions** On June 8, 2026, at 11:05 UTC, our monitoring detected a brief drop in incoming traffic across the Anaplan platform, with automated monitoring checks failing across all affected regions \(us1: Data Center - US East, us2: Data Center - US West, eu1: Data Center - Netherlands, eu2: Data Center - Germany, eu4: Cloud - Europe, us5: Cloud - US East, us7: Cloud - US, and ap1: Cloud - Japan\). Over the four days, a series of related disruptions affected the same regions. Customers experienced intermittent difficulties logging in, opening models, and running integrations. The platform was fully stabilized on June 11, 2026, at 18:12 UTC. These disruptions are linked to our previously communicated infrastructure modernization program. On the weekend of June 6, we migrated our control plane, the part of the platform that directs how traffic is routed between services. This was the most complex of the planned migration weekends, and it was completed successfully, as had the two previous migration weekends. The issues described in this report emerged in the days following that migration. This report covers the seven linked incidents that occurred between June 8 and June 11, 2026. **Root cause** As part of our infrastructure modernization program, on the weekend of June 6, we completed a successful migration of our control plane. In the days that followed, we observed two discrete network-hardware issues that interacted to drive these disruptions. _Issue 1: Media Access Control \(MAC\) flapping \(June 8–9\)_ Every device on a network has a MAC address, a unique hardware identifier that network switches use to route traffic to the correct destination. In our environment, the MAC addresses involved are virtual — assigned to logical network gateways rather than to fixed physical hardware — which allows them to legitimately move between hosts as part of normal operation. MAC flapping occurs when a switch sees the same MAC address appearing on two different physical ports in rapid succession, forcing it repeatedly to update its routing tables. This briefly slows or interrupts traffic. For customers, this surfaced as a brief, self-recovering instability. Short bursts of load and intermittent errors appeared and cleared on their own within minutes. The trigger for this behavior was the specific way live production traffic interacted with the new post-migration network. To resolve the issue, we scaled capacity, engaged our vendor, and deployed configuration changes to contain the impact. _Issue 2: network card driver defect \(June 10–11\)_ Once the first set of mitigations were in place, we identified a second issue: A defect in the network card driver, which is the software that controls how a network card sends and receives data. The defect affected fewer than 0.005% of the cards in our estate. Those cards failed randomly and unpredictably, dropping traffic while still appearing healthy to our monitoring systems. This is known as a "gray failure" condition, because the affected components don’t flag themselves as broken. The cards sat in the part of the network that routes traffic between the regions impacted. This resulted in failures that cascaded across the platform and drove disruptions on June 10 and June 11. The defect hadn't been observed in previous migrations or in any other environment, and there were no indicators in pre-deployment testing. The gray failure pattern was also what initially masked the defect as a load issue, until further investigation pointed us to the driver itself. We engaged our vendor, who confirmed the defect. Working closely with them, we rapidly prepared, tested, and deployed the patch to the affected hosts on the evening of June 11, UTC. After that, the platform stabilized. **Recovery** From the first occurrence on June 8 through to permanent resolution on June 11, our engineering team led a continuous, round-the-clock response, working closely with our vendor to identify, diagnose, and resolve the underlying defect. We deployed configuration mitigations, repeatedly rerouted traffic between hosts and across alternative network paths, and scaled out capacity to restore service to customers as quickly as possible while the underlying defect was being addressed. The seven linked incidents and their impact windows were: * **June 8, 2026, 11:00–11:20 UTC** — A short network disruption from the initial MAC flapping event caused intermittent login failures and slow page loads. For most customers, this appeared as a brief 6-minute blip and recovered automatically. Some basic authentication users experienced a longer impact and needed to start a new browser session, with full recovery by 11:20 UTC. * **June 9, 2026, 11:05–11:29 UTC** — A recurrence of the same MAC flapping condition caused a similar brief disruption. Again, most customers experienced only a short blip of around 6 minutes, with basic authentication users seeing a longer impact. We applied scaling changes to address the issue. * **June 10, 2026, 11:02–12:40 UTC** — Customers across all affected regions experienced a loss of access to the platform for approximately 98 minutes. We worked with the vendor and applied configuration changes to address the issue. * **June 10–11, 2026, 23:06–00:04 UTC** — A disruption of approximately 58 minutes, caused when the network card defect affected the backup host that traffic had been moved to. We restored connectivity by moving traffic onto an alternative network path. * **June 11, 2026, 03:43–05:20 UTC** — A disruption of approximately 97 minutes, as the next backup host was affected by the same defect. We restored connectivity by moving traffic onto an alternative network path. * **June 11, 2026, 11:10–13:02 UTC** — A further recurrence of the network traffic surge caused customers to experience slow or failed access to the platform. We restored service by applying an underlying configuration change. * **June 11, 2026, 17:04–17:48 UTC** — A final disruption of approximately 44 minutes during which we moved traffic to a host running the updated network card driver. The platform was fully stabilized at 18:12 UTC on June 11, 2026, once traffic was successfully moved to a host running the updated network card driver. We then applied the same update to a second host for resilience. Monitoring continued through to midday Friday before the incident was closed. CloudWorks™ experienced a backlog of queued jobs during and immediately after each disruption. Our engineering team scaled out CloudWorks capacity to accelerate processing, and the backlog was fully cleared shortly after each recovery. **Corrective and preventative actions** The control plane migration that preceded these disruptions was a one-time, foundational piece of work. The actions below reflect the learnings we are carrying forward from the event to further strengthen the platform. 1. The updated network card driver has been rolled out across all hosts matching the affected hardware profile, in every region. This removes the underlying defect from our infrastructure, even though it hasn't been observed in any other region. 2. The conditions that allowed MAC flapping to surface as customer-visible instability have been addressed at multiple layers. Configuration changes have been deployed in the affected regions. The underlying network configuration has been standardized across the wider production estate, and we have tuned the network behavior that triggered the initial event. 3. During the incident, our engineering team deployed dedicated alerting in real time for the specific network conditions causing the disruptions, enabling faster detection and intervention throughout the response. We are continuing to strengthen proactive monitoring and early-warning detection across post-release windows, so that emerging anomalies are surfaced and investigated before they escalate into customer-visible disruptions. 4. The remaining infrastructure update that supports the network card fix is being completed across our other environments. This brings the full benefit of the fix to every part of our infrastructure. **What's next** One final migration weekend is scheduled for June 20, 2026. After this, the migration phase of the infrastructure modernization program is complete. **Closing** We apologize for the impact this issue has had on your operations. We're committed to the improvements outlined above to prevent similar disruptions. If you have questions or concerns, please contact [Support](https://support.anaplan.com/).

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.

Thank you for your patience as we continue to investigate this issue. Currently, we do not yet have a time to full resolution.  Access to the UI has been restored and we are currently investigating the degradation to integrations. We will continue to provide updates every 30 minutes as we work to resolve this issue as quickly as possible.

We are currently investigating an issue impacting impacting Cloudworks. We are working to resolve this issue as quickly as possible and will provide updates every 30 minutes or upon resolution.

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.

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.

**Introduction**  On June 8, 2026, at 13:14 UTC, customers in our ap1: Cloud - Japan, eu1: Data Center - Netherlands, eu2: Data Center - Germany, us2: Data Center - US West, us5: Cloud - US East, us7: Cloud - US, and eu4: Cloud - Europe regions experienced delays and difficulties accessing the CloudWorks™ user interface. During this period, users experienced slow UI access and a temporary inability to create new integrations or run certain scheduled jobs. Existing workflows were unaffected, although some experienced minor delays in completion.  **Root cause**  The root cause of this incident was an incorrect configuration setting where certain backend components did not automatically pick up updated hostname configurations following a scheduled system migration. Consequently, these components continued to attempt connections using the outdated configuration, leading to connection failures. This prevented users from accessing the user interface and successfully initiating new integration runs. The issue was resolved by reloading the updated configuration on the affected services.  **Recovery**  Our engineering team identified the issue and took immediate action. We initiated a rolling restart of the job management service across the affected regions, which restored user interface access. To fully resolve the connection errors, the engineering team performed a comprehensive restart of all related service components in every affected region, forcing them to load the updated database configurations. Following these restarts, database connection errors immediately ceased, and manual validation confirmed that both user-interface access and integration scheduling were fully restored and functioning normally. By 15:52 UTC, the issue was fully resolved.  **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 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 configuration mismatches.  * We are strengthening our platform observability and system telemetry to improve our diagnostic capabilities and detect connection issues more rapidly.  * We are refining our strategy and APIs to proactively detect and manage delayed integration workflows.   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.