Platform Alerts

Update timeline

1. investigating Jun 11, 2026, 05:20 PM UTC

   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.

2. identified Jun 11, 2026, 05:45 PM UTC

   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.

3. identified Jun 11, 2026, 06:15 PM UTC

   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.

4. monitoring Jun 11, 2026, 06:27 PM UTC

   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

5. monitoring Jun 11, 2026, 06:47 PM UTC

   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.

6. monitoring Jun 12, 2026, 12:30 AM UTC

   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.

7. resolved Jun 12, 2026, 03:09 PM UTC

   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.

8. postmortem Jun 19, 2026, 02:38 PM UTC

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