{
"vendor": "Drchrono",
"slug": "drchrono",
"platform": "statuspage",
"status_url": "https://status.drchrono.com",
"last_checked": "2026-09-16T12:28:20Z",
"last_state": "ok",
"history_backfilled": true,
"first_watched": "2026-09-04T07:06:16Z",
"incidents": [
{
"body": "Our integration, Updox, has confirmed that the service disruption has been resolved and all services are operational.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-07-15T12:10:22.072-07:00",
"resolved_inferred": false,
"started_at": "2026-07-15T10:42:54.974-07:00",
"state": "resolved",
"title": "Integration Issues 7.15.26",
"updated_at": "2026-07-15T12:10:22.087-07:00",
"url": "https://stspg.io/xy00ybwzv7c8"
},
{
"body": "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,",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "critical",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-07-08T13:29:53.823-07:00",
"resolved_inferred": false,
"started_at": "2026-07-07T09:59:43.380-07:00",
"state": "resolved",
"title": "DrChrono System Issues",
"updated_at": "2026-07-08T13:29:53.842-07:00",
"url": "https://stspg.io/gdlp2ls5yqd9"
},
{
"body": "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.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-06-04T12:02:14.364-07:00",
"resolved_inferred": false,
"started_at": "2026-06-04T05:31:50.447-07:00",
"state": "resolved",
"title": "DrChrono Slowness",
"updated_at": "2026-06-04T12:02:14.379-07:00",
"url": "https://stspg.io/ts74rrn2shk0"
},
{
"body": "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.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-06-03T12:33:58.000-07:00",
"resolved_inferred": false,
"started_at": "2026-06-03T08:49:03.547-07:00",
"state": "resolved",
"title": "DrChrono Intermittent Issues",
"updated_at": "2026-06-03T13:01:19.391-07:00",
"url": "https://stspg.io/s7pgglzvlg5f"
},
{
"body": "The issue impacting appointment reminders has been resolved. All systems are now operating normally. Thank you for your patience.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-05-05T10:39:50.078-07:00",
"resolved_inferred": false,
"started_at": "2026-05-05T09:02:17.705-07:00",
"state": "resolved",
"title": "Appointment Reminder Issue",
"updated_at": "2026-05-05T10:39:50.091-07:00",
"url": "https://stspg.io/fdlxvnn4nst2"
},
{
"body": "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.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-04-07T10:34:20.460-07:00",
"resolved_inferred": false,
"started_at": "2026-04-06T12:37:08.555-07:00",
"state": "resolved",
"title": "DrChrono Slowness",
"updated_at": "2026-04-07T10:34:20.478-07:00",
"url": "https://stspg.io/tpyrk7sf4fbq"
},
{
"body": "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.\n \nRecommended Action:\nIf you previously switched to an alternate MFA method (such as an authenticator app or SMS), you may switch back to Push Notifications. \n \nFor steps to update your MFA method, visit:\nhttps://support.drchrono.com/home/360051657392-adding-or-changing-a-device-for-multi-factor-authentication-with-id-me\n \nIf you continue to experience login issues, you may still follow ID.me\u2019s recovery steps:\nhttps://help.id.me/hc/en-us/articles/360017927633-ID-me-MFA-recovery-steps-if-you-lost-access-or-can-t-sign-in",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-04-07T09:30:55.076-07:00",
"resolved_inferred": false,
"started_at": "2026-04-03T07:15:20.416-07:00",
"state": "resolved",
"title": "EPCS Prescription Issue ID.me",
"updated_at": "2026-04-07T09:30:55.095-07:00",
"url": "https://stspg.io/87k48tw51wmg"
},
{
"body": "Our engineering team has resolved the issue, and system performance has returned to normal. We appreciate your patience.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-03-30T15:05:30.638-07:00",
"resolved_inferred": false,
"started_at": "2026-03-30T13:48:56.084-07:00",
"state": "resolved",
"title": "System Slowness",
"updated_at": "2026-03-30T15:05:30.653-07:00",
"url": "https://stspg.io/kdbh696yp8c8"
},
{
"body": "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.\n \nOvernight, 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.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-03-25T14:36:19.000-07:00",
"resolved_inferred": false,
"started_at": "2026-03-25T09:59:29.379-07:00",
"state": "resolved",
"title": "DrChrono Web System Issues",
"updated_at": "2026-04-24T07:48:38.291-07:00",
"url": "https://stspg.io/s41t86phg9wx"
},
{
"body": "After a successful update, this issue will be monitored closely. If you have additional questions, please do not hesitate to contact support.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-03-25T06:18:42.000-07:00",
"resolved_inferred": false,
"started_at": "2026-03-24T12:17:23.000-07:00",
"state": "resolved",
"title": "DrChrono Web System Issues",
"updated_at": "2026-03-25T06:19:17.246-07:00",
"url": "https://stspg.io/qstbw0y9fxh6"
},
{
"body": "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.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-03-23T16:54:39.949-07:00",
"resolved_inferred": false,
"started_at": "2026-03-23T12:55:24.987-07:00",
"state": "resolved",
"title": "DrChrono Web System Issues",
"updated_at": "2026-03-23T16:54:39.967-07:00",
"url": "https://stspg.io/cjxvb7bjdhhh"
},
{
"body": "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.\n\nThank you for your patience while we worked through this issue.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-02-24T12:59:42.677-08:00",
"resolved_inferred": false,
"started_at": "2026-02-09T06:55:45.414-08:00",
"state": "resolved",
"title": "Issue Loading Billing-Related Reports",
"updated_at": "2026-02-24T12:59:42.691-08:00",
"url": "https://stspg.io/ng9h3md9dh5r"
},
{
"body": "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.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-02-06T17:25:45.658-08:00",
"resolved_inferred": false,
"started_at": "2026-02-06T10:25:44.000-08:00",
"state": "resolved",
"title": "Issue Loading Billing-Related Reports",
"updated_at": "2026-02-06T17:25:45.674-08:00",
"url": "https://stspg.io/rtxbdl3h8zkv"
},
{
"body": "The issue that caused some pages in the DrChrono web application to not load as expected has been resolved.\n\nAll services are now functioning normally.\n\nWe appreciate your patience and understanding.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-01-09T07:44:34.635-08:00",
"resolved_inferred": false,
"started_at": "2026-01-09T06:04:41.156-08:00",
"state": "resolved",
"title": "DrChrono Web System Issues",
"updated_at": "2026-01-09T07:44:34.663-08:00",
"url": "https://stspg.io/20fy8l0xwyhx"
},
{
"body": "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.\n \nAt this time, prescriptions should be sending successfully without interruption. Our team will continue to actively monitor the system to ensure stability and prevent recurrence.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-01-05T17:24:32.221-08:00",
"resolved_inferred": false,
"started_at": "2026-01-05T16:28:56.054-08:00",
"state": "resolved",
"title": "Prescription Issues",
"updated_at": "2026-01-05T17:24:32.239-08:00",
"url": "https://stspg.io/06lpn2sgs3l4"
},
{
"body": "This incident has been resolved.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-12-18T13:23:17.697-08:00",
"resolved_inferred": false,
"started_at": "2025-12-17T08:32:42.904-08:00",
"state": "resolved",
"title": "Patient Search Issues",
"updated_at": "2025-12-18T13:23:17.714-08:00",
"url": "https://stspg.io/0fbcn1bzcqdd"
},
{
"body": "This issue has been resolved. Please contact support if you are still experiencing issues.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-11-18T14:08:41.787-08:00",
"resolved_inferred": false,
"started_at": "2025-11-18T05:47:16.000-08:00",
"state": "resolved",
"title": "Cloudfare Global Network Outage",
"updated_at": "2025-11-18T14:08:41.803-08:00",
"url": "https://stspg.io/p9zw2jy6z304"
},
{
"body": "We\u2019re 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.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-10-20T16:13:45.329-07:00",
"resolved_inferred": false,
"started_at": "2025-10-20T09:14:15.455-07:00",
"state": "resolved",
"title": "AWS Ongoing Issues",
"updated_at": "2025-10-20T16:13:45.348-07:00",
"url": "https://stspg.io/6crzwkfpyn75"
}
]
}