Resolved after 1 hour 51 minutes, affecting RevolutionEHR United States, on April 16, 2025.
The failover has been completed and access to RevolutionEHR is restored. We will provide more information when we receive details from AWS. At this time there is still no ETA from AWS on the resolution of their issue but the failover allows RevolutionEHR to run on servers that are not impacted.
Affected components
Update timeline
- investigating Apr 16, 2025, 11:30 PM UTC
We are currently investigating this issue.
- investigating Apr 17, 2025, 12:17 AM UTC
We are currently seeing an AWS degradation of service in the us-2-east region which appears to be causing the current issue. We are working to confirm this and obtain additional information
- identified Apr 17, 2025, 12:38 AM UTC
We do not have any ETA from AWS on a possible resolution. In the interim we are working to perform a failover to promote a replica as the new primary database which will allow us to operate on an AWS server that is not currently experiencing degradation. This process can take 1 to 2 hours, but we will continue with this in the event that the AWS issue is not resolved soon.
- monitoring Apr 17, 2025, 01:02 AM UTC
The failover has been completed and access to RevolutionEHR is restored. We will provide more information when we receive details from AWS. At this time there is still no ETA from AWS on the resolution of their issue but the failover allows RevolutionEHR to run on servers that are not impacted.
- resolved Apr 17, 2025, 01:22 AM UTC
This incident has been resolved.
Your product runs on more than RevolutionEHR
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services