DrChrono experienced a minor incident on July 30, 2024 affecting drchrono.com and drchrono iPad EHR and 1 more component, lasting 15h 28m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jul 30, 2024, 10:22 PM UTC
DrChrono has identified that some users may experience slowness within the application. We are investigating the issue and will post updates every 60 minutes.
- investigating Jul 30, 2024, 10:35 PM UTC
We are continuing to investigate this issue.
- identified Jul 30, 2024, 10:45 PM UTC
We have identified the issue to be related to ongoing API issues with our hosting provider. We are attempting to identify a workaround while they resolve their issue in parallel. We will continue to update this page.
- identified Jul 30, 2024, 11:49 PM UTC
We have identified a workaround and are working to deploy the change to mitigate the errors we are experiencing due to our hosting provider. We will provide another update in 60 minutes.
- identified Jul 31, 2024, 12:15 AM UTC
We have partially deployed the identified workaround to circumvent issues being experienced by a regional outage for several services within our hosting provider. Via internal testing, we can confirm that most users should be able to access the system and experience normal response times. We are working to finalize the deployment of the workaround and will update accordingly.
- monitoring Jul 31, 2024, 12:54 AM UTC
We have fully deployed our workaround to circumvent issues being experienced by a regional outage for several services within our hosting provider. Users should be experiencing normal response times. For users that are not, please contact support. We are continuing to monitor in case additional changes are necessary.
- resolved Jul 31, 2024, 01:51 PM UTC
As of 12am ET, our hosting provider resolved the issues experienced for several services within our primary region. As of 8:30 ET this morning, we verified their fix and removed workarounds that were temporarily put in place. After a period of monitoring, we can confirm users are experiencing normal response times. We are transitioning this from monitoring to considered resolved.