Is Zus Health down?

Zus experienced elevated error rates on our Carequality connector starting at ~5 pm eastern on 8/17/2026. We believe these errors have died down for upcoming jobs, and we will rerun impacted jobs tomorrow. If a job you submitted has errored and the delay is impacting your operations: use the Request Records button in the ZAP to bypass this queue. You will not be charged for the additional job.

We have identified and resolved the source of these job errors, and have begun the process of replaying impacted jobs – this process will complete today. If a job you submitted has errored and the delay is impacting your operations: use the Request Records button in the ZAP to bypass this queue. You will not be charged for the additional job.

The first batch of error recovery processing has completed successfully. Zus will be completing the kickoff of all other errored jobs today, with expected completion over the weekend.

All errored jobs have been kicked off for a rerun through the system, and are flowing successfully, we expect completion within the next 12-20 hours, many have completed already.

All errored jobs have been re-run and completed. The system is functioning normally.

Due to a buildup of traffic in our non-priority queue, chart builds are operating with delays of approximately 30 hours. Please contact your account contact if this is impacting your operations. Priority chart builds, included requests submitted through the Zus App and refreshes for STAT appointments, are not impacted.

Non-priority jobs submitted to the queue are continuing to complete more slowly than normal. Processing times will remain elevated for the next several days, and may climb to 2-3 days. If a job you submitted has not started and the delay is impacting your operations: use the Request Records button in the ZAP to bypass this queue. You will not be charged for the additional job.

Non-priority jobs continue to be delayed, but we are working on clearing the backlog and expect resolution by mid-week. If a job you submitted has not started and the delay is impacting your operations: use the Request Records button in the ZAP to bypass this queue. You will not be charged for the additional job.

We expect non-priority job latencies to return to normal within a day. However, if a job you submitted has not started and the delay is impacting your operations: use the Request Records button in the ZAP to bypass this queue. You will not be charged for the additional job.

We are now regularly seeing and processing jobs with a latency of 1 day or less. Delayed jobs with longer latencies can be attributed to the minor incident of elevated error rates on CareQuality and will be addressed within those recovery efforts.

We are currently investigating reports of potential issues with EHR Integrations. At this time we have not confirmed an incident - our team is actively looking into the situation and will share an update as soon as we know more. Additional Context: The embedded ZAP and data synchronization are down for Athena. Edit: the title of this incident was updated at 12:03pm ET

We have identified the root cause of the issues impacting EHR integrations. For athenahealth, the ZAP is not functional. We are working to resolve the root cause, which we are aware of. Data exchange is also currently down. Data exchange for all other EHR integrations is currently delayed. We are working to clear these delays. We can confirm that the embedded ZAP was not functional in EHRs other than athenahealth from 10:48am-11:40am ET. This is now resolved.

We have resolved the underlying issues impacting all EHR integrations. The athenahealth integration is now fully functional, and data exchange is restored. All data exchange delays are resolved across EHRs, and ongoing data syncing is restored. We will continue to monitor these integrations to ensure smooth function going forward.

We can confirm that all data delays that were caused by the incident are now resolved. Any data that was not exchanged during this time has now been replayed and all systems are running as expected.

We are currently investigating reports of potential issues with ZusHooks. At this time we have not confirmed an incident - our team is actively looking into the situation and will share an update as soon as we know more. Additional Context: We are investigating increased Zushooks latency.

ZusHooks deliveries were delayed by up to 2 hours within the last 2 hours. We have resolved the root cause and messages are now delivering normally.

We are currently investigating reports of potential issues with Lenses and Enrichment. At this time we have not confirmed an incident - our team is actively looking into the situation and will share an update as soon as we know more. Edit: The title of this incident was updated on August 4 at 4:50pm ET.

We have identified an issue in processing data in the Risk product. Risk data was not processed between 5:00pm ET on 8/3/2026 through 12:00pm ET on 8/4/2026. All Risk gaps impacted during this period are being reprocessed. There was some loss of data during this time, which we are in the process of identifying and restoring. We will close the incident when reprocessing is complete and provide an update on data restoration.

This incident has been resolved, and all user updates have been restored.