Balena incident

Elevated API Errors

Resolved after 1 hour, affecting API and Dashboard, on October 19, 2026.

postmortem Oct 20, 2026, 08:32 PM UTC

A change to the caching mechanism inadvertently omitted our logs backend read-context handling, causing customer log queries to fail. Log ingestion was unaffected, and no logs were lost.

Started
Oct 19, 2026, 06:30 PM UTC
Resolved
Oct 19, 2026, 07:30 PM UTC
Duration
1h
Detected by Pingoru
Oct 19, 2026, 06:30 PM UTC

Affected components

APIDashboard

Update timeline

  1. investigating Oct 19, 2026, 06:30 PM UTC

    We're experiencing an elevated level of API errors (device logs) and are currently looking into the issue.

  2. monitoring Oct 19, 2026, 06:50 PM UTC

    We have identified the cause and have taken measures for system restoring, we are monitoring and seeing improvements on logs stability and reporting

  3. resolved Oct 19, 2026, 07:30 PM UTC

    This incident has been resolved.

  4. postmortem Oct 20, 2026, 08:32 PM UTC

    A change to the caching mechanism inadvertently omitted our logs backend read-context handling, causing customer log queries to fail. Log ingestion was unaffected, and no logs were lost.

Your product runs on more than Balena

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →