Is there an SAP LeanIX outage?
SAP LeanIX status: Systems Active
Last checked: 9 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: 9 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: This incident has been resolved.
Status: Resolved
Impact: Minor | Started At: Nov. 13, 2024, 10:10 p.m.
Description: This incident has been resolved.
Status: Resolved
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.
Description: ## Incident Description Following a deployment on 2024-10-14 at 14:09 UTC, all customers across all regions experienced an unresolved \(infinite\) loading indicator when attempting to access reports and diagrams from the bookmarks overview page. No customer data was affected. The service disruption lasted for approximately 40 minutes until 2024-10-14 at 14:49 UTC. ## Incident Resolution Reverting the code change that caused the incident resolved the issue. ## Root Cause Analysis A minor code change intended to extend our usage monitoring introduced a bug, which led to the infinite loading page, preventing the user to see any Reports or Diagrams. ## 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: 1. Add stricter rules in our CI/CD to prevent such code change of happening again. 2. Improve the current test scenarios during the deployment of new releases. 3. Enforce more thorough local and automated testing of all code changes.
Status: Postmortem
Impact: Major | Started At: Oct. 14, 2024, 2:39 p.m.
Description: ## Incident Description Between 2024-09-19 09:00 - 2024-09-26 15:30 UTC, notifications were dropped due to a failure in rendering notifications of type “fact sheet changes”. The issue affected customers who had enabled the “fact sheet details rendering” setting on a notification channel. ## Incident Resolution The incident was resolved by deploying a fixed version for notification rendering. ## Root Cause Analysis A modification to the rendering logic of fact sheet changes led to a failure in processing notifications. This behavior went undetected before the release due to environment differences between test and production. ## Preventative Measures We enhanced the automated tests for notification processing to prevent similar incidents in the future. We also improved internal alerting to be notified earlier for failing notification processing.
Status: Postmortem
Impact: None | Started At: Sept. 19, 2024, 7 a.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.
