Vendor Status Watch

← all vendors

Balena status history

Current state: operational — “All Systems Operational” per https://status.balena.io (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.

0incidents, last 30 days
3incidents, last 90 days
27incidents on record
Incidents per week, last 12 weeks:

How long do Balena incidents last?

3.9 hmedian incident duration27 measured
44.3 h90th percentile1 in 10 ran longer
2.9 hmedian, major/critical only13 incidents

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)

StartedIncidentStatusImpactDuration
2026-07-27 16:49 UTCElevated Error on Public Device Urlresolvedminor1 h 52 min
2026-07-06 13:47 UTCElevated API Errorspostmortemmajor50 min
2026-07-02 14:03 UTCElevated API Errorsresolvedmajor7 d 4 h
2026-05-05 18:12 UTCElevated API Errorspostmortemmajor2 h 51 min
2026-03-31 12:55 UTCElevated GIT/Application Builder Errorspostmortemminor21 d 3 h
2026-03-24 12:43 UTCElevated API Errorsresolvedmajor25 h 23 min
2026-03-23 16:57 UTCBuilder Degraded performancepostmortemminor44 h 20 min
2026-03-03 17:44 UTCElevated Dashboard Errorspostmortemminor2 h 33 min
2026-02-26 19:20 UTCElevated Device SSH Errorspostmortemminor8 h 18 min
2026-02-24 17:27 UTCElevated Device SSH Errorspostmortemcritical3 h 27 min
2026-02-10 09:33 UTCElevated Delta Errorspostmortemmajor14 h 28 min
2026-02-10 04:05 UTCElevated Cloudlink Errorspostmortemcritical3 h 51 min
2026-02-04 20:43 UTCElevated GIT/Application Builder Errorspostmortemminor41 h 09 min
2026-01-28 18:54 UTCElevated API Errorspostmortemmajor3 h 12 min
2026-01-28 01:00 UTCPartial API Outagepostmortemmajor0 min
2025-12-23 16:32 UTCDegraded Performanceresolvedminor17 h 06 min
2025-12-05 09:05 UTCAn upstream provider outage is affecting connectivity to balenaCloud servicesresolvedcritical31 min
2025-11-12 09:13 UTCBuilder partially degraded servicepostmortemminor10 h 45 min
2025-10-20 08:45 UTCElevated GIT/Application Builder Errorsresolvedminor14 h 18 min
2025-10-01 13:30 UTCElevated Device URLs/VPN Errorsresolvednone0 min
2025-09-30 19:47 UTCElevated Device VPN Tunnel Errorspostmortemmajor2 h 08 min
2025-09-17 20:10 UTCElevated Device URLs/VPN Errorspostmortemcritical1 h 51 min
2025-09-16 02:33 UTCBuilder partially degraded servicepostmortemminor9 d 6 h
2025-09-10 13:47 UTCElevated API Errorspostmortemnone8 h 20 min
2025-08-27 16:48 UTCElevated Dashboard Errorspostmortemminor3 h 56 min
2025-08-19 11:20 UTCElevated API Errorsresolvedminor8 min
2025-08-14 13:52 UTCPartial API Outageresolvedmajor1 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
}