История сбоев Drchrono

1. 15 июля 2026 г. в 17:42 UTCinvestigating

   Наша интеграция, Updox, в настоящее время переживает сбой в обслуживании. В результате пользователи могут испытывать медлительность, ошибки или задержки при отправке или получении факсов. Мы внимательно следим за этим вопросом и будем делиться обновлениями по мере их появления. Спасибо за ваше терпение. Страница статуса Updox: https://status.updox.com

2. 15 июля 2026 г. в 18:01 UTCmonitoring

   Наша интеграция, Updox внедрила исправление и сообщает, что сервисы восстанавливаются. Мы продолжаем следить за восстановлением и наблюдаем улучшение сервиса. Некоторые пользователи могут по-прежнему испытывать периодические задержки или ошибки, в то время как системы полностью стабилизируются. Мы будем продолжать предоставлять обновления по мере их появления. Спасибо за терпение, пока этот вопрос решается.

3. 15 июля 2026 г. в 19:10 UTCresolved

   Наша интеграция, Updox, подтвердила, что сбой в обслуживании был устранен, и все службы работают.

Автоматический перевод официального обновления инцидента.

1. 7 июля 2026 г. в 16:59 UTCinvestigating

   В настоящее время мы знаем о системных проблемах, влияющих на DrChrono, и активно работаем с нашей инженерной командой, чтобы исследовать и решить проблему. Мы продолжим обновлять эту страницу.

2. 7 июля 2026 г. в 18:30 UTCinvestigating

   Мы продолжаем исследовать проблему, затрагивающую DrChrono. Наша инженерная команда активно работает над решением проблемы. Мы предоставим обновления на этой странице по мере их появления.

3. 7 июля 2026 г. в 19:55 UTCmonitoring

   Наша инженерная команда внедрила меры по смягчению последствий и продолжает следить за системой. Мы предоставим обновления на этой странице по мере их появления.

4. 8 июля 2026 г. в 14:04 UTCmonitoring

   Система остается работоспособной, и наша команда инженеров продолжает следить за платформой. Мы будем предоставлять обновления на этой странице по мере поступления дополнительной информации.

5. 8 июля 2026 г. в 20:29 UTCresolved

   Система остается работоспособной, и с момента перехода к мониторингу мы не наблюдали никаких дальнейших проблем. Этот инцидент был урегулирован. Наша инженерная команда продолжит рассматривать это событие в рамках наших постоянных усилий по поддержанию надежности и производительности платформы. Спасибо за терпение,

Автоматический перевод официального обновления инцидента.

1. 4 июня 2026 г. в 12:31 UTCinvestigating

   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. 4 июня 2026 г. в 13:49 UTCmonitoring

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

3. 4 июня 2026 г. в 19:02 UTCresolved

   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.

1. 3 июня 2026 г. в 15:49 UTCinvestigating

   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. 3 июня 2026 г. в 17:22 UTCinvestigating

   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. 3 июня 2026 г. в 18:50 UTCmonitoring

   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. 3 июня 2026 г. в 19:33 UTCresolved

   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.

1. 5 мая 2026 г. в 16:02 UTCinvestigating

   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. 5 мая 2026 г. в 17:39 UTCresolved

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

1. 6 апреля 2026 г. в 19:37 UTCinvestigating

   DrChrono has identified that a limited set of users may be experiencing slowness within the application. We are investigating the issue and will post updates every 60 minutes or as soon as they become available.

2. 6 апреля 2026 г. в 20:41 UTCmonitoring

   DrChrono has implemented mitigation steps to address the earlier reported slowness affecting a limited set of users while we continue to isolate the root cause. We are currently monitoring system performance to ensure stability.

3. 7 апреля 2026 г. в 17:34 UTCresolved

   DrChrono has resolved the issue that was causing slowness for a limited set of users. System performance has returned to normal, and we will continue to monitor to ensure ongoing stability.

1. 3 апреля 2026 г. в 14:15 UTCinvestigating

   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. 3 апреля 2026 г. в 15:41 UTCidentified

   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. 4 апреля 2026 г. в 11:11 UTCidentified

   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. 6 апреля 2026 г. в 14:03 UTCidentified

   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. 7 апреля 2026 г. в 16:30 UTCresolved

   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

1. 30 марта 2026 г. в 20:48 UTCinvestigating

   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. 30 марта 2026 г. в 22:05 UTCresolved

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

1. 25 марта 2026 г. в 16:59 UTCinvestigating

   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. 25 марта 2026 г. в 17:41 UTCinvestigating

   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. 25 марта 2026 г. в 21:36 UTCresolved

   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.

1. 24 марта 2026 г. в 19:17 UTCinvestigating

   Our team has identified reports of system slowness across various areas of the DrChrono website and are actively investigating. Updates will be provided as they become available.

2. 24 марта 2026 г. в 20:53 UTCinvestigating

   Our team is still actively investigating the system slowness impacting various areas of DrChrono. We understand the impact this may have on your workflows and will continue to share updates as we learn more.

3. 24 марта 2026 г. в 21:57 UTCmonitoring

   Our Engineering team is still actively investigating the system slowness impacting parts of the DrChrono website. Performance has improved, and we are continuing to monitor the system closely to ensure stability. We will provide further updates if any issues reoccur or once we confirm full resolution.

4. 24 марта 2026 г. в 22:34 UTCmonitoring

   We have identified a potential cause of the intermittent slowdowns during peak usage hours as elevated system activity. We are implementing targeted optimizations to reduce system load and improve performance. These changes are expected to stabilize behavior during high usage periods, and we are continuing to monitor closely.

5. 25 марта 2026 г. в 13:18 UTCresolved

   After a successful update, this issue will be monitored closely. If you have additional questions, please do not hesitate to contact support.

1. 23 марта 2026 г. в 19:55 UTCinvestigating

   Our team has identified reports of system slowness across various areas of the DrChrono website and are actively investigating. Updates will be provided as they become available. At this time, the DrChrono EHR mobile app remains fully functional.

2. 23 марта 2026 г. в 22:00 UTCmonitoring

   Our Engineering team is still actively investigating the system slowness previously impacting parts of the DrChrono website. Performance has improved, and we are continuing to monitor the system closely to ensure stability. We will provide further updates if any issues reoccur or once we confirm full resolution. At this time, the DrChrono EHR mobile app remains fully functional.

3. 23 марта 2026 г. в 23:54 UTCresolved

   The issue causing system slowness across portions of the DrChrono website has been resolved. All services are now functioning normally. We appreciate your patience and understanding.

1. 9 февраля 2026 г. в 14:55 UTCinvestigating

   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. 10 февраля 2026 г. в 16:30 UTCidentified

   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. 12 февраля 2026 г. в 22:18 UTCmonitoring

   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. 24 февраля 2026 г. в 20:59 UTCresolved

   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.

1. 6 февраля 2026 г. в 18:25 UTCinvestigating

   We are aware of an issue affecting a subset of users who are reporting that some 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. 6 февраля 2026 г. в 20:11 UTCidentified

   This incident is tied to a dependency on an external service that supports our reporting functionality. We are working in coordination with that provider to restore report availability as quickly as possible.

3. 6 февраля 2026 г. в 21:25 UTCmonitoring

   Reports are currently loading as expected, and the issue appears to have resolved. We are continuing to work with our external reporting service to determine the underlying cause and to confirm stability. We will remain in monitoring and provide updates if any further impact is observed.

4. 6 февраля 2026 г. в 21:27 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 7 февраля 2026 г. в 01:25 UTCmonitoring

   The issue affecting billing-related reports has been resolved and all reports are loading as expected. Our monitoring has remained stable with no further impact observed.

6. 7 февраля 2026 г. в 01:25 UTCresolved

   The issue affecting billing-related reports has been resolved and all reports are loading as expected. Our monitoring has remained stable with no further impact observed.

1. 9 января 2026 г. в 14:04 UTCinvestigating

   We are aware of the issue currently impacting some users and are actively investigating with our engineering team. Updates will be provided as they become available. At this time, the DrChrono EHR app remains fully functional. Thank you for your patience.

2. 9 января 2026 г. в 14:46 UTCidentified

   Some users may be experiencing certain pages in the DrChrono web application, including the Calendar, Clinical Notes, and Billing modules, not loading as expected. Our team is actively investigating. In the meantime, you can still view appointments and access patient charts by navigating to Schedule > Dashboard. This issue is limited to the web experience only. The DrChrono EHR mobile app is fully functional and can be used as an alternative to the web experience. We appreciate your patience and will continue to share updates as we learn more.

3. 9 января 2026 г. в 15:06 UTCmonitoring

   We have addressed the issue that was causing some pages in the DrChrono web application to not load as expected for some users. At this time, services appear to be functioning as expected. We are continuing to monitor closely to ensure stable performance.

4. 9 января 2026 г. в 15:44 UTCresolved

   The issue that caused some pages in the DrChrono web application to not load as expected has been resolved. All services are now functioning normally. We appreciate your patience and understanding.

1. 6 января 2026 г. в 00:28 UTCinvestigating

   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. 6 января 2026 г. в 01:24 UTCresolved

   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.

1. 17 декабря 2025 г. в 16:32 UTCinvestigating

   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. 17 декабря 2025 г. в 22:40 UTCidentified

   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. 18 декабря 2025 г. в 02:28 UTCmonitoring

   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. 18 декабря 2025 г. в 21:23 UTCresolved

   This incident has been resolved.

1. 18 ноября 2025 г. в 13:47 UTCinvestigating

   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. 18 ноября 2025 г. в 16:21 UTCmonitoring

   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. 18 ноября 2025 г. в 22:08 UTCresolved

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

1. 20 октября 2025 г. в 16:14 UTCinvestigating

   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. 20 октября 2025 г. в 16:14 UTCmonitoring

   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. 20 октября 2025 г. в 23:13 UTCresolved

   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.

1. 16 июля 2025 г. в 15:24 UTCidentified

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

2. 16 июля 2025 г. в 15:47 UTCidentified

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

3. 16 июля 2025 г. в 16:44 UTCidentified

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

4. 16 июля 2025 г. в 17:03 UTCmonitoring

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

5. 16 июля 2025 г. в 17:20 UTCresolved

   This incident has been resolved.

6. 18 июля 2025 г. в 21:11 UTCpostmortem

   **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.

1. 1 июля 2025 г. в 13:11 UTCidentified

   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. 1 июля 2025 г. в 20:44 UTCidentified

   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. 2 июля 2025 г. в 00:35 UTCresolved

   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.