Incidents and maintenance reported on status page for Machine Park https://status.mp.liebherr.com/ https://d1lppblt9t2x15.cloudfront.net/logos/308aa00d05dc3e18a91cf895e12d6bc7.png https://status.mp.liebherr.com/ en https://status.mp.liebherr.com/incident/1083209 Tue, 06 Oct 2026 14:50:10 -0000 https://status.mp.liebherr.com/incident/1083209#79dfc5d33cae307652ad532dd204fcc2cfec42e647356943ce0400ba59fbe905 Incident Backend: svcmail recovered. https://status.mp.liebherr.com/incident/1083209 Tue, 06 Oct 2026 14:44:04 -0000 https://status.mp.liebherr.com/incident/1083209#c85209bc592fa03fc09a36a0c53b5be9ce6f75acf7e1e602ecb4c8257ace3b06 Incident Backend: svcmail went down. https://status.mp.liebherr.com/maintenance/936033 Fri, 26 Jun 2026 11:29:51 -0000 https://status.mp.liebherr.com/incident/936033#d2d3f4b296490fd8b3dcb8d2208d6f50f356ad4fb5edf652acf127b31106f002 Maintenance We need to upgrade infrastructure components on a new version. This may cause service interruptions. https://status.mp.liebherr.com/maintenance/932418 Tue, 23 Jun 2026 15:23:09 -0000 https://status.mp.liebherr.com/incident/932418#a7ace6bb07713f3f20cde3f81dcfbc5b3c56b25137da8501635258e5cf9cad9a Maintenance We need to update core components of our routing infrastructure. No downtime is planned. https://status.mp.liebherr.com/incident/920113 Wed, 10 Jun 2026 17:34:24 -0000 https://status.mp.liebherr.com/incident/920113#106e3fbda27dd0719d5c8b0781ef2a9b9d8ee8174b35f944defe41071856ad16 Incident mp.liebherr.com recovered. https://status.mp.liebherr.com/incident/920113 Wed, 10 Jun 2026 17:30:19 -0000 https://status.mp.liebherr.com/incident/920113#e7791993c31e7650628254e7b0a279affb9dcb4be9e11189b42de62ac929ef5e Incident mp.liebherr.com went down. https://status.mp.liebherr.com/incident/804265 Wed, 14 Jan 2026 12:21:00 -0000 https://status.mp.liebherr.com/incident/804265#7a9971dc5344d60603e0a11b573b64e4900a240bc46e66c34fbae5694d1e95fa Incident # Issue resolved > this is a test We have resolved the issue https://status.mp.liebherr.com/incident/804265 Wed, 14 Jan 2026 11:13:42 -0000 https://status.mp.liebherr.com/incident/804265#119f3a21ddb2bd373bd9346711495945b3ee2dc6126c2b88d9ee159f415cc034 Incident Backend: svcdata recovered. https://status.mp.liebherr.com/incident/804265 Wed, 14 Jan 2026 11:04:10 -0000 https://status.mp.liebherr.com/incident/804265#e8e5eb046cf479f3bac0e0a589ef3b15776fecd695c24fa444f756d3bac21789 Incident Backend: svcdata went down. https://status.mp.liebherr.com/incident/805095 Thu, 08 Jan 2026 09:52:00 -0000 https://status.mp.liebherr.com/incident/805095#18b99bfc910a85bdd8d6ac565fdc8a6fefa6565d8111d48cd3bb1c1ecb236147 Incident # Timeline of the first incident At 08:30 we started received first reports from users, that a login to the application was no longer possible. Monitoring start to show timeouts at 08:31 and waited 5 minutes before automatically creating an incident, which then happend at 08:36. By this time, it was clear that the outage was global for all users of MP and emergency troubleshooting was started. After initial investigation of basic network infrastructure, a failed infrastructure update, that was triggered at 08:00, was identified as the root cause. The failed update was initially not considered, because of the difference in timing, but as it turned out, actual changes were only applied to production at around 08:28.  An attempt to rollback the changes was unsuccessful, since the failed update left the network infrastructure in an inconsistent state, so we had to identify the faulty settings manually. At 09:10 the issue was identified and by 09:13 the application returned to a normal state and monitoring confirmed incident resolution. # Timeline of the second incident At 10:30 monitoring reported another outage, which was reported by users at 10:40. Since the team was still investigating the previous outage, the root cause was quickly related to the previous deployment again. The second incident was resolved by 10:46 and system went back to normal for the rest of the day. # Total service interruption With the two incidents combined, the service was interrupted for 1h 4min, leading to a total availability of 99,95% (last 90 days) # Technical details During the mentioned infrastructure update, terraform attempted to drop and recreate the VNET peering between the K8s network and our ApplicationGateway network, as well as the access policy of AppGW to our KeyVault resource (where SSL certificates are stored) After dropping the resources, an unexpected manual change of the K8s cluster crashed the deployment pipeline and prevented the recreation of the previously destroyed resources. This means terraform the deployment strategy seems to have given a faulty sequence of how the changes were applied. After these checks, we recreated the VNET peering and the access policy manually. https://status.mp.liebherr.com/incident/805095 Thu, 08 Jan 2026 09:30:00 -0000 https://status.mp.liebherr.com/incident/805095#4a190041580e1fe09a83691ca2e2d382fda749087072e5cf63ead5c5ab1ee698 Incident all services are down https://status.mp.liebherr.com/incident/805095 Thu, 08 Jan 2026 08:16:00 -0000 https://status.mp.liebherr.com/incident/805095#a391f03412185c81c5d6b85a74d6fcb8d777c60ae7a8152bb33283e6e621a898 Incident all services are running again https://status.mp.liebherr.com/incident/805095 Thu, 08 Jan 2026 07:37:00 -0000 https://status.mp.liebherr.com/incident/805095#db07a2401890b3de06774ea9bfa53e81209f47e8de8a77fcfce986ad516be6a4 Incident All services down https://status.mp.liebherr.com/maintenance/423001 Mon, 02 Sep 2024 10:00:00 -0000 https://status.mp.liebherr.com/incident/423001#94df5d69baafd0a698d2d069cbde2bd3c62d375b5548d5732da060b285ba0e85 Maintenance New Features are being deployed https://status.mp.liebherr.com/maintenance/417003 Wed, 21 Aug 2024 10:00:00 -0000 https://status.mp.liebherr.com/incident/417003#b3a641131b44f29263d6afcda47ce00a13feafc855d724940a96256a50f1a718 Maintenance Delivery Person in Charge https://status.mp.liebherr.com/maintenance/401777 Mon, 22 Jul 2024 10:04:00 -0000 https://status.mp.liebherr.com/incident/401777#f6c99a254e59217424318d24f91cc843c296a941697dc42a4a11e42951f83125 Maintenance Deployment of - Requirement 74574: Automatically create return shipping order https://status.mp.liebherr.com/maintenance/400577 Fri, 19 Jul 2024 09:06:02 -0000 https://status.mp.liebherr.com/incident/400577#8a32c9d41950f8012111078df0612b791f0aec18bf48b5d40b4889d6fc369a11 Maintenance Permissions issue patch applied