File Storage Access Disruption — Multiple Regions

Update timeline

1. investigating Apr 22, 2026, 05:13 PM UTC

   We are currently investigating an issue affecting file storage operations across multiple Mendix Cloud environments. Affected applications may experience errors when uploading or downloading files. Impact: Applications may be unable to read or write files stored in the platform's object storage. Affected regions: Multiple Mendix Cloud regions are impacted. We are assessing the full scope. Our engineering team is actively investigating the root cause and working toward a resolution. No data has been lost — existing files remain intact. Next update: We will provide an update within 30 minutes.

2. identified Apr 22, 2026, 05:38 PM UTC

   We have identified the issue and are working on a fix. Next update: We will provide an update within 30 minutes.

3. identified Apr 22, 2026, 05:57 PM UTC

   We have identified the root cause of the file storage access disruption. A fix has been prepared and is currently being rolled out. Due to the number of affected regions, the rollout may take some time to propagate across all environments. Applications should gradually regain full file storage access as the fix is applied to each region. Existing files and data remain unaffected. Next update: We will provide another update once the rollout is complete.

4. monitoring Apr 22, 2026, 06:17 PM UTC

   The fix for the file storage access issue has been rolled out across all affected regions. We are now monitoring the situation. If your application is still experiencing file storage errors, please restart or redeploy your environment without Zero Downtime deployment (ZDT). We will continue monitoring and provide a final update once we have confirmed full resolution.

5. resolved Apr 22, 2026, 06:59 PM UTC

   The file storage access disruption has been resolved. We have confirmed that no new applications are being affected. If your application is still experiencing file storage errors, please restart or redeploy your environment without Zero Downtime deployment (ZDT). If the issue persists after restarting, please contact our support team for further assistance.