Balena status history
Current state: operational — “All Systems Operational” per https://status.balena.io (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do Balena incidents last?
From 27 incidents with a vendor-posted start and resolve time. Longest on record: Elevated GIT/Application Builder Errors — 21.1 days (2026-03-31 12:55 UTC). Excluded, never estimated: nothing. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.
Incidents on record (27)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-07-27 16:49 UTC | Elevated Error on Public Device Url | resolved | minor | 1 h 52 min |
| 2026-07-06 13:47 UTC | Elevated API Errors | postmortem | major | 50 min |
| 2026-07-02 14:03 UTC | Elevated API Errors | resolved | major | 7 d 4 h |
| 2026-05-05 18:12 UTC | Elevated API Errors | postmortem | major | 2 h 51 min |
| 2026-03-31 12:55 UTC | Elevated GIT/Application Builder Errors | postmortem | minor | 21 d 3 h |
| 2026-03-24 12:43 UTC | Elevated API Errors | resolved | major | 25 h 23 min |
| 2026-03-23 16:57 UTC | Builder Degraded performance | postmortem | minor | 44 h 20 min |
| 2026-03-03 17:44 UTC | Elevated Dashboard Errors | postmortem | minor | 2 h 33 min |
| 2026-02-26 19:20 UTC | Elevated Device SSH Errors | postmortem | minor | 8 h 18 min |
| 2026-02-24 17:27 UTC | Elevated Device SSH Errors | postmortem | critical | 3 h 27 min |
| 2026-02-10 09:33 UTC | Elevated Delta Errors | postmortem | major | 14 h 28 min |
| 2026-02-10 04:05 UTC | Elevated Cloudlink Errors | postmortem | critical | 3 h 51 min |
| 2026-02-04 20:43 UTC | Elevated GIT/Application Builder Errors | postmortem | minor | 41 h 09 min |
| 2026-01-28 18:54 UTC | Elevated API Errors | postmortem | major | 3 h 12 min |
| 2026-01-28 01:00 UTC | Partial API Outage | postmortem | major | 0 min |
| 2025-12-23 16:32 UTC | Degraded Performance | resolved | minor | 17 h 06 min |
| 2025-12-05 09:05 UTC | An upstream provider outage is affecting connectivity to balenaCloud services | resolved | critical | 31 min |
| 2025-11-12 09:13 UTC | Builder partially degraded service | postmortem | minor | 10 h 45 min |
| 2025-10-20 08:45 UTC | Elevated GIT/Application Builder Errors | resolved | minor | 14 h 18 min |
| 2025-10-01 13:30 UTC | Elevated Device URLs/VPN Errors | resolved | none | 0 min |
| 2025-09-30 19:47 UTC | Elevated Device VPN Tunnel Errors | postmortem | major | 2 h 08 min |
| 2025-09-17 20:10 UTC | Elevated Device URLs/VPN Errors | postmortem | critical | 1 h 51 min |
| 2025-09-16 02:33 UTC | Builder partially degraded service | postmortem | minor | 9 d 6 h |
| 2025-09-10 13:47 UTC | Elevated API Errors | postmortem | none | 8 h 20 min |
| 2025-08-27 16:48 UTC | Elevated Dashboard Errors | postmortem | minor | 3 h 56 min |
| 2025-08-19 11:20 UTC | Elevated API Errors | resolved | minor | 8 min |
| 2025-08-14 13:52 UTC | Partial API Outage | resolved | major | 1 h 08 min |
Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).
Watch Balena with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"balena"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}