Hosted Mender incident

Mender Server EU issues with API services

Major Resolved View vendor source →

Hosted Mender experienced a major incident on June 24, 2026 affecting Hosted Mender EU, lasting 22m. The incident has been resolved; the full update timeline is below.

Started
Jun 24, 2026, 12:10 PM UTC
Resolved
Jun 24, 2026, 12:32 PM UTC
Duration
22m
Detected by Pingoru
Jun 24, 2026, 12:10 PM UTC

Affected components

Hosted Mender EU

Update timeline

  1. investigating Jun 24, 2026, 12:10 PM UTC

    We are currently investigating this issue.

  2. identified Jun 24, 2026, 12:18 PM UTC

    The issue has been identified: there was an issue with the Redis and NATS deployments. A fix has been implemented and we're restarting the impaired services.

  3. monitoring Jun 24, 2026, 12:23 PM UTC

    The affected services have been restarted and we're monitoring the results.

  4. resolved Jun 24, 2026, 12:32 PM UTC

    This incident has been resolved.

  5. postmortem Jun 24, 2026, 01:34 PM UTC

    # 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.