Zus Health incident

Some patient and appointment updates from athenahealth not making it to Zus

Minor Resolved View vendor source →

Zus Health experienced a minor incident on February 23, 2026 affecting Applications and EHR Integrations and 1 more component, lasting 23h 35m. The incident has been resolved; the full update timeline is below.

Started
Feb 23, 2026, 03:21 PM UTC
Resolved
Feb 24, 2026, 02:56 PM UTC
Duration
23h 35m
Detected by Pingoru
Feb 23, 2026, 03:21 PM UTC

Affected components

ApplicationsEHR Integrationsathenahealth

Update timeline

  1. investigating Feb 23, 2026, 03:21 PM UTC

    We are investigating some number of patient and appointment updates not arriving to Zus from athenahealth. This issue does not impact clinical data coming from athena and does not impact a users ability to view the ZAP in Athena. The biggest impact is likely to be on up-to-date patient history queries if we miss a newly created appointment.

  2. monitoring Feb 23, 2026, 08:47 PM UTC

    We’ve made an update to our data processing which has resolved this issue. We are going to keep this incident open as we continue to investigate the root cause and understand implications on historical data.

  3. resolved Feb 24, 2026, 02:56 PM UTC

    The root cause of the issue that prevented some Athena updates from reaching the Zus data store has been identified and addressed. A fix was deployed yesterday, and monitoring has been ongoing to confirm stability. Additional alerting has been implemented to ensure faster detection in the future, and plans are underway to introduce a self-healing mechanism to prevent data loss should a similar issue recur.