Is DrChrono down?

Product match: components.

Read the provider’s incident report

1. 2026-07-08T13:29:53.823-07:00 · resolved

   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,

2. 2026-07-08T07:04:45.878-07:00 · monitoring

   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.

3. 2026-07-07T12:55:40.820-07:00 · monitoring

   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. 2026-07-07T11:30:15.089-07:00 · investigating

   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.

5. 2026-07-07T09:59:43.457-07:00 · investigating

   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.

Product match: components.

Read the provider’s incident report

1. 2026-06-04T12:02:14.364-07:00 · resolved

   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.

2. 2026-06-04T06:49:32.976-07:00 · monitoring

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

3. 2026-06-04T06:46:51.922-07:00 · monitoring

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

4. 2026-06-04T05:31:50.561-07:00 · investigating

   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.

Product match: components.

Read the provider’s incident report

1. 2026-06-03T12:33:58.000-07:00 · resolved

   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.

2. 2026-06-03T11:50:21.663-07:00 · monitoring

   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.

3. 2026-06-03T10:22:48.397-07:00 · investigating

   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.

4. 2026-06-03T08:49:03.638-07:00 · investigating

   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.

Product match: components.

Read the provider’s incident report

1. 2026-05-05T10:39:50.078-07:00 · resolved

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

2. 2026-05-05T09:02:17.773-07:00 · investigating

   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.

Product match: components.

Read the provider’s incident report

1. 2026-04-07T10:34:20.460-07:00 · resolved

   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.

2. 2026-04-06T13:41:45.987-07:00 · monitoring

   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. 2026-04-06T12:37:08.639-07:00 · investigating

   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.

Product match: components.

Read the provider’s incident report

1. 2026-04-07T09:30:55.076-07:00 · resolved

   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

2. 2026-04-06T07:03:32.621-07:00 · identified

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

3. 2026-04-04T04:11:44.798-07:00 · identified

   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

4. 2026-04-03T08:41:51.000-07:00 · identified

   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.

5. 2026-04-03T07:15:20.517-07:00 · investigating

   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.

Product match: components.

Read the provider’s incident report

1. 2026-03-30T15:05:30.638-07:00 · resolved

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

2. 2026-03-30T13:48:56.161-07:00 · investigating

   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.

Product match: components.

Read the provider’s incident report

1. 2026-03-25T14:36:19.000-07:00 · resolved

   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 s

2. 2026-03-25T10:41:06.806-07:00 · investigating

   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 availabl

3. 2026-03-25T09:59:29.487-07:00 · investigating

   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 updat

Provider reports operational. Mapped components are operational in the latest status update; individual experiences can vary. This page was assembled at 2026-10-20T04:20:37.000Z.

The displayed rolling 24-hour window contains 0 recorded reports, from 2026-10-19T04:20:00.000Z to 2026-10-20T04:20:00.000Z. This is not a calendar-day total or a count of affected people. Estimated activity is shown separately as an estimate.

An official operational status can coexist with a local network issue, account problem, or feature-specific incident. Compare the mapped components, recent incident updates, and regional diagnostic on this page. Automated website checks test public access, not your signed-in session or every DrChrono feature.

The latest status observation was 2026-10-20T04:15:34.000Z. Only matched product components and incidents are shown. The assessment is recent.

The daily calendar links available incident evidence and retains daily monitoring summaries. Pink marks service issues, green requires sufficient observations with no issues observed, and gray means insufficient coverage. The collected history is incomplete and is not a lifetime outage count or a guarantee of uninterrupted uptime.

Use “Watch this service” to save DrChrono in this browser’s watchlist, then return to compare its status with other saved services. The watchlist does not send notifications. Use the problem-report button for an outage report; contact the provider through its official website for account, billing, or private support issues. Iszdown is independent and cannot resolve provider support tickets.