All Systems Operational

Uptime over the past 90 days. View historical uptime.
RevolutionEHR United States Operational
90 days ago
99.6 % uptime
Today
RevolutionEHR Canada Operational
90 days ago
100.0 % uptime
Today
Internet Status ? Operational
Integrated Partners ? Operational
90 days ago
100.0 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

Apr 26, 2025

No incidents reported today.

Apr 25, 2025

No incidents reported.

Apr 24, 2025

No incidents reported.

Apr 23, 2025

No incidents reported.

Apr 22, 2025

No incidents reported.

Apr 21, 2025

No incidents reported.

Apr 20, 2025

No incidents reported.

Apr 19, 2025

No incidents reported.

Apr 18, 2025

No incidents reported.

Apr 17, 2025
Investigating lag and errors when logging in
Resolved - This incident is resolved. We will provide more specific details in a post mortem posting to this incident before the end of the week
Apr 17, 13:44 CDT
Update - We are continuing to monitor for any further issues.
Apr 17, 11:45 CDT
Monitoring - A fix has been implemented and we are monitoring the results.
Apr 17, 11:45 CDT
Identified - 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
Apr 17, 11:18 CDT
Update - We are continuing to investigate this issue.
Apr 17, 10:09 CDT
Update - Our engineers are continuing to troubleshoot this issue.
Apr 17, 08:54 CDT
Investigating - We are currently investigating this issue.
Apr 17, 08:06 CDT
Apr 16, 2025
Unable to access RevolutionEHR
Resolved - This incident has been resolved.
Apr 16, 20:22 CDT
Monitoring - 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.
Apr 16, 20:02 CDT
Identified - 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.
Apr 16, 19:38 CDT
Update - 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
Apr 16, 19:17 CDT
Investigating - We are currently investigating this issue.
Apr 16, 18:30 CDT
Apr 15, 2025

No incidents reported.

Apr 14, 2025
Issues logging into RevolutionEHR
Resolved - This incident has been resolved.
Apr 14, 10:52 CDT
Monitoring - A fix has been implemented and we are monitoring the results.
Apr 14, 09:50 CDT
Identified - The issue has been identified and log ins are being restored. Some users are already able to log in, but if you are not able to log in yet, please wait a few minutes and try again
Apr 14, 09:39 CDT
Investigating - We are currently investigating this issue.
Apr 14, 09:26 CDT
Apr 13, 2025

No incidents reported.

Apr 12, 2025

No incidents reported.

← Incident History Powered by Atlassian Statuspage