balena.io Incident History

1. resolvedNov 1 · 19:21 UTC

   We 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 email delivery service. If you clicked the link, don't worry, nothing will happen and there is nothing you need to do. Because of the increased volume of these emails, messages from no-reply@mail.balena-cloud.com may currently be sorted into spam. If you signed up, requested a password reset or manually triggered an email re-verification, please check your spam folder. Only act on emails you requested yourself, and if you are unsure whether an email is genuine, please contact us rather than clicking any links. We are running a full post-mortem and will share full details on this status page in due course. Thanks for your patience, and sorry again for any confusion or inconvenience.

Reported by balena.io on their status page.

1. resolvedOct 23 · 20:16 UTC

   This incident has been resolved.

Reported by balena.io on their status page.

1. resolvedOct 23 · 19:02 UTC

   This incident has been resolved.

Reported by balena.io on their status page.

1. postmortemOct 20 · 20:32 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. To prevent a recurrence, we’ve updated our unit tests to match our production logs backend structure, so changes like this will be caught before release.

Reported by balena.io on their status page.

1. ResolvedOct 19 · 19:30 UTC

   This incident has been resolved.

Reported by balena.io on their status page.