balena.io Outage History

27 incidents recorded over the last 365 days, 23 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Every Recorded balena.io Incident

balena.io incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Nov 9, 2026balenaCloud infrastructure maintenanceWe will be undergoing scheduled maintenance during this time.3h 0mScheduled
Nov 1, 2026Email verification sent to many accountsWe apologize for any alarm caused by unexpected emails. We can confirm that this was not a security breach, no-one has accessed your account or our backend systems. The email was caused by a configuration issue in our…1h 51mResolved
Oct 23, 2026Elevated GIT/Application Builder ErrorsThis incident has been resolved.3h 10mResolved
Oct 23, 2026Elevated API ErrorsThis incident has been resolved.3h 27mResolved
Oct 19, 2026Elevated API ErrorsA 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. To prevent a recurrence, we’ve…1h 0mResolved
Sep 28, 2026Elevated Dashboard ErrorsOn September 28, the balenaCloud dashboard failed to load because some API requests stopped responding. A runtime upgrade to our API interacted badly with a legacy storage library, causing requests that depended on it…1h 50mResolved
Jul 27, 2026Elevated Error on Public Device UrlUnusual load on the proxy, caused some degraded performances on the device URL. Everything is now working properly.1h 52mResolved
Jul 6, 2026Elevated API ErrorsA routine version upgrade to a backend cache changed how the API handled its request queues. Under unusually heavy request load, those queues filled up and the API started dropping traffic, returning timeouts and…50 minResolved
Jul 2, 2026Elevated API ErrorsThis incident has been resolved.172h 20mResolved
Jun 14, 2026balenaCloud infrastructure maintenanceThe scheduled maintenance has been completed.3h 0mScheduled
May 5, 2026Elevated API ErrorsA vulnerability mitigation update required replacing compute cluster nodes, which, when applied, rolled back due to a timeout. This caused some workloads \(API, delta, builder\) to become temporarily unavailable and…2h 51mResolved
Apr 20, 2026balenaCloud infrastructure maintenanceThe scheduled maintenance has been completed.2h 0mScheduled
Mar 31, 2026Elevated GIT/Application Builder ErrorsStarting around March 11, some cloud builds began failing intermittently with no such image errors. The failures were non-deterministic and affected all architectures. At peak, some users saw around 50% failure…507h 35mResolved
Mar 24, 2026Elevated API ErrorsWe experienced degraded API performance due to an internal configuration change that unintentionally increased system load, resulting in slower response times and reduced request capacity. Our team identified the issue…25h 23mResolved
Mar 23, 2026Builder Degraded performanceBetween March 11 and March 25, some cloud builds experienced intermittent failures with "no such image" errors. The issue was non-deterministic and did not affect all builds. We've identified a likely contributing…44h 20mResolved
Mar 3, 2026Elevated Dashboard ErrorsWe identified an issue in Dashboard v32.2.0, released on March 2, 2026, where opening the dashboard via a direct link to certain pages \(such as billing or other account management pages\) could result in being…2h 33mResolved
Feb 26, 2026Elevated Device SSH ErrorsOn February 26, 2026 at approximately 19:00 UTC, users began experiencing failures when connecting to their devices via balena device ssh. The command returned a generic "host error" with no further detail. The issue…6h 25mResolved
Feb 24, 2026Elevated Device SSH ErrorsOn Feb 24, 2026 around ~17:20 UTC, a routine infrastructure deployment caused intermittent availability issues with Device URLs and web terminal access. Devices remained online and functional throughout, and CLI-based…3h 27mResolved
Feb 10, 2026Elevated Delta Errorsv2 delta generation service experienced failures from ~21:15 UTC Feb 9 to ~10:00 UTC Feb 10, 2026, due to a missing configuration dependency during a logic change. **Impact:** * v2 delta generation requests failed to…14h 28mResolved
Feb 10, 2026Elevated Cloudlink ErrorsBalena devices were unable to connect to Cloudlink on February 10, 2026, from approximately 02:26 GMT to 07:11 GMT due to an expired server certificate. Devices that were already connected to Cloudlink were unaffected…3h 51mResolved
Feb 4, 2026Elevated GIT/Application Builder ErrorsDelta generation service experienced degraded performance from ~0900 UTC Feb 4 to ~1700 UTC Feb 5, 2026, due to 32-bit address space limitations affecting large image delta processing. **Impact:** * Delta generation…41h 9mResolved
Jan 28, 2026Elevated API Errors### What Happened On January 28, our API experienced degraded performance due to a cascading pod failure triggered by infrastructure inconsistency. ### Root Cause We unexpectedly had one node running on an older…3h 12mResolved
Jan 28, 2026Partial API OutageBetween 00:35 GMT and 01:00 GMT on January 28, 2026, users may have experienced intermittent connectivity issues with the balenaCloud API. Consequently, users may have had difficulty using the balenaCloud dashboard, and…-40 minResolved
Dec 23, 2025Degraded PerformanceInsufficient AWS compute capacity overloaded the remaining nodes. This high load caused readiness probes to fail, triggering API restarts that created a feedback loop of increasing pressure.17h 6mResolved
Dec 5, 2025An upstream provider outage is affecting connectivity to balenaCloud servicesThis incident has been resolved.31 minResolved
Nov 24, 2025balenaCloud infrastructure maintenanceThe scheduled maintenance has been completed.3h 0mScheduled
Nov 12, 2025Builder partially degraded service### Summary On November 12, 2025, we experienced an incident causing increased build failures. This was traced to a significant network issue upstream of our hosting provider, which was outside their direct control…10h 45mResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next balena.io incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This balena.io Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before balena.io acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single balena.io outage in this window ran 21d 3h, against a mean recovery of 1d 9h. If you depend on balena.io in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.