Is there an SAP LeanIX outage?
SAP LeanIX status: Systems Active
Last checked: 5 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: 5 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: ## 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.
Description: ## Incident Description On September 19, 2024, at 06:30 PM to September 20 at 05:30 PM UTC, the SAP LeanIX integration to Signavio was unresponsive and unable to perform actions. ## Root Cause Analysis The incident was caused by a malformed URL used by one of our microservices. The faulty behavior was triggered by a DNS change, which rerouted the requests of the microservice through a different backend, with stricter URL handling. The rerouting to the new backend caused the requests to fail due to the malformed URL. ## Incident Resolution The incident was resolved by rolling back the DNS changes temporarily. The root cause was then addressed by fixing the URL creation process to ensure no malformed URLs are in use. ## Preventative Measures To prevent a recurrence of similar issues, we have implemented mechanisms that ensure no malformed URLs are used within the affected microservice. Additionally, we will enhance monitoring and alerting systems to quickly detect and respond to similar issues in the future.
Status: Postmortem
Impact: Minor | Started At: Sept. 19, 2024, 5:30 a.m.
Description: This incident has been resolved.
Status: Resolved
Impact: Minor | Started At: Sept. 18, 2024, 4:38 p.m.
Description: ## Incident Description On November 13, 2024, between 09:26 and 09:32 UTC, our Multi Tenancy Manager \(MTM\) API in EU experienced an outage. This disruption prevented users from logging in and accessing their workspaces. ## Incident Resolution The system recovered itself. ## Root Cause Analysis A process in the MTM service locked a database table for updates, which blocked other requests from being executed. After the lock was released, requests could access the table again. ## Preventative Measures We are enhancing our monitoring of long-running processes and the locks they create on the database.
Status: Postmortem
Impact: Major | Started At: Sept. 9, 2024, 3:08 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.
