DrFirst Outage History

DrFirst is up right now

DrFirst had 45 outages in the last 2 years totaling 805h 40m of downtime — averaging 1.8 incidents per month.

There were 45 DrFirst outages since June 23, 2025 totaling 805h 40m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.drfirst.com

Minor June 12, 2026

Issue affecting user login via LDAP within Backline

Detected by Pingoru
Jun 12, 2026, 12:49 AM UTC
Resolved
Jun 12, 2026, 01:58 AM UTC
Duration
1h 9m
Affected: Backline
Timeline · 2 updates
  1. investigating Jun 12, 2026, 12:49 AM UTC

    We are currently investigating a technical issue affecting user login via LDAP within Backline. Our engineering team has been engaged and is actively working to identify and resolve the root cause as quickly as possible.

  2. resolved Jun 12, 2026, 01:58 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 11, 2026

iPrescribe Help Center Live Chat Unavailable

Detected by Pingoru
Jun 11, 2026, 05:24 PM UTC
Resolved
Jun 11, 2026, 05:43 PM UTC
Duration
18m
Affected: iPrescribe Live Messaging/Chat
Timeline · 2 updates
  1. investigating Jun 11, 2026, 05:24 PM UTC

    We are currently investigating an issue affecting the live messaging/chat feature within the iPrescribe Help Center. The issue has been traced to a third-party service provider, and we are actively engaged with them to restore functionality. Support ticket submission is not impacted — users can continue to submit support requests as normal, and our team will respond as quickly as possible. We will provide an update as more information becomes available.

  2. resolved Jun 11, 2026, 05:43 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 8, 2026

Real Time Prescription Benefit — Intermittent Connectivity Issues

Detected by Pingoru
Jun 08, 2026, 10:31 PM UTC
Resolved
Jun 09, 2026, 06:52 PM UTC
Duration
20h 21m
Affected: Price Transparency (mBC)
Timeline · 2 updates
  1. investigating Jun 08, 2026, 10:31 PM UTC

    We are aware of intermittent connectivity issues affecting real-time benefit checks originating with a third-party data provider. DrFirst systems are operating normally, and we are actively monitoring the situation. In a small number of cases, partners may experience delayed or failed real-time benefit responses during this time. We will provide updates as more information becomes available.

  2. resolved Jun 09, 2026, 06:52 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 5, 2026

Identity Proofing (IDP) Issue

Detected by Pingoru
Jun 05, 2026, 12:47 AM UTC
Resolved
Jun 05, 2026, 02:29 PM UTC
Duration
13h 42m
Affected: EPCS IDP (Experian/ID.me)
Timeline · 4 updates
  1. investigating Jun 05, 2026, 12:47 AM UTC

    We are currently investigating reports of providers experiencing errors when attempting to complete Identity Proofing (IDP). This appears to be related to a third-party identity verification vendor. We will provide updates as our investigation progresses.

  2. investigating Jun 05, 2026, 01:57 AM UTC

    We are continuing to investigate this issue.

  3. monitoring Jun 05, 2026, 01:36 PM UTC

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

  4. resolved Jun 05, 2026, 02:29 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical May 27, 2026

Intermittent Login Issues with E-Prescribing Desktop (Rcopia)

Detected by Pingoru
May 27, 2026, 12:13 AM UTC
Resolved
May 27, 2026, 02:37 AM UTC
Duration
2h 24m
Affected: E-Prescribing Desktop Region 1 (Rcopia)E-Prescribing Desktop Region 2 (Rcopia)E-Prescribing Desktop Region 3 (Rcopia)Electronic Prescribing for Controlled Substances (EPCS)E-Prescribing Desktop Region 4 (Rcopia)E-Prescribing Mobile (iPrescribe)E-Prescribing Desktop Region 5 (Rcopia)Prescription Routing (Gadget)DrFirst Universal Login (IDaaS)Eligibility - Pharmacy Benefits
Timeline · 10 updates

Read the full incident report →

Minor May 26, 2026

PDMP Third-Party Incident

Detected by Pingoru
May 26, 2026, 03:44 PM UTC
Resolved
May 26, 2026, 03:57 PM UTC
Duration
13m
Affected: PDMP
Timeline · 4 updates
  1. investigating May 26, 2026, 03:44 PM UTC

    Customers may experience issues accessing Patient Searches via PDMP reports. We are working with our partner and will keep this page updated.

  2. identified May 26, 2026, 03:48 PM UTC

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

  3. monitoring May 26, 2026, 03:49 PM UTC

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

  4. resolved May 26, 2026, 03:57 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 26, 2026

Prescription Processing & Medication History Delays

Detected by Pingoru
May 26, 2026, 02:39 PM UTC
Resolved
May 26, 2026, 08:50 PM UTC
Duration
6h 10m
Affected: E-Prescribing Desktop Region 1 (Rcopia)E-Prescribing Desktop Region 2 (Rcopia)E-Prescribing Desktop Region 3 (Rcopia)E-Prescribing Desktop Region 4 (Rcopia)E-Prescribing Desktop Region 5 (Rcopia)Medication History (MedHx)Prescription Routing (Gadget)
Timeline · 8 updates
  1. investigating May 26, 2026, 02:39 PM UTC

    We are monitoring the system and see a build up on processing prescriptions. We are engaged and the team is taking steps to mitigate further delay. We will provide an updates as soon as more information is available.

  2. identified May 26, 2026, 02:44 PM UTC

    We are monitoring the system and see a build up on processing prescriptions. We are engaged and the team is taking steps to mitigate further delay. We will provide an updates as soon as more information is available.

  3. identified May 26, 2026, 03:16 PM UTC

    We are monitoring the system and see a build up on processing prescriptions. We are engaged and the team is taking steps to mitigate further delay. We will provide an updates as soon as more information is available.

  4. identified May 26, 2026, 03:37 PM UTC

    We are aware that eligibility, medication history and prescription processing are both experiencing delays. Our team is actively engaged and taking steps to mitigate further impact. We will provide updates as more information becomes available.

  5. identified May 26, 2026, 03:40 PM UTC

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

  6. identified May 26, 2026, 04:07 PM UTC

    We are aware that eligibility, medication history and prescription processing are both experiencing delays. Our team is actively engaged and taking steps to mitigate further impact. We will provide updates as more information becomes available.

  7. monitoring May 26, 2026, 05:03 PM UTC

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

  8. resolved May 26, 2026, 08:50 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 21, 2026

iPrescribe Provider Login Issues Impacting a Subset of Android Users

Detected by Pingoru
May 21, 2026, 02:44 PM UTC
Resolved
May 22, 2026, 11:35 AM UTC
Duration
20h 50m
Affected: E-Prescribing Mobile (iPrescribe)
Timeline · 2 updates
  1. monitoring May 21, 2026, 02:44 PM UTC

    We have identified the cause of the login failures affecting a subset of iPrescribe providers who are on Android devices. The issue is caused by a trailing space being appended to the username during username reset. This behavior appears to be isolated to Android devices and is suspected to be linked to a recent Android OS update that is auto-filling or appending a space to the username field. Backend services and recent platform deployments have been ruled out as contributing factors and iOS users are not broadly impacted. As an immediate workaround, affected users can resolve the issue by ensuring there is no trailing space in the username field when resetting or logging in. Our team continues to investigate the root cause and is coordinating on a permanent fix. Further updates will be provided as progress is made.

  2. resolved May 22, 2026, 11:35 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 19, 2026

PDMP Third-Party Incident for Washington

Detected by Pingoru
May 19, 2026, 05:34 PM UTC
Resolved
May 19, 2026, 05:52 PM UTC
Duration
18m
Affected: PDMP
Timeline · 2 updates
  1. investigating May 19, 2026, 05:34 PM UTC

    Customers may experience issues accessing Patient Searches via PDMP reports for the state Washington. We are working with our partner and will keep this page updated.

  2. resolved May 19, 2026, 05:52 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 13, 2026

Intermittent Performance Issues with E-Prescribing Desktop (Rcopia)

Detected by Pingoru
May 13, 2026, 04:52 PM UTC
Resolved
May 13, 2026, 06:06 PM UTC
Duration
1h 14m
Affected: E-Prescribing Desktop Region 1 (Rcopia)E-Prescribing Desktop Region 2 (Rcopia)E-Prescribing Desktop Region 3 (Rcopia)E-Prescribing Desktop Region 4 (Rcopia)E-Prescribing Desktop Region 5 (Rcopia)
Timeline · 3 updates
  1. investigating May 13, 2026, 04:52 PM UTC

    Some customers may experience intermittent performance issues with E-Prescribing Desktop (Rcopia) at this time. Our engineers are aware and working to resolve this as soon as possible.

  2. monitoring May 13, 2026, 05:16 PM UTC

    We are currently monitoring following a brief window of elevated session authentication errors that affected access to the application. Service has stabilized and access has been restored. Our team is continuing to investigate the root cause and determine next steps. We will provide another update as more information becomes available.

  3. resolved May 13, 2026, 06:06 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 12, 2026

Elevated Script Failure Rates - Third-Party Network Delay

Detected by Pingoru
May 12, 2026, 08:36 PM UTC
Resolved
May 13, 2026, 12:19 AM UTC
Duration
3h 42m
Affected: Pharmacy Network - Prescribing
Timeline · 3 updates
  1. investigating May 12, 2026, 08:36 PM UTC

    We are currently experiencing elevated prescription script failure rates affecting script processing through the third-party network. A buildup of pending scripts is occurring due to scripts are not returning as verified in a timely manner. Please note: scripts that remain in a pending state beyond 120 minutes will be marked as failed in the client system. This is a system timeout behavior and does not necessarily reflect an actual rejection by the pharmacy. We are actively working with our third-party network partner to address the delay and reduce the backlog of pending scripts. Further updates will be provided as more information becomes available.

  2. identified May 12, 2026, 08:54 PM UTC

    Identified - The third-party network has identified the source of the delay and is actively working on a resolution. We will provide another update once we are informed the fix is in place. As a reminder, scripts that remain pending beyond 120 minutes will be marked as failed in the client system due to system timeout behavior. This does not necessarily reflect an actual rejection by the pharmacy.

  3. resolved May 13, 2026, 12:19 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 8, 2026

Intermittent Performance Issues with E-Prescribing Desktop Staging Environment (Rcopia Staging Environment)

Detected by Pingoru
May 08, 2026, 06:58 PM UTC
Resolved
May 08, 2026, 07:24 PM UTC
Duration
26m
Affected: E-Prescribing Desktop Staging Environment (Rcopia Staging Environment)
Timeline · 2 updates
  1. investigating May 08, 2026, 06:58 PM UTC

    Some customers may experience intermittent performance issues with E-Prescribing Desktop Staging Environment (Rcopia Staging Environment) at this time. Our engineers are aware and working to resolve this as soon as possible.

  2. resolved May 08, 2026, 07:24 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 8, 2026

Degraded Performance – US Live Messaging / Chat

Detected by Pingoru
May 08, 2026, 01:55 AM UTC
Resolved
May 08, 2026, 06:32 PM UTC
Duration
16h 36m
Affected: DrFirst US Live Messaging/Chat
Timeline · 3 updates
  1. investigating May 08, 2026, 01:55 AM UTC

    We are currently aware of an ongoing issue affecting DrFirst US Live Messaging and Chat functionality. The disruption is caused by an outage impacting an external third-party platform that supports these services. Our team is actively monitoring the situation. We appreciate your patience as we work to restore full service.

  2. monitoring May 08, 2026, 09:20 AM UTC

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

  3. resolved May 08, 2026, 06:32 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 6, 2026

CA CURES Connectivity Issue — PDMP Transactions Impacted

Detected by Pingoru
May 06, 2026, 10:43 PM UTC
Resolved
May 07, 2026, 12:42 AM UTC
Duration
1h 58m
Affected: PDMP
Timeline · 2 updates
  1. investigating May 06, 2026, 10:43 PM UTC

    We are currently investigating an issue affecting PDMP transactions in California. CA CURES appears to be unavailable, which is preventing PDMP checks from completing for California providers. Our team is actively investigating the root cause, including potential connectivity and traffic routing factors. We will provide an update as additional information becomes available.

  2. resolved May 07, 2026, 12:42 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 5, 2026

Intermittent Performance Issues - EPCS IDP (Experian/ID.me)

Detected by Pingoru
May 05, 2026, 02:18 PM UTC
Resolved
May 05, 2026, 05:55 PM UTC
Duration
3h 36m
Affected: EPCS IDP (Experian/ID.me)Electronic Prescribing for Controlled Substances (EPCS)
Timeline · 6 updates
  1. investigating May 05, 2026, 04:37 PM UTC

    Some customers may experience intermittent performance issues while sending prescription at this time. Our engineers are aware and working with third party vendor to resolve this as soon as possible.

  2. investigating May 05, 2026, 04:40 PM UTC

    We are continuing to investigate this issue.

  3. investigating May 05, 2026, 04:43 PM UTC

    We are continuing to investigate this issue.

  4. investigating May 05, 2026, 04:48 PM UTC

    IDP is currently experiencing an issue, which may affect your ability to authenticate or access services through the IDP. We are working with our 3rd Party vendor to resolve this as quickly as possible

  5. monitoring May 05, 2026, 04:59 PM UTC

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

  6. resolved May 05, 2026, 05:55 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 4, 2026

Third-Party Connectivity Issue – ePrescribing Impacted

Detected by Pingoru
May 04, 2026, 08:20 PM UTC
Resolved
May 05, 2026, 02:28 PM UTC
Duration
18h 7m
Affected: Pharmacy Network - Prescribing
Timeline · 6 updates
  1. investigating May 04, 2026, 08:20 PM UTC

    Some customers may be experiencing intermittent issues with Pharmacy Network - Prescribing. This is related to a third-party connectivity issue currently under investigation. We will provide updates as more information becomes available.

  2. investigating May 04, 2026, 09:17 PM UTC

    We are continuing to investigate this issue.

  3. investigating May 04, 2026, 09:55 PM UTC

    We are continuing to investigate this issue.

  4. investigating May 04, 2026, 10:36 PM UTC

    We are continuing to investigate this issue.

  5. monitoring May 04, 2026, 11:17 PM UTC

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

  6. resolved May 05, 2026, 02:28 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 1, 2026

Retail & Portal Practice User Login Disruption

Detected by Pingoru
May 01, 2026, 01:48 PM UTC
Resolved
May 01, 2026, 04:04 PM UTC
Duration
2h 16m
Affected: E-Prescribing Desktop Region 1 (Rcopia)E-Prescribing Desktop Region 2 (Rcopia)E-Prescribing Desktop Region 3 (Rcopia)E-Prescribing Desktop Region 4 (Rcopia)E-Prescribing Mobile (iPrescribe)E-Prescribing Desktop Region 5 (Rcopia)
Timeline · 8 updates
  1. investigating May 01, 2026, 01:48 PM UTC

    We are currently investigating an issue affecting login access for retail practice users. Users attempting to log in are encountering an error at the final step of authentication and are unable to access the application. Our team has identified a potential cause and is actively working toward resolution. Further updates will follow.

  2. investigating May 01, 2026, 02:03 PM UTC

    We are continuing to investigate this issue.

  3. identified May 01, 2026, 02:19 PM UTC

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

  4. identified May 01, 2026, 02:51 PM UTC

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

  5. identified May 01, 2026, 03:37 PM UTC

    We are currently investigating an issue affecting login access for retail & portal practice users. Users attempting to log in are encountering an error at the final step of authentication and are unable to access the application. Our team has identified a potential cause and is actively working toward resolution. Further updates will follow.

  6. identified May 01, 2026, 03:53 PM UTC

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

  7. monitoring May 01, 2026, 03:57 PM UTC

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

  8. resolved May 01, 2026, 04:04 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 27, 2026

Intermittent Performance Issues with Prescription Routing (Gadget)

Detected by Pingoru
Apr 27, 2026, 06:48 PM UTC
Resolved
Apr 27, 2026, 09:27 PM UTC
Duration
2h 39m
Affected: Prescription Routing (Gadget)
Timeline · 6 updates
  1. investigating Apr 27, 2026, 06:48 PM UTC

    Some customers may experience intermittent performance issues with Prescription Routing (Gadget) at this time. Our engineers are aware and working to resolve this as soon as possible.

  2. investigating Apr 27, 2026, 07:13 PM UTC

    We are continuing to investigate this issue.

  3. investigating Apr 27, 2026, 07:32 PM UTC

    We are continuing to investigate this issue.

  4. investigating Apr 27, 2026, 08:16 PM UTC

    We are continuing to investigate this issue.

  5. monitoring Apr 27, 2026, 08:44 PM UTC

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

  6. resolved Apr 27, 2026, 09:27 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 17, 2026

Intermittent Performance Issues with E-Prescribing Desktop (Rcopia Update Region 1,2,3 )

Detected by Pingoru
Apr 17, 2026, 01:46 AM UTC
Resolved
Apr 17, 2026, 03:18 AM UTC
Duration
1h 32m
Affected: E-Prescribing Desktop Region 1 (Rcopia)E-Prescribing Desktop Region 2 (Rcopia)E-Prescribing Desktop Region 3 (Rcopia)
Timeline · 4 updates
  1. investigating Apr 17, 2026, 01:46 AM UTC

    Some customers may experience intermittent performance issues with E-Prescribing Desktop (Rcopia Update) at this time. Our engineers are aware and working to resolve this as soon as possible.

  2. investigating Apr 17, 2026, 01:47 AM UTC

    We are continuing to investigate this issue.

  3. investigating Apr 17, 2026, 02:11 AM UTC

    We are continuing to investigate this issue.

  4. resolved Apr 17, 2026, 03:18 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 13, 2026

Prescription Processing Delays — Third Party Vendor Performance Degradation

Detected by Pingoru
Apr 13, 2026, 08:16 PM UTC
Resolved
Apr 13, 2026, 09:16 PM UTC
Duration
59m
Affected: Prescription Routing (Gadget)
Timeline · 3 updates
  1. investigating Apr 13, 2026, 08:16 PM UTC

    We are currently investigating reports of prescription processing delays impacting some users. We are working with a third party pharmacy vendor to coordinate a resolution. We will provide an update as soon as more information is available.

  2. investigating Apr 13, 2026, 09:01 PM UTC

    We are continuing to investigate this issue.

  3. resolved Apr 13, 2026, 09:16 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 27, 2026

Issue retrieving and responding to pharmacy messages with E-Prescribing Desktop (Rcopia)

Detected by Pingoru
Mar 27, 2026, 02:47 PM UTC
Resolved
Mar 27, 2026, 02:56 PM UTC
Duration
9m
Affected: E-Prescribing Desktop Region 1 (Rcopia)E-Prescribing Desktop Region 2 (Rcopia)E-Prescribing Desktop Region 3 (Rcopia)E-Prescribing Desktop Region 4 (Rcopia)E-Prescribing Desktop Region 5 (Rcopia)
Timeline · 4 updates
  1. investigating Mar 27, 2026, 02:47 PM UTC

    Some customers may experience issues retrieving and responding to pharmacy messages. Our engineers are aware and working to resolve this as soon as possible.

  2. identified Mar 27, 2026, 02:50 PM UTC

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

  3. identified Mar 27, 2026, 02:54 PM UTC

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

  4. resolved Mar 27, 2026, 02:56 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 19, 2026

3rd Party Pharmacy Network - Prescribing Issue

Detected by Pingoru
Mar 19, 2026, 09:20 PM UTC
Resolved
Mar 27, 2026, 11:15 AM UTC
Duration
7d 13h
Affected: Pharmacy Network - Prescribing
Timeline · 8 updates
  1. investigating Mar 19, 2026, 09:20 PM UTC

    We are currently investigating an issue in which a small percentage of electronic prescriptions are not receiving verification responses from a third-party vendor. Prescriptions are continuing to be sent successfully, and our fallback protocol is active - ensuring pharmacies receive prescriptions within our standard fax window. We are working with the vendor to identify the root cause. We will provide updates as more information becomes available.

  2. investigating Mar 20, 2026, 02:08 PM UTC

    We are continuing to investigate this issue.

  3. identified Mar 20, 2026, 07:54 PM UTC

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

  4. identified Mar 23, 2026, 12:29 PM UTC

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

  5. identified Mar 24, 2026, 11:24 PM UTC

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

  6. identified Mar 25, 2026, 12:41 PM UTC

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

  7. identified Mar 26, 2026, 12:49 PM UTC

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

  8. resolved Mar 27, 2026, 11:15 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 23, 2026

Intermittent Performance Issues - Electronic Prior Authorization (Myndshft)

Detected by Pingoru
Feb 23, 2026, 05:09 PM UTC
Resolved
Feb 23, 2026, 07:46 PM UTC
Duration
2h 37m
Affected: Medical - Patient Financial Responsibility(PFR)Medical - Prior Auth Requirements(PAR)Medical - Prior Auth Submission(PAS)Pharmacy - Realtime Pharmacy Benefits(RTPB)
Timeline · 4 updates
  1. investigating Feb 23, 2026, 05:09 PM UTC

    DrFirst is aware of an issue affecting Electronic Prior Authorization (Myndshft) that may cause intermittent performance degradation for some customers. Our engineering team is actively investigating and working toward a resolution.

  2. identified Feb 23, 2026, 05:42 PM UTC

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

  3. identified Feb 23, 2026, 06:18 PM UTC

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

  4. resolved Feb 23, 2026, 07:46 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 9, 2026

Intermittent Performance Issues with E-Prescribing Desktop Staging Environment (Rcopia Staging Environment) & E-Prescribing Mobile (iPrescribe)

Detected by Pingoru
Feb 09, 2026, 05:38 PM UTC
Resolved
Feb 09, 2026, 05:42 PM UTC
Duration
3m
Affected: E-Prescribing Mobile (iPrescribe)E-Prescribing Desktop Staging Environment (Rcopia Staging Environment)
Timeline · 2 updates
  1. investigating Feb 09, 2026, 05:38 PM UTC

    We are currently experiencing an issue with the E-Prescription Desktop Staging Environment (Rcopia Staging Environment). Users are unable to launch the application at this time. Our engineers are aware and working to resolve this as soon as possible.

  2. resolved Feb 09, 2026, 05:42 PM UTC

    This incident has been resolved.

Read the full incident report →