AdvancedMD Outage History

AdvancedMD is up right now

There were 16 AdvancedMD outages since February 3, 2026 totaling 56h 22m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.advancedmd.com

Major May 1, 2026

eSending Controlled Substances — Prescriptions Stuck in Pending

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
  1. 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

  2. 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 →

Minor April 17, 2026

Degraded Claims Processing

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
  1. 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.

  2. resolved Apr 17, 2026, 01:24 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 15, 2026

Limited Access to Client Support Chat

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
  1. 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.

  2. resolved Apr 15, 2026, 02:05 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 7, 2026

Eligibility Processing Error: Invalid Participant Identification / Credentials not associated with user

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
  1. investigating Apr 07, 2026, 06:59 PM UTC

    We are actively investigating an intermittent issue where some eligibility responses are returning an "Invalid Participant Identification / Credentials not associated with user" error. Our technical teams are engaged and working to identify the root cause and restore full functionality. Incident Managers will continue to provide updates here as additional information becomes

  2. identified Apr 07, 2026, 08:19 PM UTC

    The issue has been identified and a fix is being implemented.

  3. identified Apr 07, 2026, 11:29 PM UTC

    We are continuing to work on a fix for this issue.

  4. investigating Apr 08, 2026, 01:36 AM UTC

    We are continuing to work to resolve the eligibility error causing an "Invalid Participant Identification / Credentials not associated with user" error for some clients. Our engineering team is working to resolve this as quickly as possible, and we are collaborating with our clearinghouse partner to assist in the resolution. We will continue to provide updates as new information becomes available.

  5. investigating Apr 08, 2026, 04:05 AM UTC

    We continue to work to resolve the eligibility issue resulting in an "Invalid Participant Identification / Credentials not associated with user" error for some clients. Our engineering team is collaborating with our clearinghouse partner to assist in the resolution. Our next update will be provided by 9:00 AM MT.

  6. identified Apr 08, 2026, 03:03 PM UTC

    We have identified the root cause of the eligibility issue resulting in an "Invalid Participant Identification / Credentials not associated with user" error and are actively working to implement a solution. Our next update will be provided by 1:00 PM MT.

  7. identified Apr 08, 2026, 06:20 PM UTC

    We understand the disruption this issue is causing and sincerely apologize. We have identified the root cause of the eligibility issue resulting in an "Invalid Participant Identification / Credentials not associated with user" error and are actively validating a fix. Our next update will be provided no later than 2:30 PM MT.

  8. monitoring Apr 08, 2026, 08:47 PM UTC

    A fix has been implemented and we are monitoring the results.

  9. resolved Apr 08, 2026, 09:05 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 3, 2026

Eligibility Processing Intermittent Errors

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
  1. 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.

  2. investigating Apr 03, 2026, 06:50 PM UTC

    We are continuing to investigate this issue.

  3. identified Apr 03, 2026, 07:47 PM UTC

    The issue has been identified and a fix is being implemented.

  4. monitoring Apr 03, 2026, 09:13 PM UTC

    A fix has been implemented and we are monitoring the results.

  5. resolved Apr 03, 2026, 10:42 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 24, 2026

Claims Submission Errors

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
  1. 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

  2. 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.

  3. resolved Mar 24, 2026, 07:30 PM UTC

    This incident has been resolved.

Read the full incident report →

Major March 20, 2026

EHR Notes Error – "Control Not Found" (Error 404)

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
  1. 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.

  2. investigating Mar 20, 2026, 03:00 PM UTC

    We are continuing to investigate this issue.

  3. identified Mar 20, 2026, 04:02 PM UTC

    The issue has been identified and a fix is being implemented.

  4. monitoring Mar 20, 2026, 04:43 PM UTC

    A fix has been implemented and we are monitoring the results.

  5. resolved Mar 20, 2026, 05:09 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 12, 2026

Errors processing Credit Card Payments through AMDPay

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
  1. 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.

  2. resolved Mar 12, 2026, 07:30 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 12, 2026

Degraded Claim Submission

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
  1. 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.

  2. investigating Mar 12, 2026, 02:14 AM UTC

    We are continuing to investigate this issue.

  3. 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 →

Minor March 10, 2026

Slowness in PM and EHR - Pool 133

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
  1. 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.

  2. investigating Mar 10, 2026, 05:01 PM UTC

    We are continuing to investigate this issue.

  3. investigating Mar 10, 2026, 06:03 PM UTC

    We are continuing to investigate this issue.

  4. monitoring Mar 10, 2026, 06:26 PM UTC

    A fix has been implemented and we are monitoring the results.

  5. monitoring Mar 10, 2026, 06:27 PM UTC

    We are continuing to monitor for any further issues.

  6. resolved Mar 10, 2026, 08:20 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 10, 2026

Fax Disruption of Service

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
  1. 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/.

  2. resolved Mar 10, 2026, 01:46 PM UTC

    This incident has been resolved.

Read the full incident report →

Major March 4, 2026

AdvancedMD Single Sign-On to Waystar Unavailable

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
  1. 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.

  2. resolved Mar 04, 2026, 11:29 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 24, 2026

Fax Service Provider- Updox System Slowdown

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
  1. 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.

  2. monitoring Feb 24, 2026, 07:22 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Feb 24, 2026, 07:41 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice February 18, 2026

Clients Unable To Login to EHR

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
  1. 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.

  2. resolved Feb 18, 2026, 07:51 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 18, 2026

Practice Management: Intermittent Pop‑Up Message on Login: “Please Close the Window and Re‑Log In”

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
  1. 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.

  2. identified Feb 18, 2026, 07:17 PM UTC

    We are continuing to work on a fix for this issue.

  3. monitoring Feb 18, 2026, 11:09 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Feb 19, 2026, 01:32 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 3, 2026

Updox Outage: Users are unable access AdvancedMD Fax

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
  1. 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/.

  2. resolved Feb 03, 2026, 02:03 AM UTC

    This incident has been resolved.

Read the full incident report →

Looking to track AdvancedMD downtime and outages?

Pingoru polls AdvancedMD's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when AdvancedMD reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track AdvancedMD alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring AdvancedMD for free

5 free monitors · No credit card required