- Detected by Pingoru
- Jun 11, 2026, 06:56 PM UTC
- Resolved
- Jun 12, 2026, 03:08 PM UTC
- Duration
- 20h 11m
Affected: Claim Submission
Timeline · 4 updates
-
identified Jun 11, 2026, 06:56 PM UTC
We have identified an issue with Optum (Change Healthcare) resulting in claims processing delays beginning June 10, 2025. All other Optum (Change Healthcare) integrations are functioning normally. No action is required — claims do not need to be rebilled and will process automatically once resolved. We are actively engaged with Optum (Change Healthcare) and will provide updates as information becomes available.
-
identified Jun 11, 2026, 09:09 PM UTC
Optum (Change Healthcare) is actively working to resolve the claims processing delays. We will continue to provide updates as information becomes available.
-
monitoring Jun 11, 2026, 11:01 PM UTC
Optum (Change Healthcare) has implemented a change and we are beginning to see claims transmit successfully. We will leave this incident open while we monitor to ensure all queued claims have processed. Please note that this may take many hours to fully complete. Our next update will be provided no later than tomorrow morning at 9:00 AM MT.
-
resolved Jun 12, 2026, 03:08 PM UTC
All delayed claims have been processed. This incident is now resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 10, 2026, 12:46 PM UTC
- Resolved
- Jun 10, 2026, 01:59 PM UTC
- Duration
- 1h 12m
Affected: ePrescribing
Timeline · 4 updates
-
investigating Jun 10, 2026, 12:46 PM UTC
We are currently investigating an issue where some users are receiving an error when sending ePrescriptions. Our technical teams are actively engaged and working to resolve the issue. Our Incident Managers will continue to provide updates here as additional information becomes available.
-
investigating Jun 10, 2026, 01:12 PM UTC
We are investigating an issue where users are receiving errors when sending prescriptions. We are engaging with our third-party partner to resolve the issue. Our next update will be provided in approximately 30 minutes. Our Incident Managers will continue to provide updates here as additional information becomes available.
-
identified Jun 10, 2026, 01:38 PM UTC
We have identified the issue and are working on implementing a solution. Our next update will be provided by 8:30 AM MT. Our Incident Managers will continue to provide updates here as additional information becomes available.
-
resolved Jun 10, 2026, 01:59 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 27, 2026, 01:02 AM UTC
- Resolved
- May 27, 2026, 12:08 PM UTC
- Duration
- 11h 5m
Affected: ePrescribing
Timeline · 3 updates
-
monitoring May 27, 2026, 01:02 AM UTC
We are currently aware of an ongoing issue with DrFirst that is impacting the ability to electronically prescribe controlled substances for some providers. Our team is actively monitoring the situation and working with DrFirst as they investigate and resolve the outage. Non-controlled substance prescribing and other platform functions remain available unless otherwise noted. We will continue to share updates as more information becomes available. Thank you for your patience and understanding.
-
monitoring May 27, 2026, 04:33 AM UTC
DrFirst is still investigating the issue. We will continue to share updates as more information becomes available. Thank you for your patience and understanding.
-
resolved May 27, 2026, 12:08 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 07, 2026, 01:23 PM UTC
- Resolved
- May 07, 2026, 05:45 PM UTC
- Duration
- 4h 21m
Affected: Claim StatusEligibility
Timeline · 5 updates
-
investigating May 07, 2026, 01:23 PM UTC
We are currently investigating an issue affecting eligibility responses for some users. Affected users may see the following error: "Error while retrieving Eligibility Response." The issue is related to our Change Healthcare (Optum) integration. We will provide updates as more information becomes available.
-
identified May 07, 2026, 02:21 PM UTC
We are actively working with Change Healthcare (Optum) to resolve the "Error while retrieving Eligibility Response" error. There is no workaround available at this time. We will provide updates as more information becomes available.
-
identified May 07, 2026, 03:09 PM UTC
Change Healthcare (Optum) has confirmed an outage affecting their services. AdvancedMD users may experience issues with real-time eligibility, claim status, and enrollments. Change Healthcare (Optum) is working to resolve the issue. We will continue to provide updates as more information becomes available.
-
identified May 07, 2026, 04:03 PM UTC
Change Healthcare (Optum) has confirmed an outage affecting their services. AdvancedMD users may experience issues with real-time eligibility, claim status, and enrollments. Change Healthcare (Optum) is working to resolve the issue. Users can view incident notifications on the Change Healthcare status page at https://status.optum.com/.
-
resolved May 07, 2026, 05:45 PM UTC
Change Healthcare (Optum) has resolved the issue on their end. Eligibility and status checks are now processing normally. Recommended action: If you submitted eligibility requests during the outage window, please resubmit them if you need results today. Any failed runs will rerun overnight. No data was lost — this was a connectivity interruption only. We apologize for the disruption and appreciate your patience. For questions, contact AdvancedMD Support.
Read the full incident report →
- Detected by Pingoru
- May 06, 2026, 08:48 PM UTC
- Resolved
- May 06, 2026, 09:05 PM UTC
- Duration
- 17m
Affected: Electronic Health Records (EHR)
Timeline · 3 updates
-
investigating May 06, 2026, 08:48 PM UTC
We are aware of an issue affecting the EHR dashboard and patient charts. Some users may encounter errors when loading dashboard widgets or attempting to open a patient chart. Our team is actively investigating and working to resolve this as quickly as possible. We will continue to provide updates as more information becomes available.
-
monitoring May 06, 2026, 09:02 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved May 06, 2026, 09:05 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 01, 2026, 04:04 PM UTC
- Resolved
- May 01, 2026, 04:36 PM UTC
- Duration
- 32m
Affected: ePrescribing
Timeline · 2 updates
-
investigating May 01, 2026, 04:04 PM UTC
We are currently investigating reports that clients are experiencing errors when eSending controlled substances. When attempting to sign and send, you may receive an error stating that one or more prescriptions cannot be sent, and affected prescriptions will show a pending status with Dr. First in the eSend Status Report. Our technical teams are actively engaged and working to resolve the issue. We recommend holding off on eSending controlled substance prescriptions until this issue is resolved to avoid additional prescriptions entering a pending state. Non-controlled substance prescriptions are not affected and can continue to be sent normally. Incident Managers will continue to provide updates here as additional information becomes available
-
resolved May 01, 2026, 04:36 PM UTC
Some prescriptions may have failed due to an authentication issue. If you see a failed or pending prescription, use the steps below to re authenticate and resend. 1. Open the E send Status screen and Navigate to Reports → E send Status → Prescriptions. 2. Find failed or pending prescriptions. Look for prescriptions in a Pending state (orange icon), or filter by Pending. 3. Open the prescription. The status will update. 4. If it failed, resend EPCS 5. Re authenticate when prompted. Complete the DrFirst authentication when the prompt appears. 6. Expected result In many cases, the prescription failed because the authentication was not received by DrFirst. After resending, the authentication screen should open and the prescription should process successfully.
Read the full incident report →
- Detected by Pingoru
- Apr 17, 2026, 12:59 PM UTC
- Resolved
- Apr 17, 2026, 01:24 PM UTC
- Duration
- 24m
Affected: Practice Management (PM)
Timeline · 2 updates
-
investigating Apr 17, 2026, 12:59 PM UTC
We are currently investigating reports of intermittent issues related to claims processing. Our technical teams are actively engaged and working to resolve the issue. Incident Managers will continue to provide updates here as additional information becomes available.
-
resolved Apr 17, 2026, 01:24 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 15, 2026, 01:32 PM UTC
- Resolved
- Apr 15, 2026, 02:05 PM UTC
- Duration
- 33m
Affected: Client Services Support
Timeline · 2 updates
-
investigating Apr 15, 2026, 01:32 PM UTC
We are currently experiencing an issue affecting our Support chat service. As a result, you may be unable to reach our Client Support team via chat. We are actively working to restore service. Clients needing immediate assistance are encouraged to call us at (888) 700-9060. Our Incident Managers will continue to post updates as new information becomes available.
-
resolved Apr 15, 2026, 02:05 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 07, 2026, 06:59 PM UTC
- Resolved
- Apr 08, 2026, 09:05 PM UTC
- Duration
- 1d 2h
Affected: Eligibility
Timeline · 9 updates
Read the full incident report →
- Detected by Pingoru
- Apr 03, 2026, 05:31 PM UTC
- Resolved
- Apr 03, 2026, 10:42 PM UTC
- Duration
- 5h 11m
Affected: Eligibility
Timeline · 5 updates
-
investigating Apr 03, 2026, 05:31 PM UTC
We are currently investigating an issue affecting eligibility verification for some clients. Some users may be experiencing eligibility errors or delays in processing. Our team has identified the issue and is actively working on a resolution. As a precautionary measure, we have implemented interim steps to restore processing, and queues are returning to normal levels. We will provide a further update as soon as more information is available. We apologize for any inconvenience this may cause.
-
investigating Apr 03, 2026, 06:50 PM UTC
We are continuing to investigate this issue.
-
identified Apr 03, 2026, 07:47 PM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Apr 03, 2026, 09:13 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Apr 03, 2026, 10:42 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 24, 2026, 06:41 PM UTC
- Resolved
- Mar 24, 2026, 07:30 PM UTC
- Duration
- 49m
Affected: Practice Management (PM)Claim Submission
Timeline · 3 updates
-
investigating Mar 24, 2026, 06:41 PM UTC
We are currently investigating an issue affecting claims submission. Some clients are reporting errors when generating claims or editing charges. Our technical teams are actively engaged and working to identify the root cause and restore full functionality. Incident Managers will continue to provide updates here as additional information becomes available
-
monitoring Mar 24, 2026, 07:06 PM UTC
The issue has been resolved. If errors persist, please retry your claims run. We are continuing to monitor the results.
-
resolved Mar 24, 2026, 07:30 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 20, 2026, 01:42 PM UTC
- Resolved
- Mar 20, 2026, 05:09 PM UTC
- Duration
- 3h 26m
Affected: Electronic Health Records (EHR)
Timeline · 5 updates
-
investigating Mar 20, 2026, 01:42 PM UTC
We are investigating an issue where clients are receiving a "Control Not Found" 404 error when saving a sub note. Our technical teams are engaged and actively working to resolve the issue. Incident managers will continue to provide updates here as additional information becomes available.
-
investigating Mar 20, 2026, 03:00 PM UTC
We are continuing to investigate this issue.
-
identified Mar 20, 2026, 04:02 PM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Mar 20, 2026, 04:43 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Mar 20, 2026, 05:09 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 12, 2026, 07:11 PM UTC
- Resolved
- Mar 12, 2026, 07:30 PM UTC
- Duration
- 18m
Affected: Practice Management (PM)
Timeline · 2 updates
-
investigating Mar 12, 2026, 07:11 PM UTC
AdvancedMD clients using AMDPay are reporting errors when processing credit card payments. Our Incident Management team is engaged and will continue to provide updates here as additional information becomes available.
-
resolved Mar 12, 2026, 07:30 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 12, 2026, 12:16 AM UTC
- Resolved
- Mar 12, 2026, 03:22 AM UTC
- Duration
- 3h 5m
Affected: Practice Management (PM)
Timeline · 3 updates
-
investigating Mar 12, 2026, 12:16 AM UTC
We are currently investigating an issue that began at approximately 4:30 PM, where some claim runs are failing and returning the error message: “Error #0: Claims were found, but no transformation was found to generate the result.” Our technical teams are actively engaged and working to resolve the issue. Incident Managers will continue to provide updates here as additional information becomes available.
-
investigating Mar 12, 2026, 02:14 AM UTC
We are continuing to investigate this issue.
-
resolved Mar 12, 2026, 03:22 AM UTC
A fix has been implemented, and claim processing has been restored. Any claim runs that encountered the “Error #0: Claims were found, but no transformation was found to generate the result…” during this incident were not billed and will be automatically included in the next subsequent claim run. No additional action is required. We apologize for the disruption and appreciate your patience.
Read the full incident report →
- Detected by Pingoru
- Mar 10, 2026, 04:18 PM UTC
- Resolved
- Mar 10, 2026, 08:20 PM UTC
- Duration
- 4h 1m
Affected: Practice Management (PM)Electronic Health Records (EHR)
Timeline · 6 updates
-
investigating Mar 10, 2026, 04:18 PM UTC
Some customers may notice slower than usual performance when using the Practice Management (PM) and Electronic Health Record (EHR) system. Our teams are actively investigating and working to improve performance as quickly as possible. This issue is not affecting all customers and is currently limited to those within Pool 133. We understand that performance issues can be disruptive, and we appreciate your patience. We will continue to share updates here as more information becomes available.
-
investigating Mar 10, 2026, 05:01 PM UTC
We are continuing to investigate this issue.
-
investigating Mar 10, 2026, 06:03 PM UTC
We are continuing to investigate this issue.
-
monitoring Mar 10, 2026, 06:26 PM UTC
A fix has been implemented and we are monitoring the results.
-
monitoring Mar 10, 2026, 06:27 PM UTC
We are continuing to monitor for any further issues.
-
resolved Mar 10, 2026, 08:20 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 10, 2026, 12:40 PM UTC
- Resolved
- Mar 10, 2026, 01:46 PM UTC
- Duration
- 1h 5m
Affected: Fax
Timeline · 2 updates
-
investigating Mar 10, 2026, 12:40 PM UTC
Our third party partner, Updox, is currently experiencing a service disruption. Users may encounter errors when uploading, viewing, or sending documents. Our incident managers will continue to monitor the situation and provide updates as they become available. Users can subscribe to incident updates on Updox’s status page at https://partnerstatus.updox.com/.
-
resolved Mar 10, 2026, 01:46 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 04, 2026, 10:57 PM UTC
- Resolved
- Mar 04, 2026, 11:29 PM UTC
- Duration
- 31m
Affected: Waystar Portal Single Sign-On (SSO)
Timeline · 2 updates
-
investigating Mar 04, 2026, 10:57 PM UTC
We are actively working to resolve an issue that is preventing users from accessing the Waystar Portal through Single Sign-On. Our technical teams are investigating and working toward a resolution. Incident Managers will provide updates on the Status Page as more information becomes available.
-
resolved Mar 04, 2026, 11:29 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 24, 2026, 06:52 PM UTC
- Resolved
- Feb 24, 2026, 07:41 PM UTC
- Duration
- 48m
Affected: Fax
Timeline · 3 updates
-
investigating Feb 24, 2026, 06:52 PM UTC
Updox, our fax service provider, is currently experiencing system slowdowns. Some AdvancedMD fax users may notice delays as a result. We are actively monitoring the situation and will provide updates as they become available.
-
monitoring Feb 24, 2026, 07:22 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Feb 24, 2026, 07:41 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 18, 2026, 07:03 PM UTC
- Resolved
- Feb 18, 2026, 07:51 PM UTC
- Duration
- 47m
Affected: Electronic Health Records (EHR)
Timeline · 2 updates
-
monitoring Feb 18, 2026, 07:03 PM UTC
We experienced login issues affecting some EHR customers and have implemented a fix. Access has been restored, and our teams will continue monitoring to ensure full stability.
-
resolved Feb 18, 2026, 07:51 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 18, 2026, 05:28 PM UTC
- Resolved
- Feb 19, 2026, 01:32 AM UTC
- Duration
- 8h 3m
Affected: Practice Management (PM)
Timeline · 4 updates
-
identified Feb 18, 2026, 05:28 PM UTC
We have identified an issue where some users experience an intermittent pop‑up message upon logging into the PM that states: “Please close the window and re‑log in.” Our technical teams are actively engaged and working to resolve the issue. Incident Managers will continue to provide updates as additional information becomes available. Workaround: Refreshing the browser typically clears the message. - Windows (Edge and Chrome): Press F5 to refresh the page - Mac (Safari and Chrome): Go to View → Reload Page - Mac Chrome: Press Shift + Command + R Note: This action may have to be repeated as needed and moving past the error without refreshing may cause an error-prone session.
-
identified Feb 18, 2026, 07:17 PM UTC
We are continuing to work on a fix for this issue.
-
monitoring Feb 18, 2026, 11:09 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Feb 19, 2026, 01:32 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 03, 2026, 01:27 AM UTC
- Resolved
- Feb 03, 2026, 02:03 AM UTC
- Duration
- 35m
Affected: Fax
Timeline · 2 updates
-
identified Feb 03, 2026, 01:27 AM UTC
Our third-party partner, Updox, is currently experiencing an outage that impacts our clients’ ability to use AdvancedMD Fax. Our incident managers will continue to monitor the situation and provide updates as they become available. Users can subscribe to incident updates on Updox’s status page at https://partnerstatus.updox.com/.
-
resolved Feb 03, 2026, 02:03 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 02, 2026, 05:15 PM UTC
- Resolved
- Feb 02, 2026, 05:19 PM UTC
- Duration
- 3m
Affected: Client Services Support
Timeline · 2 updates
-
investigating Feb 02, 2026, 05:15 PM UTC
We are currently experiencing a network issue affecting our phone system. As a result, you may have difficulty reaching our Client Support team by phone. We are actively working to restore service. Clients needing assistance are encouraged to use the Chat service in the meantime. Our Incident Managers will continue to post updates as new information becomes available.
-
resolved Feb 02, 2026, 05:19 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jan 22, 2026, 08:33 PM UTC
- Resolved
- Jan 23, 2026, 03:18 PM UTC
- Duration
- 18h 45m
Affected: Practice Management (PM)Patient MessagingElectronic Health Records (EHR)
Timeline · 7 updates
-
investigating Jan 22, 2026, 08:33 PM UTC
We are aware of an issue preventing clients using two‑factor authentication from logging in to AdvancedMD. Our technical teams are actively investigating and working toward a resolution.
-
investigating Jan 22, 2026, 09:34 PM UTC
Clients using two‑factor authentication may be unable to log in to AdvancedMD due to an AWS‑related messaging delay. We are actively engaged with AWS as they work to restore normal delivery performance.
-
investigating Jan 22, 2026, 11:02 PM UTC
We are still actively engaged with AWS while they work to restore normal delivery performance.
-
investigating Jan 23, 2026, 12:19 AM UTC
Our applications remain fully functional. AWS has identified that the current issue affects customers sending mail through Microsoft‑hosted mail servers. Microsoft is currently experiencing mail‑delivery issues, which may impact email‑based workflows such as notifications or verification messages. You can view Microsoft’s official service‑health notice here: https://status.cloud.microsoft/. We are continuing to monitor the situation and will provide updates as AWS and Microsoft progress with their remediation.
-
monitoring Jan 23, 2026, 04:17 AM UTC
Microsoft is continuing to work toward resolving their Microsoft 365 incident. This issue has been intermittently impacting the following AdvancedMD workflows: Logging into AdvancedMD using Two‑Factor Authentication (2FA) Patient workflows that involve sending or receiving emails may be affected if the recipient uses Microsoft‑hosted email services (e.g., Telehealth, Patient Portal, Appointment Reminders) You can view Microsoft’s official service health notice here: https://status.cloud.microsoft/. We will continue to monitor the situation and provide updates as they become available.
-
monitoring Jan 23, 2026, 05:55 AM UTC
Microsoft has reported a high level of confidence that their Microsoft 365 incident is largely resolved. We will continue to closely monitor the situation throughout the evening to ensure there is no further impact to AdvancedMD services. Updates will be posted if conditions change. There may still be lingering impacts to Patient Messaging for recipients who use Microsoft‑hosted email services (e.g., Telehealth, Patient Portal, Appointment Reminders).
-
resolved Jan 23, 2026, 03:18 PM UTC
We have confirmed that Two-Factor Authentication (2FA) and Patient Messaging services remain functional. While we do not have evidence of any messaging service failures, Telehealth, Appointment Reminder, and Patient Portal messages may have experienced delays.
Read the full incident report →
- Detected by Pingoru
- Jan 08, 2026, 05:19 PM UTC
- Resolved
- Jan 08, 2026, 11:41 PM UTC
- Duration
- 6h 22m
Affected: Practice Management (PM)
Timeline · 3 updates
-
investigating Jan 08, 2026, 05:19 PM UTC
We are investigating an issue where some claim runs remain in a pending state or fail to process. Our technical teams are actively working to resolve the problem. Incident Managers will provide updates on the Status Page as more information becomes available.
-
monitoring Jan 08, 2026, 08:03 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jan 08, 2026, 11:41 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jan 08, 2026, 04:40 PM UTC
- Resolved
- Jan 08, 2026, 11:29 PM UTC
- Duration
- 6h 49m
Affected: Practice Management (PM)
Timeline · 3 updates
Read the full incident report →