Ensora Health had 17 outages in the last 2 years totaling 547h 16m of downtime — averaging 0.7 incidents per month.
There were 17 Ensora Health outages since October 19, 2025 totaling 547h 16m of downtime. Each is summarised below — incident details, duration, and resolution information.
Walgreens Pharmacy experienced an unexpected disruption in service and they had engaged their Message Queue Service. All e-prescribing messages to this receiver were placed in a queue and released when connectivity was restored this morning. Prescriptions should now be routing to Walgreens pharmacy as normal.
We experienced a brief period of degraded performance due to increased load on the database caused by a specific query. This resulted in temporary application unresponsiveness. The issue was quickly identified and resolved by terminating the query, and system performance has since returned to normal. The parameters of this query have been refined to avoid any future disruption.
We are aware of the Azure Quota Host Limit – No Available Resources issue currently affecting the environment. Our team is actively working toward resolving this, and we expect services to be restored shortly. We appreciate your patience and understanding while we address the matter.
Connectivity has now been fully restored, and all affected services are operating normally. We ask that users begin retrying their actions at this time to confirm full functionality on their end. If anyone continues to experience errors or notices any unexpected behavior, please report it to us immediately so we can investigate further.
Incident Update – Service Restored We have successfully resolved the incident, and all services are now operating normally. Connectivity and system functionality have been fully restored. We ask that users resume their activities and verify that everything is working as expected on their end. If any issues persist or if you observe unexpected behavior, please report it to us so we can investigate promptly.
Some prescribers are encountering EPCS signing issues when using the Exostar services. We are working with Exostar to investigate the issue. This may result in CS scripts failing to transmit. Please use alternative means to contact the pharmacy if the situation is urgent.
We have seen almost all impacted users now prescribing controlled substances normally. We are helping individual doctors that have ongoing issues separately.
We are currently experiencing an interruption affecting Support Request case submissions. At this time, cases submitted through our customer portal or via email may be delayed in being received and responded to. The underlying issue has been identified, and our team is actively working with our support ticket management system provider to resolve this as quickly as possible. We will provide updates as more information becomes available.
We are now able to receive new Support case submissions through our portal and email. Our team is actively monitoring to ensure all cases have been successfully received and is working through any delayed requests. We will continue to monitor closely and provide further updates as needed.
This incident has been resolved.
We are triaging this matter with the highest priority and appreciate your patience. We will provide updates as soon as possible.
Our engineering team has identified the source of these errors and is working with our partners to establish a temporary workaround and timeline to full resolution. We appreciate your patience.
A temporary fix has been implemented and providers should be able to connect and use ERX as normal. Please have providers reattempt.
We have received confirmation that providers are able to access and prescribe from Ensora ERX once again. If users continue to see any errors, please contact [email protected]. Thank you!
Some ID.me users are encountering an error while attempting to sign prescriptions for controlled substances. Our engineers are working with ID.me to investigate and resolve the issue.
ID.me users are encountering an error while attempting to sign prescriptions for controlled substances. This issue seems to be most common with push notifications; please attempt other means. Our engineers are working with ID.me to investigate and resolve the issue.
ID.me users are encountering an error while attempting to sign prescriptions for controlled substances. This issue seems to be most common with push notifications; please attempt other means. The ID.me team is working on a solution to the signing errors.
ID.me has reported that they have corrected the signing issue for Android users, and have implemented a temporary fix for iPhone users. Please report any ongoing signing issues that you may encounter.
This incident has been resolved.
Some users are currently unable to register with Surescripts. We are not seeing any issues with prescribing for users already registered, but new registration attempts or adding service levels appears to be failing. We are coordinating with Surescripts to investigate and resolve the issue.
The Surescripts registrations are now succeeding. We are continuing to monitor the transactions.
This incident has been resolved.
Exostar is continuing to experience issues for some Authy users and is working to resolve the issue.
Exostar is continuing to investigate an issue that is impacting some Authy users. Those users may not be able to sign scheduled drug prescriptions with the Authy app. Note that the similar issue for hardware tokens has been resolved.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Some providers may be experiencing failed claims due to an import issue with the Connex printer. Our development team is actively working on a resolution. In the meantime, you may manually correct any affected claims. We appreciate your patience and will provide updates as soon as the issue is resolved.
The issue has been identified and a fix is being prepared for release.
We have deployed a fix to this issue and are monitoring to ensure that it is fully resolved.
This incident has been resolved.
We are currently investigating an issue that may result in connectivity issues, including timeouts and slowdowns. This may result in 503 or 504 errors. Our engineers are evaluating the issue and working to a resolution.
The issue has been identified and we are seeing the system performance restored and connectivity times improve. We are continuing to evaluate and monitor the situation.
We are continuing to monitor for potential issues, but we are seeing normal performance.
This incident has been resolved.
Exostar is addressing an ongoing issue that is resulting in inconsistent connectivity for signing prescriptions and registering for EPCS. It is recommended that EPCS registrations are not attempted during this outage. 2FA signing attempts may be reattempted if necessary.
Exostar has indicated that the signing issue has been resolved.
We are investigating reports of website latency and are working to resolve the issue.
The issue has been resolved and we are monitoring the results.
This incident has been resolved.
We’re currently experiencing service disruptions due to a widespread outage affecting Amazon Web Services (AWS), which powers key components of our platform. Our team is actively monitoring the situation and staying closely aligned with AWS as they work toward resolution. We are seeing this impact eligibility and drug history services, likely due to PBMs hosted on AWS.
Amazon Web Services is continuing to solve the performance issues which may result in latency for end users. We are now seeing eligibility and drug history services functioning in most cases, despite some delays.
Amazon Web Services continue to troubleshoot this matter and have made some improvements throughout the day. Several vendors are still impacted and you may continue to see issues with eligibility checks, MFA signing for controlled substances, load times and latency. This can result in issues with registration, transmission, and records retrieval. You can learn more at their status page here: https://health.aws.amazon.com/health/status We will continue to monitor the AWS status page and provide updates here as they come available. We will provide an update tomorrow morning if not before. We appreciate your patience.
AWS has announced that the latency issues and timeouts have been resolved. All services should now be working as expected. If any issues persist, please contact support.
We are investigating an issue that is causing prescriptions to fail electronic transmission. We are working to resolve the issue as our top priority. Please note that prescriptions may be printed or faxed in the interim as permitted by your state. Thank you for your patience as we investigate and resolve the issue.
We have identified the source of the issue and are deploying a hotfix to production. This will result in a brief interruption of service as the update deploys.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.