Is there an SAP LeanIX outage?
SAP LeanIX status: Systems Active
Last checked: 2 minutes ago
Get notified about any outages, downtime or incidents for SAP LeanIX and 1800+ other cloud vendors. Monitor 10 companies, for free.
Last checked: 2 minutes ago
Get notified about any outages, downtime or incidents for SAP LeanIX and 1800+ other cloud vendors. Monitor 10 companies, for free.
Outage and incident data over the last 30 days for SAP LeanIX.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage. It's completely free and takes less than 2 minutes!
Sign Up NowOutlogger tracks the status of these components for Xero:
| Component | Status |
|---|---|
| Website | Active |
| AE Instances | Active |
| EAM | Active |
| SMP | Active |
| VSM | Active |
| AU Instances | Active |
| EAM | Active |
| SMP | Active |
| VSM | Active |
| BR Instances | Active |
| EAM | Active |
| CA Instances | Active |
| EAM | Active |
| SMP | Active |
| VSM | Active |
| CH Instances | Active |
| EAM | Active |
| SMP | Active |
| VSM | Active |
| DE Instances | Active |
| EAM | Active |
| SMP | Active |
| VSM | Active |
| EU Instances | Active |
| EAM | Active |
| SMP | Active |
| VSM | Active |
| UK Instances | Active |
| EAM | Active |
| SMP | Active |
| VSM | Active |
| US Instances | Active |
| EAM | Active |
| SMP | Active |
| VSM | Active |
View the latest incidents for SAP LeanIX and check for official updates:
Description: Performance of the system has successfully recovered. This incident is resolved.
Status: Resolved
Impact: Minor | Started At: Nov. 21, 2024, 5:27 p.m.
Description: Our Hyperscaler experienced an unexpected host failure at 14:01 UTC today and automatically initiated the auto-recovery process to start the affected virtual machine on a different host. The affected instance was up and running again by 14:11 UTC.
Status: Resolved
Impact: None | Started At: Nov. 18, 2024, 2:16 p.m.
Description: ## Incident Description In the time from 13 Nov 2024, 09:04 PM UTC to 14 Nov 2024, 00:01 AM UTC, all customers experienced a disruption of data access through the OData bookmark endpoints. During that time, the OData bookmark endpoints would return an excessive amount of 400 errors. ## Incident Resolution The change causing the service disruption was rolled back at 14 Nov 2024, 00:01 AM UTC. ## Root Cause Analysis The code change that introduced the service disruption extended logs in case of OData endpoint failures. It was small in size, looked harmless as it did not affect business logic and caused no errors during local testing. We did not further test the code on a production environment and due to an unrelated issue, automated service monitoring was disabled. ## Preventative Measures We plan to reintroduce the service monitoring for 400 and 500 errors as soon as possible. We will also be extending the existing threshold-based alerts to include 400 errors.
Status: Postmortem
Impact: Minor | Started At: Nov. 13, 2024, 10:10 p.m.
Description: ## Incident Description On 2024-12-11 at 08:00 UTC, multiple customers in the EU region experienced incorrect KPI values. No customer data was affected. The service disruption lasted approximately 10 hours and 30 minutes until 2024-12-11 at 18:30 UTC. ## Incident Resolution Our team worked diligently to address the issue. We identified the affected customers and implemented a solution that corrected the KPI values. By 18:30, we had verified that all KPI values were accurate and the issue was entirely resolved. ## Root Cause Analysis The root cause of the problem was an overload of KPI calculation jobs that were not being processed due to limited resources and processing time. As the jobs grew, processing resources and processing time remained constant. We reached a point where calculations of KPI jobs for multiple customers were being dropped hence giving outdated KPI values. ## Preventative Measures We have identified the combination of factors that led to this oversight and will enforce the following practices to prevent similar issues in the future: * Increasing our system's capacity to handle a more significant number of KPI calculation jobs. * We have created an automated fallback script that can run the leftover jobs manually, decreasing downtime if the incident happens again. * We are already working on a much more efficient solution. When it is completed, we will replace the current KPI calculation implementation.
Status: Postmortem
Impact: Minor | Started At: Nov. 12, 2024, 10:13 a.m.
Description: ## Incident Description In the time from 2024-10-22 at 11:50 UTC until 14:18 UTC, all customers experienced an issue with creating Reports, Diagrams, Saved Searches, Dashboards and Excel Exports. The introduced regression prevented creation of above listed entities for all users during this time. No data loss happened, and updates of existing e.g. Diagrams were still possible. ## Incident Resolution The team deployed a fix for the introduced bug. The fix has been finally rolled out on 2024-10-22 at 14:18 UTC. ## Root Cause Analysis We introduced a change that inadvertently impacted downstream dependencies, resulting in issues with the creation of bookmarks. Although we prioritize comprehensive automated testing, this specific scenario was not covered by our test suite. ## Preventative Measures We hardened our testing pipelines to prevent similar regressions from happening again. Next to the improved testing pipelines, we will improve our monitoring to detect similar issues faster, and reduce the impact time. Additionally, we are working on improved rollout mechanisms to reduce the blast radius of incidents.
Status: Postmortem
Impact: Major | Started At: Oct. 22, 2024, 1:18 p.m.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage or down time. Join for free - no credit card required.
