Unify outage history

We record Unify's status every five minutes and have not recorded an incident from Unify's status page yet. We never invent one.

Uptime & history

Tracking since Jun 22, 2026
Currently up for 84d 15h since the last recorded problem.
Operational · 24h
100%
0 incidents · no downtime
288 checks
Operational · 7d
100%
0 incidents · no downtime
2015 checks
Operational · 30d
100%
0 incidents · no downtime
8638 checks
Operational · since Jun 22, 2026
99.11%
0 incidents · ≈19h 15m down · ≈11h 30m degraded
41480 checks

% of our checks that found Unify fully operational — a degraded check counts against it, because a slow or partly-broken service is not a working one. Down and degraded time are counted at our 5-minute check resolution, so both are approximate. Longer windows fill in as data accrues — we never show uptime we haven't measured.

Recent checks
oldernow

How Unify fails

Since Jun 27, 2026, Unify's status page has marked 5 Unify components as impaired, across 672 of our five-minute readings. Console accounts for the most: 263 readings (about 22 hours) on 2 days, 263 of them marked as an outage rather than degraded, most recently on Aug 26, 2026. Next is unify.ai, with 236 readings on 2 days.

ComponentOutageDegradedMaint.DaysLast
Console263——2Aug 26, 2026
unify.ai236——2Aug 26, 2026
Orchestra150——4Aug 26, 2026
Communication17——3Aug 26, 2026
Adapters6——1Aug 26, 2026

Counts are five-minute readings of Unify's own component statuses, recorded only when a component is not operational. Hours are readings times five minutes, so a gap in our recording would undercount, never overcount.

Incidents and their updates are Unify's own words from its status page, recorded every five minutes; we never add an inferred cause. AIDownCheck is independent and not affiliated with Unify.