LumApps incident
Access issue on LumApps EU-MS-1 (ms-cell-001) & JP-MS-2 (ms-cell-002)
LumApps experienced a major incident on October 29, 2025 affecting ms-cell-001 - LumApps (ms-cell-001 - LumApps) and ms-cell-002 - LumApps (ms-cell-002 - LumApps), lasting 15h 23m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Oct 29, 2025, 03:57 PM UTC
We are experiencing issue on the cells LumApps EU-MS-1 (ms-cell-001) and cell LumApps EU-MS-2 (ms-cell-002). Our team is investigating. We will update as soon as possible.
- investigating Oct 29, 2025, 04:18 PM UTC
The current investigation suggests the issue may be related to our cloud provider, Azure. We are actively engaging with Azure support to confirm the root cause and determine the appropriate mitigation steps. We will provide another update as soon as we have confirmed details from Azure or...
- investigating Oct 29, 2025, 04:27 PM UTC
Our team has confirmed that the disruption is a result of an ongoing issue with our cloud provider, Microsoft Azure. We have correlated our internal data with the information provided on the Azure Service Health Dashboard. Impact and Azure Status: <a href="https://azure.status....
- investigating Oct 29, 2025, 05:13 PM UTC
This is an update on the incident affecting EU-MS-1 (ms-cell-001) and JP-MS-2 (ms-cell-002). The root cause remains confirmed as a dependency on an ongoing Microsoft Azure platform issue. Latest Information from Azure: We are forwarding the latest status update provided by Azure...
- investigating Oct 29, 2025, 05:46 PM UTC
This is the latest update regarding the incident affecting EU-MS-1 (ms-cell-001) and JP-MS-2 (ms-cell-002). The disruption is still tied to the ongoing issue with our cloud provider, Microsoft Azure. Latest Information from Azure: Below is the newest status update we have...
- investigating Oct 29, 2025, 06:22 PM UTC
This is the latest update regarding the incident affecting EU-MS-1 (ms-cell-001) and JP-MS-2 (ms-cell-002). The disruption is still tied to the ongoing issue with our cloud provider, Microsoft Azure. Latest Information from Azure: Below is the newest status update we have...
- investigating Oct 29, 2025, 07:00 PM UTC
This is the most recent update on the incident affecting EU-MS-1 (ms-cell-001) and JP-MS-2 (ms-cell-002). Latest Status from Azure: We have received the following new status update from our provider, Microsoft Azure: Impact and Azure Status: https://azure.status.microsoft/...
- investigating Oct 29, 2025, 07:38 PM UTC
Our cloud provider, Microsoft Azure, has confirmed they have initiated a recovery process for the underlying issue. This is a crucial step towards full resolution. Latest Status from Azure: We have received the following new status update from our provider, Microsoft Azure: ...
- investigating Oct 29, 2025, 08:10 PM UTC
This is an update on the incident affecting EU-MS-1 (ms-cell-001) and JP-MS-2 (ms-cell-002). While Azure has initiated its recovery process, we have received updated information indicating that the full resolution and stabilization timeline will be longer than initially anticipated. ...
- investigating Oct 29, 2025, 09:52 PM UTC
While our cloud provider, Microsoft Azure, has not yet indicated a full resolution on their status page, our internal monitoring and testing are showing a marked and sustained improvement in product behavior across both affected cells. This suggests that the recovery actions Azure...
- resolved Oct 30, 2025, 07:21 AM UTC
Our team has confirmed that the underlying issue with the cloud provider, Microsoft Azure, is now in the final stages of resolution on their side. Information are available at https://azure.status.microsoft/en-us/status/history/ Tracking ID: YKYN-BWZ. Our own cells have been stable...