DrChrono incident

Third Party Vendor: ID.me

Minor Resolved View vendor source →

DrChrono experienced a minor incident on November 18, 2024 affecting drchrono.com and drchrono iPad EHR, lasting 20h 55m. The incident has been resolved; the full update timeline is below.

Started
Nov 18, 2024, 03:29 PM UTC
Resolved
Nov 19, 2024, 12:25 PM UTC
Duration
20h 55m
Detected by Pingoru
Nov 18, 2024, 03:29 PM UTC

Affected components

drchrono.comdrchrono iPad EHR

Update timeline

  1. identified Nov 18, 2024, 03:29 PM UTC

    ID.me, our third-party vendor, has identified an issue within their system and is actively working on deploying a fix. We will continue to provide updates as new information becomes available. Thank you for your patience and understanding. Please follow their status page for more information: https://status.id.me/

  2. identified Nov 18, 2024, 04:48 PM UTC

    ID.me, our third-party vendor, has identified an issue within their system and is actively working on deploying a fix. We will continue to provide updates as new information becomes available. Thank you for your patience and understanding. Please follow their status page for more information: https://status.id.me/

  3. identified Nov 18, 2024, 05:53 PM UTC

    ID.me, our third-party vendor, is continuing to work on a fix to address their ongoing platform degradation. We will continue to provide updates as new information becomes available. Thank you for your patience and understanding. Please follow their status page for more information: https://status.id.me/

  4. monitoring Nov 18, 2024, 07:10 PM UTC

    ID.me, our third-party vendor, has implemented a fix and is continuing to monitor their system. We will continue to provide updates as new information becomes available. Thank you for your patience and understanding. Please follow their status page for more information: https://status.id.me/

  5. monitoring Nov 19, 2024, 12:25 PM UTC

    ID.me, our third-party vendor, has resolved their incident. Thank you for your patience and understanding.

  6. resolved Nov 19, 2024, 12:25 PM UTC

    This incident has been resolved.