RevolutionEHR incident

Investigating lag and errors when logging in

Critical Resolved View vendor source →

RevolutionEHR experienced a critical incident on April 17, 2025 affecting RevolutionEHR United States, lasting 5h 37m. The incident has been resolved; the full update timeline is below.

Started
Apr 17, 2025, 01:06 PM UTC
Resolved
Apr 17, 2025, 06:44 PM UTC
Duration
5h 37m
Detected by Pingoru
Apr 17, 2025, 01:06 PM UTC

Affected components

RevolutionEHR United States

Update timeline

  1. investigating Apr 17, 2025, 01:06 PM UTC

    We are currently investigating this issue.

  2. investigating Apr 17, 2025, 01:54 PM UTC

    Our engineers are continuing to troubleshoot this issue.

  3. investigating Apr 17, 2025, 03:09 PM UTC

    We are continuing to investigate this issue.

  4. identified Apr 17, 2025, 04:18 PM UTC

    As a response to last night's Amazon Web Service's Outage , our team shifted our hosting database in order to minimize the impact of the AWS issue. This database was operating as expected until an increase of user activity overwhelmed the new, temporary host. We are continuing to work to identify the cause

  5. monitoring Apr 17, 2025, 04:45 PM UTC

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

  6. monitoring Apr 17, 2025, 04:45 PM UTC

    We are continuing to monitor for any further issues.

  7. resolved Apr 17, 2025, 06:44 PM UTC

    This incident is resolved. We will provide more specific details in a post mortem posting to this incident before the end of the week