DrChrono experienced a major incident on August 26, 2024 affecting drchrono.com, lasting 4h 47m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Aug 26, 2024, 04:00 PM UTC
DrChrono has identified that some users may experience slowness and/or errors within the application. We are investigating the issue and will post updates every 45 minutes.
- investigating Aug 26, 2024, 04:29 PM UTC
Our team continues to investigate the slowness and/or errors within DrChrono. We are working on a resolution with our third-party hosting provider. We will continue to provide updates every 45 minutes. Thank you for your patience.
- identified Aug 26, 2024, 04:29 PM UTC
Our team continues to investigate the slowness and/or errors within DrChrono. We are working on a resolution with our third-party hosting provider. We will continue to provide updates every 45 minutes. Thank you for your patience.
- identified Aug 26, 2024, 04:30 PM UTC
Our team continues to investigate the slowness and/or errors within DrChrono. We are working on a resolution with our third-party hosting provider. We will continue to provide updates every 45 minutes. Thank you for your patience.
- monitoring Aug 26, 2024, 05:33 PM UTC
We have implemented a fix for the slowness and/or error issue within DrChrono. We will continue to monitor along with our third-party hosting provider. We will continue to provide updates every 45 minutes. Thank you for your patience.
- monitoring Aug 26, 2024, 06:51 PM UTC
We continue to monitor the issue within our third party hosting provider that caused errors and intermittent slowness. This issue lasted between 11:45am ET and 12:45pm ET. We have seen no recurrence since this time frame. Our system health, response times and experience continue to be normal. We are working with our hosting provider to understand the root cause and permanent remediation. We are sorry for any inconveniences this has caused.
- resolved Aug 26, 2024, 08:48 PM UTC
We have seen no additional occurrences of this issue. We are transitioning this issue from monitoring to resolved.