DrChrono Outage History

Started Jul 15, 2026, 05:42 PM UTC· resolved Jul 15, 2026, 07:10 PM UTC

1. investigating Jul 15, 2026, 05:42 PM UTC

   Our third-party provider, Updox, is currently experiencing a service disruption. As a result, users may experience slowness, errors, or delays when sending or receiving faxes. We are monitoring the issue closely and will share updates as they become available. Thank you for your patience. Updox Status Page: https://status.updox.com/

2. monitoring Jul 15, 2026, 06:01 PM UTC

   Our integration, Updox has implemented a fix and is reporting that services are recovering. We are continuing to monitor the recovery and are seeing service improvements. Some users may still experience intermittent delays or errors while systems fully stabilize. We will continue to provide updates as they become available. Thank you for your patience while this issue is being resolved.

3. resolved Jul 15, 2026, 07:10 PM UTC

   Our integration, Updox, has confirmed that the service disruption has been resolved and all services are operational.

Read the full incident report →

Started Jul 07, 2026, 04:59 PM UTC· resolved Jul 08, 2026, 08:29 PM UTC

1. investigating Jul 07, 2026, 04:59 PM UTC

   We are currently aware of system issues impacting DrChrono and are actively working with our Engineering team to investigate and resolve the issue. We will continue to update this page.

2. investigating Jul 07, 2026, 06:30 PM UTC

   We are continuing to investigate the issue impacting DrChrono. Our Engineering team is actively working to resolve the issue. We will provide updates on this page as they become available.

3. monitoring Jul 07, 2026, 07:55 PM UTC

   Our Engineering team has implemented mitigation measures and is continuing to monitor the system. We will provide updates on this page as they become available.

4. monitoring Jul 08, 2026, 02:04 PM UTC

   The system remains operational, and our Engineering team continues to monitor the platform. We will provide updates on this page as more information becomes available.

5. resolved Jul 08, 2026, 08:29 PM UTC

   The system remains operational, and we have not observed any further issues since moving to monitoring yesterday. This incident has been resolved. Our Engineering team will continue to review the event as part of our ongoing efforts to maintain the reliability and performance of the platform. Thank you for your patience,

Read the full incident report →

Started Jun 04, 2026, 12:31 PM UTC· resolved Jun 04, 2026, 07:02 PM UTC

1. investigating Jun 04, 2026, 12:31 PM UTC

   We are aware that some users may be experiencing intermittent errors when using the system. Our Support team is currently working with our Engineering team to review and resolve the issue. We will continue to monitor the situation and provide updates as more information becomes available.

2. monitoring Jun 04, 2026, 01:46 PM UTC

   We are continuing to monitor the intermittent system errors and will provide updates as additional information becomes available.

3. monitoring Jun 04, 2026, 01:49 PM UTC

   We are continuing to monitor the intermittent system errors and will provide updates as additional information becomes available.

4. resolved Jun 04, 2026, 07:02 PM UTC

   We have confirmed that the adjustments we implemented have fully resolved the issue and our systems are up and operational. We appreciate your patience as we worked through this matter.

Read the full incident report →

Started Jun 03, 2026, 03:49 PM UTC· resolved Jun 03, 2026, 07:33 PM UTC

1. investigating Jun 03, 2026, 03:49 PM UTC

   We are aware that some users may be experiencing intermittent errors when using the system. Our Support team is currently working with our Engineering team to review and resolve the issue. We will continue to monitor the situation and provide updates as more information becomes available.

2. investigating Jun 03, 2026, 05:22 PM UTC

   Our team is still actively working on a fix for the issue. We will continue to monitor progress and provide updates as more information becomes available.

3. monitoring Jun 03, 2026, 06:50 PM UTC

   We have implemented corrective measures to resolve the issue causing intermittent slowness for some users. Initial results indicate that system performance has returned to normal. Our team is actively monitoring the platform to ensure stability and confirm that the issue has been fully resolved. We will continue to provide updates as needed. Thank you for your patience while we worked to address this issue.

4. resolved Jun 03, 2026, 07:33 PM UTC

   The intermittent slowness issue has been mitigated, and platform performance is currently stable. Our investigation indicates the issue may be related to AWS throttling behavior. We are continuing to partner with AWS to validate the root cause and implement additional corrective measures while closely monitoring system performance.

Read the full incident report →

Started May 05, 2026, 04:02 PM UTC· resolved May 05, 2026, 05:39 PM UTC

1. investigating May 05, 2026, 04:02 PM UTC

   We are currently aware of an issue impacting a small subset of customers where appointment reminders are not being sent. Our Engineering team is actively investigating and working toward a resolution. We will provide an update here as soon as the issue has been resolved.

2. resolved May 05, 2026, 05:39 PM UTC

   The issue impacting appointment reminders has been resolved. All systems are now operating normally. Thank you for your patience.

Read the full incident report →

Started Apr 03, 2026, 02:15 PM UTC· resolved Apr 07, 2026, 04:30 PM UTC

1. investigating Apr 03, 2026, 02:15 PM UTC

   Our third-party provider, ID.me, is currently experiencing an issue which is impacting the ability to send controlled prescriptions. We are actively working with ID.me to better understand the scope of the issue and will provide updates as more information becomes available.

2. identified Apr 03, 2026, 03:41 PM UTC

   ID.me is still experiencing issues. However, as a workaround, users can update their multi-factor authentication (MFA) method by switching from push notifications to a code generator (authenticator app). For step-by-step instructions, please visit: https://support.drchrono.com/home/360051657392-adding-or-changing-a-device-for-multi-factor-authentication-with-id-me We are actively working with ID.me to resolve this issue and will provide updates as more information becomes available.

3. identified Apr 04, 2026, 11:11 AM UTC

   Our third-party provider, ID.me, is still experiencing ongoing issues, which is impacting the ability to send controlled prescriptions. A temporary fix has been implemented. iOS users can continue logging in by manually opening the Authenticator app and approving requests. Push notifications on Android devices have been restored and are working as expected. ID.me is actively working on a complete fix to restore push notification functionality on iOS. In the meantime, we are closely monitoring the situation and coordinating with their team. For the latest updates, please refer to their status page: https://status.id.me/ We will continue to share updates as more information becomes available. If you experience any ongoing issues, please don’t hesitate to reach out with details. Thank you for your patience and understanding.

4. identified Apr 06, 2026, 02:03 PM UTC

   Our third-party provider, ID.me, is still experiencing ongoing issues, which may affect your ability to prescribe controlled substances. This appears to be limited to Push Notification MFA and may result in authentication errors. At this time, services are functioning normally on Android devices. ID.me is actively working on a fix to restore push notifications on iOS. Recommended Action: Switch to an alternate MFA method using an authenticator app for code generation to avoid disruption. Set up a new MFA method via ID.me Wallet: https://help.id.me/hc/en-us/articles/202673924-Create-your-ID-me-Wallet If you’re unable to log into ID.me Wallet, use MFA recovery: https://help.id.me/hc/en-us/articles/360017927633-ID-me-MFA-recovery-steps-if-you-lost-access-or-can-t-sign-in We are actively monitoring the situation and will provide updates as they become available. Thank you for your patience. For the latest updates, please refer to their status page: https://status.id.me/

5. resolved Apr 07, 2026, 04:30 PM UTC

   Our third-party provider, ID.me, has resolved the issue that was impacting the ability to prescribe controlled substances. Push Notification MFA is now functioning as expected. Recommended Action: If you previously switched to an alternate MFA method (such as an authenticator app or SMS), you may switch back to Push Notifications. For steps to update your MFA method, visit: https://support.drchrono.com/home/360051657392-adding-or-changing-a-device-for-multi-factor-authentication-with-id-me If you continue to experience login issues, you may still follow ID.me’s recovery steps: https://help.id.me/hc/en-us/articles/360017927633-ID-me-MFA-recovery-steps-if-you-lost-access-or-can-t-sign-in

Read the full incident report →

Started Mar 30, 2026, 08:48 PM UTC· resolved Mar 30, 2026, 10:05 PM UTC

1. investigating Mar 30, 2026, 08:48 PM UTC

   We are aware of an issue causing system slowness for some users. Our engineering team is actively investigating and working toward a resolution. We will share additional updates as more information becomes available.

2. resolved Mar 30, 2026, 10:05 PM UTC

   Our engineering team has resolved the issue, and system performance has returned to normal. We appreciate your patience.

Read the full incident report →

Started Mar 25, 2026, 04:59 PM UTC· resolved Mar 25, 2026, 09:36 PM UTC

1. investigating Mar 25, 2026, 04:59 PM UTC

   We have identified an issue causing intermittent symptoms across multiple areas of the system, and you may encounter the following error messages: “Bad Gateway” “Server is Busy” “Failed to Load Footer” Our engineering team is all-hands-on-deck and investigating the root cause to restore full functionality as quickly as possible. We understand the impact this may have and appreciate your patience while we resolve the issue. We are working on this as quickly as we can and will provide updates as they become available.

2. investigating Mar 25, 2026, 05:41 PM UTC

   We are continuing to investigate the issue causing intermittent symptoms across multiple areas of the system, and you may encounter the following error messages: “Bad Gateway” “Server is Busy” “Failed to Load Footer” Our engineering team remains actively engaged and is working to resolve the issue as quickly as possible. As a temporary solution, refreshing the page may clear the error. We appreciate your continued patience and will provide further updates as more information becomes available.

3. resolved Mar 25, 2026, 09:36 PM UTC

   We have resolved the intermittent system issues experienced over the past three days. The root cause was related to brief scenarios where one of the supporting databases was unable to accept new connections, resulting in a small percentage of requests (approximately 3%) returning errors. Overnight, we implemented performance improvements to reduce system strain and help isolate the issue. Today, we made additional infrastructure adjustments to address the connection limitations and monitored system performance throughout peak usage hours. The system is now operating normally. We will publish a detailed root cause analysis (RCA) on our status page in the coming days.

Read the full incident report →

Started Feb 09, 2026, 02:55 PM UTC· resolved Feb 24, 2026, 08:59 PM UTC

1. investigating Feb 09, 2026, 02:55 PM UTC

   We are aware of an issue affecting a subset of users who are reporting that some billing related reports fail to load. This includes the Financial Transactions Report, Aging A/R Analysis, Denial Analysis, and other billing-related reports. Our team is actively investigating and will provide updates as more information becomes available.

2. identified Feb 10, 2026, 04:30 PM UTC

   The Financial Transactions Report is temporarily refreshing once per day overnight and should be used for prior days only, not today’s activity. For current day reporting, please use the Day Sheet. We are making adjustments to optimize performance of the Financial Transactions Report, and some tabs may be temporarily unavailable during this work. All other billing reports are functioning normally and continue to refresh every 15 minutes.

3. monitoring Feb 12, 2026, 10:18 PM UTC

   Thank you for your patience while we worked to restore performance of billing-related reporting. All reports, including all tabs of the Financial Transactions Report, are loading as expected and refreshing on the standard 15-minute cadence. We worked closely with our hosting partner and our internal team to identify contributing factors and implement corrective measures. We are also taking additional preventive measures to help reduce the risk of recurrence. We will continue to monitor performance and provide updates as needed.

4. resolved Feb 24, 2026, 08:59 PM UTC

   The performance of billing-related reporting has remained stable following the corrective measures implemented. All reports, including all tabs of the Financial Transactions Report, continue to load as expected. After an extended monitoring period confirming system stability, this incident is now considered resolved. We have implemented preventive measures to reduce the risk of recurrence. Thank you for your patience while we worked through this issue.

Read the full incident report →

Started Jan 06, 2026, 12:28 AM UTC· resolved Jan 06, 2026, 01:24 AM UTC

1. investigating Jan 06, 2026, 12:28 AM UTC

   We’re aware of an issue impacting the ability to send prescriptions. Our team is actively investigating and working to resolve this as quickly as possible. We’ll provide another update as soon as we have more information.

2. resolved Jan 06, 2026, 01:24 AM UTC

   We identified the issue impacting prescription transmission and worked closely with our third-party vendor, Surescripts, to investigate and resolve the problem. The issue has now been fully resolved. At this time, prescriptions should be sending successfully without interruption. Our team will continue to actively monitor the system to ensure stability and prevent recurrence.

Read the full incident report →

Started Dec 17, 2025, 04:32 PM UTC· resolved Dec 18, 2025, 09:23 PM UTC

1. investigating Dec 17, 2025, 04:32 PM UTC

   We are currently investigating an issue affecting patient search on both the web platform and the iPad app. Some users may see search results that includes their patients that do not match the search criteria. Our engineering team is actively working to identify the cause and restore expected functionality. We will provide updates here as more information becomes available. We recommend temporarily typing the entire patient first and last name to return the most accurate results. Thank you for your patience.

2. identified Dec 17, 2025, 10:40 PM UTC

   We have identified the cause of the issue affecting patient search results on the web platform and iPad app. A fix has been developed and is scheduled for deployment. Until the fix is fully deployed, some users may continue to see search results that includes their patients that do not match the search criteria. We will update this page once the fix has been released.

3. monitoring Dec 18, 2025, 02:28 AM UTC

   The fix for the patient search issue has been deployed. We are actively monitoring the system to ensure patient search results are returning as expected on both the web platform and iPad app. Please reach out to our Support team if you are continuing to experience the issue. We will continue monitoring and provide a final update once the issue is fully resolved.

4. resolved Dec 18, 2025, 09:23 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 18, 2025, 01:47 PM UTC· resolved Nov 18, 2025, 10:08 PM UTC

1. investigating Nov 18, 2025, 01:47 PM UTC

   Cloudflare (internet infrastructure) is experiencing a global network outage. This issue may be impacting access to parts of the system. Our system does not leverage Cloudflare directly but many of our integrated third parties do and are showing intermittent impact. Due to this, functionality that relies on third parties may have intermittent errors and/or delays. This is also preventing our support team from accessing certain tools used to support our customers. We are monitoring the situation closely and will update this message with the known list of impacted areas.

2. monitoring Nov 18, 2025, 04:21 PM UTC

   Cloudflare (internet infrastructure) has communicated that they are continuing to monitor the issue. We may continue to experience intermittent issues as systems update across the internet. We will continue to monitor to ensure all systems are back to normal across the day.

3. resolved Nov 18, 2025, 10:08 PM UTC

   This issue has been resolved. Please contact support if you are still experiencing issues.

Read the full incident report →

Started Oct 20, 2025, 04:14 PM UTC· resolved Oct 20, 2025, 11:13 PM UTC

1. investigating Oct 20, 2025, 04:14 PM UTC

   Earlier today, Amazon Web Services (AWS) experienced an issue involving many of their core systems. While AWS has reported the issue is mostly mitigated, residual effects are still continuing as their systems recover. The DrChrono system is healthy at this time with the exception of the following: *Possible delays in delivery of reports to the message center *Possible delays in labs, referrals and fax processing As AWS recovery progresses, you may experience intermittent slowness, delays, or other performance impacts while working inside the DrChrono platform. Our teams are closely monitoring the situation and will provide updates as recovery progresses. We will update the above list as the situation continues. We appreciate your patience and understanding as AWS works to fully restore normal operations.

2. monitoring Oct 20, 2025, 04:14 PM UTC

   Earlier today, Amazon Web Services (AWS) experienced an issue involving many of their core systems. While AWS has reported the issue is mostly mitigated, residual effects are still continuing as their systems recover. The DrChrono system is healthy at this time with the exception of the following: *Possible delays in delivery of reports to the message center *Possible delays in labs, referral and fax processing As AWS recovery progresses, you may experience intermittent slowness, delays, or other performance impacts while working inside the DrChrono platform. Our teams are closely monitoring the situation and will provide updates as recovery progresses. We will update the above list as the situation continues. We appreciate your patience and understanding as AWS works to fully restore normal operations.

3. resolved Oct 20, 2025, 11:13 PM UTC

   We’re seeing significant improvements across the DrChrono platform following the earlier AWS-related issues. Reports, labs, referrals, and fax processing have recovered, and overall system performance has returned to normal.

Read the full incident report →

Started Jul 16, 2025, 03:24 PM UTC· resolved Jul 16, 2025, 05:20 PM UTC

1. identified Jul 16, 2025, 03:24 PM UTC

   Our team has identified reports of system slowness across various areas of the DrChrono application. We are working to resolve this issue.

2. identified Jul 16, 2025, 03:47 PM UTC

   We are continuing to work on a fix for this issue.

3. identified Jul 16, 2025, 04:17 PM UTC

   We are continuing to work on a fix for this issue. The next update will be in 20 minutes.

4. identified Jul 16, 2025, 04:44 PM UTC

   We are continuing to work on a fix for this issue. The next update will be in 20 minutes.

5. monitoring Jul 16, 2025, 05:03 PM UTC

   A fix has been implemented and we are monitoring the results.

6. resolved Jul 16, 2025, 05:20 PM UTC

   This incident has been resolved.

7. postmortem Jul 18, 2025, 09:11 PM UTC

   **Incident Overview** On July 16th, 2025, the DrChrono application experienced a temporary service outage following a scheduled release the evening prior. The release itself was successful; however, during post-release monitoring the morning of July 17th we observed slightly elevated memory pressure across application servers. This memory pressure was not causing end user experience impact but was identified due to increased observability following the deployment. In response, a proactive configuration change was made to improve memory usage. Unfortunately, this adjustment unintentionally restricted the system’s ability to allocate sufficient resources for application processes, resulting in a temporary outage. Due to this occurring during core business hours, it took some time to restore enough resources to support application traffic, but services returned to normal operation once resources were restored. **How We Responded** The configuration change was reverted, and traffic was temporarily paused to allow the system to recover. Once the application was confirmed healthy traffic was resumed and the system became fully available. **Corrective and Preventative Actions** To prevent recurrence, we are taking the following steps: * **Standard Operating Procedure \(SOP\) Enhancements:** We are updating and reinforcing our internal SOPs to emphasize slow rollout and verification testing when applying infrastructure setting changes prior to rollout for all traffic – even when thought to be safe or simple. * **Warm Resources on Standby:** We have created and will continue to maintain a pool of separate warm servers so that we can restore previous configurations more quickly as well as spin up needed resources faster in cases of high traffic. We know that many of you rely on DrChrono every day to support your operations. We sincerely apologize for this disruption and are committed to strengthening our systems to prevent it from happening again. Thank you for your patience and continued trust.

Read the full incident report →

Started Jul 01, 2025, 01:11 PM UTC· resolved Jul 02, 2025, 12:35 AM UTC

1. identified Jul 01, 2025, 01:11 PM UTC

   We want to make you aware that Availity is currently experiencing technical issues on their platform, which is affecting the ability to run eligibility checks within DrChrono. Our team has contacted Availity for assistance and is closely monitoring the situation. We will share updates as soon as more information becomes available. Thank you for your patience and understanding.

2. identified Jul 01, 2025, 08:44 PM UTC

   DrChrono is currently experiencing connectivity issues with Availity, which is affecting eligibility check functionality within the platform. Our team is working with Availity to resolve the issue and restore normal service as quickly as possible. We will provide further updates as more information becomes available. Thank you for your patience.

3. resolved Jul 02, 2025, 12:35 AM UTC

   The connectivity issue between DrChrono and Availity has been resolved. Eligibility checks within the platform are now functioning as expected. We appreciate your patience while we worked to address this issue. If you continue to experience any problems, please reach out to our Support Team for further assistance. Thank you for your continued trust in DrChrono.

Read the full incident report →

Started Jun 13, 2025, 02:12 PM UTC· resolved Jun 13, 2025, 07:09 PM UTC

1. investigating Jun 13, 2025, 02:12 PM UTC

   We are currently investigating an issue affecting the ability to generate refill prescription data in the e-Rx ordering screen in DrChrono. Our team is actively working with engineering to identify the root cause and resolve the problem as quickly as possible. Prescriptions are still being sent successfully, but you may need to re-enter the medication information in the e-Rx ordering screen. We understand the urgency of this functionality and will provide updates here as we learn more. Thank you for your patience.

2. identified Jun 13, 2025, 04:03 PM UTC

   Our team has identified the cause of this issue and we are working toward implementing a fix today. We can confirm the issue is isolated to the web version of DrChrono and is not affecting any prescription ordering workflows on the mobile application version. When initiating a refill from the patient's medication list on the web, the system is not automatically populating the medication information in the e-Rx order. Refill prescriptions from the web version are continuing to be sent successfully after the refill information is entered either manually or by selecting a favorite prescription. We will continue to update here once we implement the fix for this issue.

3. resolved Jun 13, 2025, 07:09 PM UTC

   The issue impacting the automatic population of medication details when initiating a refill from the patient’s Medication List on the web version of DrChrono has now been resolved. Our team identified the root cause and implemented a fix. You should now see the medication information auto-populate as expected when processing refill prescriptions via the web. Please note, this issue was isolated to the web version only and did not affect any prescription ordering workflows through the mobile application. Additionally, refill prescriptions continued to send successfully during the issue once the medication details were manually entered or selected from favorites. If you experience any further issues, please don’t hesitate to contact Support at 650-988-5379, email at [email protected], or use the in-app chat to speak with a live agent.

Read the full incident report →

Started May 27, 2025, 03:30 PM UTC· resolved May 28, 2025, 01:23 PM UTC

1. investigating May 27, 2025, 03:30 PM UTC

   Our team is investigating an issue with appointment reminders. We will provide updates as they are available.

2. identified May 27, 2025, 05:53 PM UTC

   The appointment reminder issue has been identified and a fix is being implemented. We will provide updates as they are available.

3. identified May 27, 2025, 07:27 PM UTC

   Our team has identified an issue that has prevented SMS, Email, and Phone Call appointment reminders scheduled to be sent from 05/23/2025-05/27/2025 from being delivered successfully. Email invitations to telehealth appointments are not affected. We are implementing a fix to ensure future appointment reminders will be delivered successfully and exploring the possibility of re-sending failed reminders scheduled to send from 05/23/2025-05/27/2025 for future appointment dates. We will continue to provide updates here.

4. monitoring May 27, 2025, 11:05 PM UTC

   We have successfully deployed a fix for the reminder transmission issue. Our team was also able to successfully send out all reminders for future appointments that were originally scheduled to be delivered 05/27/2025. All future appointment reminders will transmit without issue. We are still working on identifying appointment reminders for future appointments originally scheduled for delivery 05/23/2025-05/26/2025. We will continue to provide updates on the previous reminders here.

5. resolved May 28, 2025, 01:23 PM UTC

   We have successfully transmitted all email appointment reminders originally scheduled for delivery from 05/23/2025-05/26/2025 for appointments with dates of service 05/28/2025 and later. It was determined that we are unable to re-send SMS reminders from this time period. This issue is now resolved and our team confirms that all reminders are transmitting without issue since 05/27/2025.

Read the full incident report →

Started Mar 20, 2025, 04:22 PM UTC· resolved Mar 20, 2025, 09:56 PM UTC

1. investigating Mar 20, 2025, 04:22 PM UTC

   We are aware that some users are experiencing issues with the billing tab not loading properly. Our team is actively investigating the situation and working closely with our engineering team to resolve this as quickly as possible. We will continue to update this page with updates.

2. identified Mar 20, 2025, 04:45 PM UTC

   Users who are not currently utilizing our Support Chat functionality are experiencing loading issues with items in the Billing menu. Our team is working on resolving this issue urgently. Please reach out to our Support Team if you are experiencing this issue.

3. resolved Mar 20, 2025, 09:56 PM UTC

   The issue with the billing tab has been resolved. We are sorry for any issues this may have caused.

Read the full incident report →

Started Mar 06, 2025, 02:13 PM UTC· resolved Mar 06, 2025, 05:29 PM UTC

1. investigating Mar 06, 2025, 02:13 PM UTC

   We are currently aware of issues affecting users attempting to log into OnPatient via DrChrono. Our team is actively investigating the situation and working to resolve it as quickly as possible. We appreciate your patience and understanding as we work on resolving this. We will provide updates as soon as we have more information.

2. monitoring Mar 06, 2025, 03:00 PM UTC

   We are pleased to inform you that a fix has been implemented affecting users logging into OnPatient via DrChrono. Our team is continuing to monitor the situation closely to ensure everything remains stable.

3. resolved Mar 06, 2025, 05:29 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Dec 22, 2024, 09:27 PM UTC· resolved Dec 23, 2024, 12:51 AM UTC

1. investigating Dec 22, 2024, 09:27 PM UTC

   Our team is investigating reports of an issue with OnPatient, which may prevent a patient from logging into OnPatient or joining a telehealth visit. We will continue to provide updates as new information becomes available. Thank you for your patience and understanding.

2. monitoring Dec 22, 2024, 10:18 PM UTC

   A fix for this issue has been implemented and our team is monitoring the results. We will continue to provide updates as new information becomes available. Thank you for your patience and understanding.

3. resolved Dec 23, 2024, 12:51 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Dec 19, 2024, 07:08 PM UTC· resolved Dec 20, 2024, 02:08 PM UTC

1. monitoring Dec 19, 2024, 07:08 PM UTC

   Monitoring: We have identified an issue with documents displayed in the patient chart. We have implemented a fix and are monitoring the results.

2. identified Dec 19, 2024, 07:23 PM UTC

   Identified: We have identified an issue with documents displayed in the patient chart. We have identified a fix and are working towards resolving this issue.

3. resolved Dec 20, 2024, 02:08 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 18, 2024, 03:29 PM UTC· resolved Nov 19, 2024, 12:25 PM UTC

1. identified Nov 18, 2024, 03:29 PM UTC

   ID.me, our third-party vendor, has identified an issue within their system and is actively working on deploying a fix. We will continue to provide updates as new information becomes available. Thank you for your patience and understanding. Please follow their status page for more information: https://status.id.me/

2. identified Nov 18, 2024, 04:48 PM UTC

   ID.me, our third-party vendor, has identified an issue within their system and is actively working on deploying a fix. We will continue to provide updates as new information becomes available. Thank you for your patience and understanding. Please follow their status page for more information: https://status.id.me/

3. identified Nov 18, 2024, 05:53 PM UTC

   ID.me, our third-party vendor, is continuing to work on a fix to address their ongoing platform degradation. We will continue to provide updates as new information becomes available. Thank you for your patience and understanding. Please follow their status page for more information: https://status.id.me/

4. monitoring Nov 18, 2024, 07:10 PM UTC

   ID.me, our third-party vendor, has implemented a fix and is continuing to monitor their system. We will continue to provide updates as new information becomes available. Thank you for your patience and understanding. Please follow their status page for more information: https://status.id.me/

5. monitoring Nov 19, 2024, 12:25 PM UTC

   ID.me, our third-party vendor, has resolved their incident. Thank you for your patience and understanding.

6. resolved Nov 19, 2024, 12:25 PM UTC

   This incident has been resolved.

Read the full incident report →