Is there an SAP LeanIX outage?
SAP LeanIX status: Systems Active
Last checked: 31 seconds ago
Get notified about any outages, downtime or incidents for SAP LeanIX and 1800+ other cloud vendors. Monitor 10 companies, for free.
Last checked: 31 seconds 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 From 2024-09-09 at 13:00 UTC until 17:00 UTC there was an issue with the Table view in Inventory, where the page would show a blank page after opening an Inventory Saved Search. After loading the Saved Search, going to list view and then switching back to table view has been a temporary workaround. ## Incident Resolution The incident was resolved after rolling back the identified change. ## Root Cause Analysis We've made a change to the Table UI component in Inventory to improve the performance and memory consumption of the application. The change replaced a certain logic for rendering the table to avoid unnecessary rendering runs and improve overall responsiveness. Unfortunately, there was an undetected issue when rendering the table after opening an existing Saved Search only, which led to the blank page. ## Preventative Measures We will expand our e2e testing coverage to include stricter validation checks and to prevent such visual regressions from happening again. For future changes like this one, we will use canary releases to mitigate potential customer impact as much as possible before releasing the change to everyone.
Status: Postmortem
Impact: Minor | Started At: Sept. 9, 2024, 11:30 a.m.
Description: This incident has been resolved.
Status: Resolved
Impact: Major | Started At: Sept. 7, 2024, 7:56 a.m.
Description: This incident has been resolved.
Status: Resolved
Impact: Minor | Started At: Sept. 6, 2024, 1:21 p.m.
Description: ## Incident Description On 4 September 2024, the Diagram back-end service was unavailable from`15:09 UTC` to `15:26 UTC`. During this time, the diagram editor could not be loaded, but already open diagrams could still be edited and saved, yet no new images could be inserted into diagrams and existing images in diagrams may not have loaded correctly. No data was lost during this incident. ## Incident Resolution A manual restart of the Diagram back-end service resolved the downtime. ## Root Cause Analysis The root cause was identified as a token-refresh call at `15:02:59 UTC` from the diagram service in the West-Europe-region to an external system which never received a response, yet also never timed out. This token refresh is intentionally wrapped with a database transaction, which includes a lock of the corresponding database table row. As the request never completed or timed out, this lock was never released. At `15:05:55 UTC`, an unrelated job was started in the same region, which required a complete lock of the same database table. This lock query never completed, but already started to lock table access for all other processes and requests. At `15:09:31 UTC`, the Diagram-service-internal database connection pool was full and all subsequent requests to the Diagram service received a `503 Service Unavailable` error. Until recently, this complete Diagram-service unavailability would not have prevented the diagram editor in the front-end from loading and users from being able to edit and save diagrams, as only some of the diagram-features are provided by this service \(such as the saving and storing of images included in diagrams\). Yet due to a recent change in the Diagram front-end code, these failed diagram service requests now led to the diagram editor not loading any more at all. ## Preventative Measures We have undertaken and planned the following measures to prevent such an incident from happening again: * Ensure that the diagram editor in the front-end still loads and is usable, albeit with a slightly reduced feature set, when the Diagram service is unavailable. \(Completed\) * Add timeouts to all calls to external systems to prevent long-running database transactions and locks. \(Completed\) * Ensure that all pending database transactions are completed/rolled back when the Diagram service containers are shut down during deployments.
Status: Postmortem
Impact: Major | Started At: Sept. 4, 2024, 1 p.m.
Description: This incident has been resolved.
Status: Resolved
Impact: Major | Started At: Aug. 18, 2024, 9:32 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.
