Zus Health Outage History
Zus Health is up right nowPingoru has recorded 35 incidents for Zus Health: 35 in the last 12 months and 10 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 2 | 285 of 720 (40%) |
| May 2026 | 5 | 103 of 744 (14%) |
| June 2026 | 3 | 51 of 720 (7%) |
| July 2026 | 6 | 397 of 744 (53%) |
| August 2026 | 6 | 281 of 744 (38%) |
| September 2026 | 1 | 1 of 720 (0%) |
| October 2026 | 2 | 12 of 592 (2%) |
Incidents, newest first
Minor October 21, 2026 Generated Patient Summaries failing intermittently 7h 1m Applications, Zus App
Started Oct 21, 2026, 02:06 PM UTC· resolved Oct 21, 2026, 09:07 PM UTC
- investigating Oct 21, 2026, 02:06 PM UTC
We are aware of an intermittent issue with Generated Patient Summaries (GPS) due to an upstream provider issue. We are working with the provider to resolve the issue and will provide updates as we get them
- investigating Oct 21, 2026, 05:58 PM UTC
We continue to work with upstream dependencies on resolving this incident. Error rates have reduced but are not yet to zero. If any user experiences an issue with GPS, reloading the page or clicking the “Generate” button again should result in successful summary generation.
- monitoring Oct 21, 2026, 08:51 PM UTC
Intermittent errors appear to have subsided. We will leave this incident open in monitoring so we can confirm that all systems are fully operational.
- resolved Oct 21, 2026, 09:07 PM UTC
We have confirmed with our upstream provider that the issue causing this incident has resolved.
Minor October 20, 2026 GPS Experiencing Intermittent Failures 5h 20m Applications, Zus App
Started Oct 20, 2026, 02:14 PM UTC· resolved Oct 20, 2026, 07:35 PM UTC
- investigating Oct 20, 2026, 02:14 PM UTC
GPS is experiencing intermittent failures to generate new summaries due to an underlying service dependency. We are monitoring the health of this service and will update when it recovers.
- investigating Oct 20, 2026, 04:56 PM UTC
GPS is still experiencing intermittent issues generating new summaries. We are working with the dependency team for resolution.
- resolved Oct 20, 2026, 07:35 PM UTC
Intermittent GPS errors have now resolved. We’ll continue to monitor our services to ensure GPS operates smoothly.
Minor September 24, 2026 Commonwell data retrieval errors 1h Data Connections, CommonWell Network
Started Sep 24, 2026, 08:00 PM UTC· resolved Sep 24, 2026, 09:00 PM UTC
- investigating Sep 25, 2026, 07:24 PM UTC
We experienced errors in data retrieval from CommonWell between 4pm and 5pm eastern time yesterday for jobs which registered a new patient in CommonWell. Approximately 25% of all CommonWell jobs run during this time entered an error status. All affected jobs had been successfully rerun by 6:30pm eastern time. No customer action is required, and the system has operated normally since.
Minor August 24, 2026 Elevated errors in FQS 55m Applications, Zus App, Data APIs, FHIR APIs
Started Aug 24, 2026, 09:26 PM UTC· resolved Aug 24, 2026, 10:21 PM UTC
- investigating Aug 24, 2026, 09:26 PM UTC
The FQS API is returning elevated rates of 502 errors. This affects the REST and GraphQL APIs, Zus App, and reciprocity requests
- monitoring Aug 24, 2026, 10:13 PM UTC
The team rolled back a bad deployment and error rates have dropped. We are continuing to monitor.
- resolved Aug 24, 2026, 10:21 PM UTC
We have addressed the root cause of the FQS errors, and services are back to normal.
Minor August 17, 2026 Elevated error rates on Carequality 4d 22h Data Connections, Carequality Network
Started Aug 17, 2026, 09:00 PM UTC· resolved Aug 22, 2026, 07:15 PM UTC
- investigating Aug 18, 2026, 10:10 PM UTC
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.
- monitoring Aug 20, 2026, 01:18 PM UTC
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.
- investigating Aug 21, 2026, 02:47 PM UTC
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.
- investigating Aug 21, 2026, 08:34 PM UTC
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.
- resolved Aug 22, 2026, 07:15 PM UTC
All errored jobs have been re-run and completed. The system is functioning normally.
Minor August 12, 2026 Non-priority jobs operating with delays 8d 16h Data Connections, CommonWell Network, Carequality Network
Started Aug 12, 2026, 10:49 PM UTC· resolved Aug 21, 2026, 03:05 PM UTC
- investigating Aug 12, 2026, 10:49 PM UTC
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.
- investigating Aug 13, 2026, 04:41 PM UTC
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.
- investigating Aug 17, 2026, 03:39 PM UTC
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.
- investigating Aug 20, 2026, 01:10 PM UTC
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.
- resolved Aug 21, 2026, 03:05 PM UTC
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.
Major August 12, 2026 Incident impacting the embedded ZAP in EHRs. 3h 5m Applications, EHR Integrations, athenahealth, Elation Health and 3 more
Started Aug 12, 2026, 02:31 PM UTC· resolved Aug 12, 2026, 05:36 PM UTC
- investigating Aug 12, 2026, 02:31 PM UTC
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
- investigating Aug 12, 2026, 03:57 PM UTC
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.
- resolved Aug 12, 2026, 05:34 PM UTC
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.
- investigating Aug 13, 2026, 01:43 PM UTC
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.
Major August 4, 2026 Potential issue with ZusHooks 21m ZusHooks
Started Aug 04, 2026, 09:16 PM UTC· resolved Aug 04, 2026, 09:38 PM UTC
- investigating Aug 04, 2026, 09:16 PM UTC
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.
- resolved Aug 04, 2026, 09:38 PM UTC
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.
Major August 3, 2026 Risk Gaps not being calculated as expected 1d 16h Lenses and Enrichment
Started Aug 03, 2026, 09:00 PM UTC· resolved Aug 05, 2026, 01:45 PM UTC
- investigating Aug 04, 2026, 07:09 PM UTC
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.
- monitoring Aug 04, 2026, 08:48 PM UTC
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.
- resolved Aug 05, 2026, 01:45 PM UTC
This incident has been resolved, and all user updates have been restored.
Minor July 29, 2026 Issue with reciprocity on Carequality and Commonwell Networks 1d 2h Data Connections, CommonWell Network, Carequality Network
Started Jul 29, 2026, 07:00 PM UTC· resolved Jul 30, 2026, 09:14 PM UTC
- investigating Jul 29, 2026, 07:00 PM UTC
We can confirm incident conditions on reciprocity on the CareQuality and Commonwell networks. We are seeing elevated 5xx error rates in our responses to the networks and also latency has increased. The impact is seen on the patient discovery and document list endpoints, document retrieval appears to be unaffected. The team is continuing to investigate cause and potential solutions.
- monitoring Jul 30, 2026, 01:48 PM UTC
The situation of higher than acceptable 5xx messages and longer latency has resolved, but the team continues to research and monitor.
- resolved Jul 30, 2026, 09:14 PM UTC
With further research and monitoring, we’ve identified and upgraded the system configuration to improve it’s performance and mitigate the likelihood of further recurrences of the 5xx and latency behavior. This issue is resolved.
Major July 27, 2026 Some clients may not be able to access the ZAP in athena 1h 32m Applications, EHR Integrations, athenahealth
Started Jul 27, 2026, 03:25 PM UTC· resolved Jul 27, 2026, 04:57 PM UTC
- investigating Jul 27, 2026, 03:25 PM UTC
We are currently investigating reports of potential issues with Zus App. 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 July 27 11:40am ET: We have confirmed that this issue only impacts users of the ZAP embedded in athenahealth. We have updated the title and impacted services of this incident as such.
- monitoring Jul 27, 2026, 04:03 PM UTC
The issue impacting users’ ability to open the ZAP in athena appears to have resolved. We are continuing to actively monitor this situation. We are also continuing to track athena’s own published incident, and will update this incident once we can confirm full resolution of the source issues.
- resolved Jul 27, 2026, 04:57 PM UTC
We can confirm that users of the ZAP in athenahealth are now able to open the ZAP as expected. There was no data loss during this incident.
Minor July 15, 2026 Delays processing Surescripts medication history requests 20h 28m Data Connections, Surescripts Service
Started Jul 15, 2026, 04:41 PM UTC· resolved Jul 16, 2026, 01:10 PM UTC
- investigating Jul 15, 2026, 04:41 PM UTC
We’re aware of an issue affecting the processing of some Surescripts medication history requests created on July 10, which may delay or leave incomplete the return of medication history data for the affected requests. This is a partial delay rather than a complete outage, and new requests continue to be processed normally. We’re actively working with Surescripts to resolve the issue and will provide an update as soon as the affected data is fully processed.
- resolved Jul 16, 2026, 01:10 PM UTC
The issue is resolved and all delayed data has now been processed.
Major July 8, 2026 Documents unable to be loaded in Zus App 2h 52m Applications, Zus App
Started Jul 08, 2026, 06:20 PM UTC· resolved Jul 08, 2026, 09:12 PM UTC
- investigating Jul 08, 2026, 09:11 PM UTC
We are aware the customers are unable to view documents in the Zus App. The team is working on a fix.
- resolved Jul 08, 2026, 09:12 PM UTC
We have discovered and remediated the root cause. Documents are now loading normally. There has been no data loss.
Minor July 7, 2026 Some UPIDs stuck loading tin Zus App 1h 43m Applications, Zus App, Data APIs, FHIR APIs
Started Jul 07, 2026, 08:31 PM UTC· resolved Jul 07, 2026, 10:15 PM UTC
- investigating Jul 07, 2026, 08:31 PM UTC
We are aware of certain UPIDs stuck in a loading state in the Zus App and are currently working on mitigation.
- resolved Jul 07, 2026, 10:15 PM UTC
We identified the root cause of the stuck UPIDs and deployed a fix. These UPIDs are now loading normally in the Zus App. We will continue monitoring for loading problems.
Minor July 1, 2026 Potential issue with Carequality Network 22d 21h Data Connections, Carequality Network
Started Jul 01, 2026, 06:33 PM UTC· resolved Jul 24, 2026, 03:35 PM UTC
- investigating Jul 21, 2026, 06:33 PM UTC
We are currently investigating reports of potential issues with Carequality Network. 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.
- monitoring Jul 22, 2026, 10:02 PM UTC
We have identified an issue that was resulting in slightly degraded patient matching results on the Carequality network since 7/1. The original behavior has been restored as of 7/22. If you have any concerns about a potential data gap, please feel free to rerun a new job or reach out to your account contact.
- resolved Jul 24, 2026, 03:35 PM UTC
This incident is now resolved. Based on our continued monitoring, record location is performing as expected. We will continue to support customers with reruns as needed.
Major June 29, 2026 Potential issue with Surescripts Service 1d 22h Data Connections, Surescripts Service
Started Jun 29, 2026, 04:46 PM UTC· resolved Jul 01, 2026, 02:49 PM UTC
- investigating Jun 29, 2026, 04:46 PM UTC
We are currently investigating reports of potential issues with Surescripts Service. 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.
- investigating Jun 29, 2026, 08:52 PM UTC
We’ve confirmed delays affecting Surescripts Bulk medication history data. A portion of medication history requests are taking longer than expected to return results from Surescripts. This issue began on June 26. This is a partial delay rather than a complete outage, and requests continue to be processed. We’ve engaged Surescripts, who are actively investigating on their side, and we’re monitoring the situation closely.
- investigating Jun 30, 2026, 02:59 PM UTC
We have identified the root cause of the delays affecting Surescripts Bulk medication history data. We’ve implemented a fix and processing has resumed. We’re currently working through the backlog of queued requests and expect response times to continue improving as the queue is processed. We’ll provide another update as we make further progress toward full recovery.
- investigating Jun 30, 2026, 07:26 PM UTC
Reprocessing of the delayed Surescripts Bulk medication history files has completed. Based on our current assessment, all affected files have been successfully processed. We’re continuing to monitor our data pipeline to verify that processing has fully completed and to ensure no data remains unprocessed. We’ll provide a final update once we have this confirmation.
- resolved Jul 01, 2026, 02:49 PM UTC
The delays affecting Surescripts Bulk medication history data have been resolved. We’ve confirmed that all delayed files have been successfully processed and medication history data is now current and flowing normally. We’ll continue to monitor our systems, but all indicators show the issue has been fully resolved. Thank you for your patience while we worked to address this incident.
Minor June 26, 2026 Carequality reciprocity services experiencing elevated error rates 18h 39m Data Connections, Carequality Network
Started Jun 26, 2026, 07:44 PM UTC· resolved Jun 27, 2026, 02:23 PM UTC
- investigating Jun 27, 2026, 01:41 AM UTC
We are investigating elevated error rates in the Carequality reciprocity service, which responds to inbound queries for patient records from other network participants. As of 5:44 PM ET, the reciprocity service is successfully responding to ~75% of requests.
- resolved Jun 27, 2026, 02:23 PM UTC
This issue was resolved at 11:10pm EDT yesterday evening.
Minor June 5, 2026 GPS Summaries are intermittently failing to generate 1h 11m Applications, Zus App
Started Jun 05, 2026, 05:40 PM UTC· resolved Jun 05, 2026, 06:52 PM UTC
- investigating Jun 05, 2026, 05:40 PM UTC
We are investigating reports of GPS summaries failing to load. We will post an update as soon as we’ve identified the root cause.
- resolved Jun 05, 2026, 06:52 PM UTC
We’ve resolved the root issue causing some Generated Patient Summaries to never load or error. Previously impacted users should be able to generate summaries, and we will continue to monitor GPS status.
Major May 26, 2026 Missing SureScripts Bulk responses 1d 8h Data Connections, Surescripts Service
Started May 26, 2026, 02:27 PM UTC· resolved May 27, 2026, 10:57 PM UTC
- investigating May 26, 2026, 02:27 PM UTC
We are investigating an issue with missing data response files from the SureScripts Bulk service. As a result, medication history data for patients will be delayed until the issue is resolved. This issue appears to have begun on or after 5/24/2026. We are engaging with SureScripts and will provide updates as we receive more information.
- investigating May 26, 2026, 07:04 PM UTC
SureScripts has confirmed that a DNS issue caused a backlog of response files. They have remediated the issue and Zus is now receiving SureScripts Bulk files. We are processing these files and will send a final update when everything has finished processing.
- resolved May 27, 2026, 10:57 PM UTC
As of ~1:40 pm eastern today, all missing data has been received and processed successfully. This incident is now resolved.
Minor May 15, 2026 Some relational tables not refreshing 2d 3h Data Marts
Started May 15, 2026, 02:45 PM UTC· resolved May 17, 2026, 06:31 PM UTC
- investigating May 15, 2026, 02:45 PM UTC
The following tables in the relational data marts have been failing to refresh since 2pm Eastern Time on Thursday, May 14: condition and child tables document_reference and child tables encounter and child tables The data in these tables reflects data as of 2pm yesterday. We are working to bring these tables back up to date to meet our documented 3-hour target freshness.
- investigating May 15, 2026, 04:06 PM UTC
The condition and encounter tables have been rectified. We are continuing to work on refreshing the docuemnt_reference tables.
- monitoring May 15, 2026, 04:44 PM UTC
document_reference tables have now been refreshed as well. We are continuing to monitor the situation.
- resolved May 17, 2026, 06:31 PM UTC
We have resolved the underlying problem that was preventing tables from automatically refreshing. All relational tables should now be following the targeted freshness published in the documentation.
Minor May 14, 2026 Generated Patient Summaries are failing to generate 23m Applications, Zus App
Started May 14, 2026, 08:19 PM UTC· resolved May 14, 2026, 08:42 PM UTC
- investigating May 14, 2026, 08:19 PM UTC
New Generated Patient Summary requests are failing for users. The root cause has been identified and the fix is rolling out. We will post an update when the issue is fully resolved.
- resolved May 14, 2026, 08:42 PM UTC
Generated Patient Summaries are now restored and will generate as expected.
Minor May 7, 2026 Degraded performance in the Zus App and Zus APIs 13m Applications, Zus App, EHR Integrations, athenahealth and 6 more
Started May 07, 2026, 09:06 PM UTC· resolved May 07, 2026, 09:19 PM UTC
- investigating May 07, 2026, 09:06 PM UTC
We are aware of and investigating degraded performance with Zus APIs and in the Zus Application. We will post an update with more information when we’ve identified the root cause.
- resolved May 07, 2026, 09:19 PM UTC
We identified the root cause of performance degradation and stopped the process from continuing. We’ll continue to monitor closely to ensure there is no further performance impact.
Major May 4, 2026 [Resolved] Some patients were unavailable in the Zus Web Application 1h Applications, Zus App
Started May 04, 2026, 07:48 PM UTC· resolved May 04, 2026, 08:48 PM UTC
- resolved May 04, 2026, 08:48 PM UTC
From 3:48pm ET - 4:45pm ET some patients were not accessible in the Zus Web Application. Navigating to the patient ZAP would have resulted in a message that the patient was “inactive” when they were in fact “active.” We identified the root cause and are deploying additional protections to ensure this will not happen again.
Minor April 21, 2026 Increased Carequality errors for zip code based patient lookups 9d 20h Data Connections, Carequality Network
Started Apr 21, 2026, 08:14 PM UTC· resolved May 01, 2026, 04:51 PM UTC
- investigating Apr 21, 2026, 08:14 PM UTC
We are investigating an increased number of Carequality errors affecting a subset of requests primarily for California-based patients. We have identified a pattern related to certain zip code based patient lookups and are coordinating with our network partner, Kno2, on root cause analysis. Some customers may see delayed or incomplete results while this is ongoing.
- investigating Apr 22, 2026, 09:33 PM UTC
We have identified the likely root cause of the increased number of Carequality errors affecting a subset of requests, primarily for California-based patients. Our investigation with Kno2 found that some data published to the Carequality directory by one implementer is not formatted according to Carequality policy, which appears to be driving the pattern related to certain zip code based patient lookups. This issue appears to be affecting ~6% of Zus jobs for patients with a California address. The affected implementer is actively working on a correction. Some customers may continue to see delayed or incomplete results until that correction is made and the directory sync completes.
- investigating Apr 27, 2026, 06:16 PM UTC
We are continuing to work with Kno2 on having the affected implementer correct their impacted Carequality directory listings. This issue continues to affect ~6% of Zus jobs for patients with a California address.
- resolved May 01, 2026, 04:51 PM UTC
We have worked with Kno2 to prevent job errors when encountering misconfigured Carequality directory listings. We are no longer seeing errors for this issue and we have successfully re-run affected jobs.
Minor April 17, 2026 Errors in data mart tables 2d 17h Data Marts
Started Apr 17, 2026, 11:45 PM UTC· resolved Apr 20, 2026, 04:45 PM UTC
- resolved Apr 20, 2026, 04:45 PM UTC
From April 17, 7:45PM to April 20, 12:45Pm EDT, a number of tables in data marts were returning errors when queried. These errors were caused by an incomplete deployment, and affected the following tables: care_team_identifier care_team_participant care_team_participant_role_coding care_team_telecom diagnostic_report_code_coding diagnostic_report_identifier diagnostic_report_performer diagnostic_report_result These tables have been rectified, and we will be adding additional measures to prevent these errors in the future. We sincerely apologize for the inconvenience.