Live / balena.io / Incident
balena.io: Elevated API Errors
balena.io · balena.ioMinor incidentResolved2026-10-23 19:02 UTC
Public — what happened
Summary
balena.io reported a minor incident titled "Elevated API Errors," saying that more requests than normal to its API were failing. It said it began looking into the problem at 15:34 UTC on 2026-10-23, and by 15:59 UTC it said it had found the issue and was working on a fix. At 16:38 UTC balena.io said a fix was in place and it was watching the results, and the incident was marked resolved at 19:02 UTC. The company did not say who was affected or give details of what caused the errors.
Affected
API
Timeline
- Started — 2026-10-23 15:34 UTC
- Investigating — 2026-10-23 15:34 UTC
- Identified — 2026-10-23 15:59 UTC
- Monitoring — 2026-10-23 16:38 UTC
- Resolved — 2026-10-23 19:02 UTC · 3h 28m 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.