Hosted Mender Status Page

Jul 9, 2026 · resolved Jul 10

This incident has been resolved by tuning the mbedTLS heap size.

Jun 24, 2026 · resolved Jun 24

# Brief service disruption on Hosted Mender \(EU\) On June 24, between 12:04 and 12:09 UTC, some customers on our EU region experienced a short interruption. During this five minute window, devices may have had trouble connecting, and parts of the web interface and API may have returned errors. ## What happened While cleaning up a configuration issue, we removed an internal duplicated definition \(the same set of kubernetes manifests rendered twice from Kustomize\). Our automation interpreted this as a request to remove and reinitialize two background components that handle messaging and caching \(NATS and Redis\). They were rebuilt automatically, but for about five minutes they were unavailable, which caused the disruption. ## What we are doing about it The automation completed the reconciliation loop and redeployed the background components automatically. We verified that normal operation was restored and confirmed all services are healthy. We are changing how we make this type of change so that components are never removed before their replacement is ready. We apologize for the disruption.

Jun 18, 2026 · resolved Jun 18

Incident Summary - 2026-06-18 What happened On June 18, between 18:46 UTC and approximately 19:00 UTC, some users may have experienced intermittent connectivity issues or elevated error rates when accessing Mender services from the EU cluster. The incident was triggered by a scheduled maintenance job running on the infrastructure hosting our services. This job - responsible for cleaning up unused container images across cluster nodes - ran simultaneously on all nodes and consumed a significant amount of CPU resources. This created resource contention with the ingress controller pods responsible for routing incoming traffic, causing them to become temporarily unresponsive to health checks and restart repeatedly. The repeated restarts reduced the number of healthy ingress endpoints below the threshold required to serve traffic across all availability zones, leading to degraded routing and elevated error rates for most of the requests. Resolution The ingress controller stabilized once the image cleanup job completed. This job is a new managed feature coming from the recent Kubernetes upgrades, and since it’s not a critical feature, we suspended it. Additional safeguards have been put in place to prevent ingress controller pods from being affected by resource pressure from unrelated workloads. What we are doing The image cleanup job has been permanently suspended. CPU resource limits have been tightened on the ingress layer to isolate it from competing workloads. Node pool capacity is being expanded with larger instances to provide additional headroom. We apologize for the disruption.

Jun 17, 2026 · resolved Jun 17

This incident has been resolved, the rollback worked and we'll apply the fix in the next release.

Apr 8, 2026 · resolved Apr 8

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.

Is Hosted Mender down right now?

No — Hosted Mender is up. All systems operational as of Jul 13, 11:46 PM UTC.

What is Hosted Mender's current status?

Hosted Mender: All Systems Operational. Alert24 checks Hosted Mender's status page continuously and can notify you the moment it changes.

How do I get alerted when Hosted Mender goes down?

Alert24 monitors Hosted Mender and 3,700+ other cloud and SaaS providers. When an outage is detected it updates your status page automatically and pages your on-call team — no manual checks. Start free at alert24.net.