Is Anaplan down?

Last checked 7m ago
Current status
Anaplan is having a partial outage

Active incident: Platform Alerts

Official status page: https://status.anaplan.com · Polled every 5 minutes · 24 components tracked

Anaplan is reporting a partial outage right now (last checked 7m ago). Some components are affected; others remain operational.

Real-time Anaplan status, recent outages, and incident history — pulled directly from Anaplan's official status page at https://status.anaplan.com every 5 minutes. Pingoru tracks 24 Anaplan services and has captured 31 incidents in the last 90 days (94.65% uptime). Get email, Slack, Discord, or webhook alerts the moment Anaplan reports a new incident — free for 5 monitors, no credit card.

Users who monitor Anaplan also follow these Finance services: Affirm QuickBooks PayRange Avalara Plaid Xero Zuora Bill.com Xero Developer Platform Recharge View all 6,000+ providers
Anaplan uptime 94.65% uptime · past 90 days
Mon Wed Fri
MayJunJul
Less More

Active incident 1

  1. Ongoing ● 6d 8h
    Started Jul 24, 2026, 08:35 PM UTC
    ca1: Cloud - Canada
    Timeline · 53 updates
    • investigating · Jul 24, 2026, 08:35 PM UTC

      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.

    • investigating · Jul 24, 2026, 08:59 PM UTC

      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.

    • investigating · Jul 24, 2026, 09:29 PM UTC

      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.

    • investigating · Jul 24, 2026, 10:00 PM UTC

      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.

    • investigating · Jul 24, 2026, 10:28 PM UTC

      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.

    • investigating · Jul 24, 2026, 11:01 PM UTC

      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.

    • investigating · Jul 24, 2026, 11:33 PM UTC

      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.

    • investigating · Jul 25, 2026, 12:07 AM UTC

      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.

    • investigating · Jul 25, 2026, 12:39 AM UTC

      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.

    • investigating · Jul 25, 2026, 01:08 AM UTC

      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.

    • investigating · Jul 25, 2026, 01:42 AM UTC

      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.

    • investigating · Jul 25, 2026, 02:18 AM UTC

      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.

    • investigating · Jul 25, 2026, 03:09 AM UTC

      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.

    • investigating · Jul 25, 2026, 03:47 AM UTC

      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.

    • investigating · Jul 25, 2026, 04:47 AM UTC

      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.

    • identified · Jul 25, 2026, 06:05 AM UTC

      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.

    • identified · Jul 25, 2026, 07:06 AM UTC

      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.

    • identified · Jul 25, 2026, 08:07 AM UTC

      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.

    • identified · Jul 25, 2026, 09:06 AM UTC

      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.

    • investigating · Jul 25, 2026, 10:07 AM UTC

      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.

    • identified · Jul 25, 2026, 11:14 AM UTC

      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.

    • identified · Jul 25, 2026, 12:37 PM UTC

      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.

    • identified · Jul 25, 2026, 01:51 PM UTC

      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.

    • identified · Jul 25, 2026, 03:01 PM UTC

      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.

    • identified · Jul 25, 2026, 04:22 PM UTC

      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.

    • identified · Jul 25, 2026, 05:24 PM UTC

      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.

    • identified · Jul 25, 2026, 07:39 PM UTC

      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.

    • identified · Jul 25, 2026, 09:20 PM UTC

      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.

    • identified · Jul 25, 2026, 10:21 PM UTC

      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.

    • identified · Jul 25, 2026, 11:28 PM UTC

      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.

    • identified · Jul 25, 2026, 11:52 PM UTC

      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.

    • investigating · Jul 26, 2026, 08:59 AM UTC

      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.

    • investigating · Jul 26, 2026, 11:16 AM UTC

      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.

    • investigating · Jul 26, 2026, 01:06 PM UTC

      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.

    • investigating · Jul 26, 2026, 03:20 PM UTC

      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.

    • identified · Jul 26, 2026, 05:53 PM UTC

      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.

    • identified · Jul 26, 2026, 06:49 PM UTC

      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.

    • investigating · Jul 27, 2026, 10:03 AM UTC

      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.

    • investigating · Jul 27, 2026, 12:30 PM UTC

      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.

    • investigating · Jul 27, 2026, 02:04 PM UTC

      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.

    • identified · Jul 27, 2026, 03:54 PM UTC

      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.

    • investigating · Jul 27, 2026, 05:37 PM UTC

      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.

    • identified · Jul 28, 2026, 09:02 AM UTC

      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.

    • identified · Jul 28, 2026, 11:01 AM UTC

      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.

    • identified · Jul 28, 2026, 01:11 PM UTC

      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.

    • identified · Jul 28, 2026, 04:02 PM UTC

      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.

    • identified · Jul 28, 2026, 07:51 PM UTC

      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.

    • identified · Jul 29, 2026, 09:04 AM UTC

      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.

    • investigating · Jul 29, 2026, 01:23 PM UTC

      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.

    • investigating · Jul 29, 2026, 03:21 PM UTC

      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.

    • investigating · Jul 29, 2026, 05:17 PM UTC

      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.

    • investigating · Jul 30, 2026, 08:59 AM UTC

      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.

    • investigating · Jul 30, 2026, 11:07 AM UTC

      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.

    Latest: 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 re…

Recent outages & incidents

Past 90 days
  1. Resolved 1h 44m
    Started Jul 29, 2026, 11:06 AM UTC · Resolved Jul 29, 2026, 12:51 PM UTC
    us1: Data Center - US Eastus2: Data Center - US Westeu1: Data Center - Netherlandseu2: Data Center - Germanyeu4: Cloud - Europeus5: Cloud - US Eastap1: Cloud - Japanus7: Cloud - US
    Timeline · 4 updates
    • investigating · Jul 29, 2026, 11:06 AM 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.

    • investigating · Jul 29, 2026, 11:36 AM UTC

      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.

    • monitoring · Jul 29, 2026, 11:41 AM UTC

      Service has now been restored; you should now be able to resume normal activities. We will continue to monitor the platform to ensure no additional issues arise. If you have any questions, concerns, or continue to experience issues, please do not hesitate to contact Anaplan Support. We will provide a final update to you when we consider this situation fully resolved.

    • resolved · Jul 29, 2026, 12:51 PM UTC

      We have confirmed that the issue is now resolved. We deeply apologize for any impact this issue may have caused. We appreciate your patience and partnership as we worked through this issue. We will follow up within 7 business days with a detailed root cause analysis (RCA) that will be shared on our Status Page. If you have any question or concerns, please do not hesitate to contact us at Anaplan Support.

    Latest: 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 th…

  2. Resolved 24m
    Started Jul 21, 2026, 02:30 PM UTC · Resolved Jul 21, 2026, 02:54 PM UTC
    us5: Cloud - US East
    Timeline · 4 updates
    • investigating · Jul 21, 2026, 02:30 PM UTC

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

    • monitoring · Jul 21, 2026, 02:44 PM UTC

      Service has now been restored; you should now be able to resume normal activities. We will continue to monitor the platform to ensure no additional issues arise. If you have any questions, concerns, or continue to experience issues, please do not hesitate to contact Anaplan Support. We will provide a final update to you when we consider this situation fully resolved.

    • resolved · Jul 21, 2026, 02:54 PM UTC

      We have confirmed that the issue is now resolved. We deeply apologize for any impact this issue may have caused. We appreciate your patience and partnership as we worked through this issue. We will follow up within 7 business days with a detailed root cause analysis (RCA) that will be shared on our Status Page. If you have any question or concerns, please do not hesitate to contact us at Anaplan Support.

    • postmortem · Jul 30, 2026, 10:22 PM UTC

      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.

    Latest: 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 wor…

  3. Resolved 1h 7m
    Started Jul 14, 2026, 08:04 PM UTC · Resolved Jul 14, 2026, 09:12 PM UTC
    us7: Cloud - US
    Timeline · 6 updates
    • investigating · Jul 14, 2026, 08:04 PM UTC

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

    • monitoring · Jul 14, 2026, 08:31 PM UTC

      Service has now been restored; you should now be able to resume normal activities. We will continue to monitor the platform to ensure no additional issues arise. If you have any questions, concerns, or continue to experience issues, please do not hesitate to contact Anaplan Support. We will provide a final update to you when we consider this situation fully resolved.

    • monitoring · Jul 14, 2026, 09:00 PM UTC

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

    • monitoring · Jul 14, 2026, 09:04 PM UTC

      Service has now been restored; you should now be able to resume normal activities. We will continue to monitor the platform to ensure no additional issues arise. If you have any questions, concerns, or continue to experience issues, please do not hesitate to contact Anaplan Support. We will provide a final update to you when we consider this situation fully resolved.

    • resolved · Jul 14, 2026, 09:12 PM UTC

      We have confirmed that the issue is now resolved. We deeply apologize for any impact this issue may have caused. We appreciate your patience and partnership as we worked through this issue. We will follow up within 7 business days with a detailed root cause analysis (RCA) that will be shared on our Status Page. If you have any question or concerns, please do not hesitate to contact us at Anaplan Support.

    • postmortem · Jul 22, 2026, 06:15 PM UTC

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

    Latest: 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 s…

  4. Resolved 4h
    Started Jul 02, 2026, 12:00 AM UTC · Resolved Jul 02, 2026, 04:00 AM UTC
    me1: Cloud - Saudi Arabiaeu5: Cloud - Europe
    Timeline · 10 updates
    • investigating · Jul 02, 2026, 12:00 AM 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.

    • investigating · Jul 02, 2026, 12:30 AM UTC

      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.

    • investigating · Jul 02, 2026, 12:59 AM UTC

      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.

    • investigating · Jul 02, 2026, 01:29 AM UTC

      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.

    • investigating · Jul 02, 2026, 01:58 AM UTC

      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.

    • investigating · Jul 02, 2026, 02:27 AM UTC

      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.

    • investigating · Jul 02, 2026, 02:55 AM UTC

      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.

    • monitoring · Jul 02, 2026, 03:21 AM UTC

      Service has now been restored; you should now be able to resume normal activities. We will continue to monitor the platform to ensure no additional issues arise. If you have any questions, concerns, or continue to experience issues, please do not hesitate to contact Anaplan Support. We will provide a final update to you when we consider this situation fully resolved.

    • resolved · Jul 02, 2026, 04:00 AM UTC

      We have confirmed that the issue is now resolved. We deeply apologize for any impact this issue may have caused. We appreciate your patience and partnership as we worked through this issue. We will follow up within 7 business days with a detailed root cause analysis (RCA) that will be shared on our Status Page. If you have any question or concerns, please do not hesitate to contact us at Anaplan Support.

    • postmortem · Jul 10, 2026, 06:35 PM UTC

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

    Latest: 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 region…

  5. Resolved 3h 23m
    Started Jun 22, 2026, 07:29 AM UTC · Resolved Jun 22, 2026, 10:52 AM UTC
    us7: Cloud - US
    Timeline · 10 updates
    • investigating · Jun 22, 2026, 07:29 AM UTC

      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.

    • investigating · Jun 22, 2026, 07:48 AM UTC

      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.

    • investigating · Jun 22, 2026, 08:23 AM UTC

      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.

    • identified · Jun 22, 2026, 08:52 AM UTC

      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.

    • identified · Jun 22, 2026, 09:25 AM UTC

      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.

    • identified · Jun 22, 2026, 09:36 AM UTC

      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.

    • identified · Jun 22, 2026, 10:05 AM UTC

      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.

    • monitoring · Jun 22, 2026, 10:22 AM UTC

      Service has now been restored; you should now be able to resume normal activities. We will continue to monitor the platform to ensure no additional issues arise. If you have any questions, concerns, or continue to experience issues, please do not hesitate to contact Anaplan Support. We will provide a final update to you when we consider this situation fully resolved.

    • resolved · Jun 22, 2026, 10:52 AM UTC

      We have confirmed that the issue is now resolved. We deeply apologize for any impact this issue may have caused. We appreciate your patience and partnership as we worked through this issue. We will follow up within 7 business days with a detailed root cause analysis (RCA) that will be shared on our Status Page. If you have any question or concerns, please do not hesitate to contact us at Anaplan Support.

    • postmortem · Jul 01, 2026, 07:34 PM UTC

      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.

    Latest: 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 approx…

See the full Anaplan outage history

19 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Browse Anaplan outage history →

Or sign up free to get alerts when Anaplan breaks · 10 free monitors · No credit card

Outage history

Past 90 days · 24 incidents View full outage history →
  • Started Jul 29, 2026, 11:06 AM UTC · Resolved Jul 29, 2026, 12:51 PM UTC · 1h 44m
  • Started Jul 24, 2026, 08:35 PM UTC · ● 6d 8h
  • Started Jul 21, 2026, 02:30 PM UTC · Resolved Jul 21, 2026, 02:54 PM UTC · 24m
  • Started Jul 14, 2026, 08:04 PM UTC · Resolved Jul 14, 2026, 09:12 PM UTC · 1h 7m
  • Started Jul 02, 2026, 12:00 AM UTC · Resolved Jul 02, 2026, 04:00 AM UTC · 4h
  • Started Jun 22, 2026, 07:29 AM UTC · Resolved Jun 22, 2026, 10:52 AM UTC · 3h 23m
  • Started Jun 17, 2026, 07:02 AM UTC · Resolved Jun 17, 2026, 10:23 AM UTC · 3h 20m
  • Started Jun 11, 2026, 05:20 PM UTC · Resolved Jun 12, 2026, 03:09 PM UTC · 21h 49m