AWS Ongoing Issues

Incident Report for DrChrono

Resolved

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.
Posted Oct 20, 2025 - 16:13 PDT

Monitoring

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.
Posted Oct 20, 2025 - 09:14 PDT

Investigating

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.
Posted Oct 20, 2025 - 09:14 PDT
This incident affected: drchrono.com.