Hosted Mender had 19 outages in the last 2 years totaling 131h 40m of downtime — averaging 0.8 incidents per month.
There were 19 Hosted Mender outages since August 9, 2025 totaling 131h 40m of downtime. Each is summarised below — incident details, duration, and resolution information.
An upstream provider notified that they are experiencing elevated error accessing API on EU region. It's possible that the Mender devices are unable to pull artifacts and deployments might fail. We're monitoring the upstream incident status.
The upstream provider reported their incident is resolved.
We are currently investigating the root cause of the issue.
We found a possible root cause with the new intermediate certificate of https://eu.hosted.mender.io with a different size. A tested workaround is to increase the mbedTLS heap size in your application's prj.conf: CONFIG_MBEDTLS_HEAP_SIZE=98304.
This incident has been resolved by tuning the mbedTLS heap size.
We've identified a regression affecting users who access Mender with a custom role (rather than the built-in administrator role). As a result, we have rolled back to the previous version. When a user with a custom role attempts to list software when creating a deployment, the request is rejected with There was an error while listing software forbidden by role-based access control Only users assigned a custom role were affected. Users with the built-in admin role were not affected. We apologize sincerely for this issue.
We rolled back the affected version and we're monitoring the results
This incident has been resolved, the rollback worked and we'll apply the fix in the next release.
We are currently investigating the issue
The issue has been identified and a fix is being implemented
A fix has been implemented and we are monitoring the results.
Mender UI was unavailable between 2026-04-08T13:16:15Z and 2026-04-08T13:42:09Z (26m) due to a breaking change to Google Analytics dependency leading to misconfiguration. The issue has been mitigated by temporarily disabling Google Analytics until a fix is deployed.
We just upgraded the hosted Mender US cluster to Kubernetes v1.33 with a blue/green approach. The new cluster (blue) right after the switch is experiencing issues with the rate limits for some customer. We are investigating the issue.
We rolled back to the old green cluster, still having the same issue.
We found the root cause, a fix has been implemented, and we're monitoring the results.
This incident has been resolved. However, a rate limit hot fix has been implemented, so we will schedule a new maintenance window soon, to apply the definitive fix.
This is the same incident as https://mender.statuspage.io/incidents/v85h4c0whdtc, which is keeping track of it for the hosted Mender EU The issue has been identified. A migration triggered by an upgrade caused an index to be removed prematurely. This in turn caused data corruption. We have initiated a database restore and rolled back the upgrade. We apologize for the inconvenience.
The restore to 08:10:00 UTC has completed and the server is scaled back up. We will continue to monitor the situation.
This incident has been resolved
We identified an issue with an upstream cloud provider. Unfortunately, even our statuspage was affected and we could not open this status page before now. Among the issues, we identified: * issues reaching the hosted Mender API server * emails not being sent * UI login not possible. The incident started at about 07:50 UTC
The cloud provider is fixing their issues, we can see that most of the hosted Mender services are back to full operation. We're continuing to monitor the issue. The email service is still not working.
This incident has been solved.
We are aware of an open incident with a Cloud Provider for the Artifacts Storage for both hosted Mender US and EU. You may experience slow artifact download or throttling. We're monitoring the upstream provider's status.
The upstream provider solved their issue.
On September 25th, we updated the internal Redis Cluster to a new provisioning model, but it turned out that this new deployment was applied without a proper Kubernetes Priority Class being set. So we found out that during a new regular hosted Mender deployment, the pods with higher priority and "preempt = true" could preempt Redis pods to be scheduled faster. We applied a fix on the 30th of September, but during the previous 5 days we had at least four Redis Cluster issues, which lasted 1-2 minutes each. We apologize for the issues this incident might have caused to you.
Customers are reporting issues with the remote terminal (Deviceconnect Service) which is frequently dropping the remote connection. We are investigating this issue.
The issue has been identified and we're working on a solution.
We rolled back the Deviceconnect service to the previous known working version. We're monitoring the metrics and the results.
This incident has been resolved.
When you try to upgrade your subscription in the Billing page, you can't see the Checkout button and so you cannot upgrade your subscription. We're investigating the issue.
We reverted a change for the billing page. Now the behavior should be the one before the version v4.1.0-saas.12 of hosted Mender.
We acknowledged that the documentation website docs.mender.io is currently not serving traffic. We are investigating the issue
The issue has been identified on the web server serving traffic; as a temporary workaround, we forcefully scaled out the web server and we're observing the results.
This incident has been resolved.