Live / balena.io / Incident
balena.io: Elevated API Errors
balena.io · balena.ioMinor incidentResolved2026-10-19 19:30 UTC
Public — what happened
Summary
balena.io said it saw a higher-than-normal number of errors affecting its API, specifically around device logs, starting at 18:30 UTC on 2026-10-19, and it classed the incident as minor. About twenty minutes later the company said it had found the cause and taken steps to restore the system, and it reported that log stability and reporting were improving. The incident was marked resolved at 19:30 UTC the same day.
Affected
API, Dashboard
Timeline
- Started — 2026-10-19 18:30 UTC
- Investigating — 2026-10-19 18:30 UTC
- Monitoring — 2026-10-19 18:50 UTC
- Resolved — 2026-10-19 19:30 UTC · 1h after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach balena.io against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for balena.io: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the balena.io report →
More from balena.io
Covered in The Squid’s Ink, Week 44, 2026, our weekly internet health report.