RevolutionEHR Outage History
RevolutionEHR is up right nowPingoru has recorded 70 incidents for RevolutionEHR: 55 in the last 12 months and 8 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 7 | 75 of 720 (10%) |
| May 2026 | 2 | 3 of 744 (0%) |
| June 2026 | 4 | 140 of 720 (20%) |
| July 2026 | 6 | 363 of 744 (49%) |
| August 2026 | 2 | 111 of 744 (15%) |
| September 2026 | 2 | 0 of 720 (0%) |
| October 2026 | 2 | 4 of 592 (1%) |
Incidents, newest first
Major October 23, 2025 RXNT Login Outage 19h 25m Integrated Partners
Started Oct 23, 2025, 06:45 PM UTC· resolved Oct 24, 2025, 02:11 PM UTC
- investigating Oct 23, 2025, 06:45 PM UTC
We’ve been notified by RXNT of a system-wide outage affecting RXNT logins. As of 1:05 PM ET, RXNT reports that users may be unable to sign in and access RXNT services. RXNT has classified this as a Priority 1 incident, and their engineering team is working around the clock to resolve it. What we know: Start time: 1:05 PM ET Impact: Login/access to RXNT is currently unavailable for all clients We will relay any new information from RXNT to you as soon as it’s available. No action is required on your end at this time. If you have downtime procedures related to RXNT-dependent workflows, you may wish to follow them until service is restored.
- investigating Oct 23, 2025, 06:46 PM UTC
We are continuing to investigate this issue.
- monitoring Oct 23, 2025, 08:10 PM UTC
RXNT has provided an update regarding the login issues. Stating at this time, you should be able to log in to RXNT successfully. They traced the issue back to their third-party login service. To restore access and prevent any further delays in this outage, they reverted to their legacy login page. If you encounter an “invalid password” error, please select "Forgot Password" to reset your RXNT password and successfully login. Please note that RXNT system performance may be slower than usual as their services fully recover.
- monitoring Oct 23, 2025, 08:47 PM UTC
We are continuing to monitor for any further issues.
- resolved Oct 24, 2025, 02:11 PM UTC
This incident has been resolved.
Notice October 20, 2025 Intermittent issues impacting RevolutionEHR phone lines for all departments 23h 37m RevolutionEHR United States, RevolutionEHR Canada
Started Oct 20, 2025, 04:34 PM UTC· resolved Oct 21, 2025, 04:11 PM UTC
- identified Oct 20, 2025, 04:34 PM UTC
We are currently experiencing intermittent phone issues due to a known AWS outage impacting multiple major services. At times, our phones may connect normally, while other times you may have difficulty reaching us. AWS is actively working to resolve the issue.
- monitoring Oct 20, 2025, 09:55 PM UTC
Reports from AWS indicate that services are gradually recovering. Our phone system appears to be operating normally at this time, and we will continue to monitor throughout the evening and into tomorrow morning to ensure the issue has been fully resolved.
- resolved Oct 21, 2025, 04:11 PM UTC
This incident has been resolved.
Major October 11, 2025 Currency exchange: Incident – Currency exchange
Started Oct 11, 2025, 09:46 PM UTC· resolved Oct 11, 2025, 09:46 PM UTC
- resolved Oct 11, 2025, 09:46 PM UTC
Type: Incident · Affected: AT, BE, BG, HR, CY, CZ, DK, EE, FI, FR (+27 more)
Notice September 3, 2025 Errors Reported When Accessing Multiple RevolutionEHR Accounts 22h 23m RevolutionEHR United States
Started Sep 03, 2025, 07:04 PM UTC· resolved Sep 04, 2025, 05:28 PM UTC
- identified Sep 03, 2025, 07:04 PM UTC
We have identified an issue affecting billers and other users with access to multiple RevolutionEHR accounts, where functionality challenges arise when switching between accounts. Our engineering team has developed a solution, and we are scheduled to deploy a fix tonight at 9:00 PM PST. This update will not cause any system downtime; however, active users will be logged out and prompted to log in again. To avoid issues until the fix is implemented, we recommend that users switching between RevolutionEHR accounts log out of RevolutionEHR, close their browser, reopen the browser, and then navigate to revolutionehr.com. Thank you for your patience and understanding. If you have any questions, please contact our support team.
- resolved Sep 04, 2025, 05:28 PM UTC
This incident has been resolved.
Notice August 27, 2025 Printing and upload Error – Troubleshooting Steps 1d RevolutionEHR United States, RevolutionEHR Canada
Started Aug 27, 2025, 01:59 PM UTC· resolved Aug 28, 2025, 02:17 PM UTC
- investigating Aug 27, 2025, 01:59 PM UTC
We are currently receiving reports that some offices are experiencing errors when attempting to print or uploading files. If you're encountering this issue, please follow the steps below: Ensure your web browser is up to date. Clear your browser cache. Allow pop-ups for Revolution in your browser settings. These steps often resolve the issue. If the problem persists after trying the above, please reach out to our support team for further assistance. Thank you for your patience!
- resolved Aug 28, 2025, 02:17 PM UTC
This incident has been resolved.
Minor July 25, 2025 Error Uploading Images Using RevIntegrator for Imaging 3d 22h RevolutionEHR United States, RevolutionEHR Canada
Started Jul 25, 2025, 03:09 PM UTC· resolved Jul 29, 2025, 01:10 PM UTC
- investigating Jul 25, 2025, 03:09 PM UTC
Users have reported they are unable to upload images using RevIntegrator for Imaging.
- identified Jul 25, 2025, 07:18 PM UTC
Our engineers have identified the issue and working on a resolution. The fix will require a patch to be release, we anticipate this to happen early next week but will provide a more specific date when it is available
- identified Jul 28, 2025, 09:13 PM UTC
A patch will be released at 9 pm Central tonight to resolve this issue
- resolved Jul 29, 2025, 01:10 PM UTC
This incident has been resolved.
Notice June 23, 2025 Order Submission Error – VisionWeb 1d RevolutionEHR United States
Started Jun 23, 2025, 02:12 PM UTC· resolved Jun 24, 2025, 03:07 PM UTC
- investigating Jun 23, 2025, 02:12 PM UTC
VisionWeb is currently investigating an issue that is preventing orders from being submitted. Users may encounter the following error message: "404 - File or directory not found. The resource you are looking for might have been removed, had its name changed, or is temporarily unavailable." VisionWeb is actively working to identify and resolve the issue. We will provide updates as soon as more information becomes available.
- resolved Jun 24, 2025, 03:07 PM UTC
This incident has been resolved.
Major June 11, 2025 RXNT ISSUES REPORTED THIS MORNING 10m Integrated Partners
Started Jun 11, 2025, 01:48 PM UTC· resolved Jun 11, 2025, 01:59 PM UTC
- investigating Jun 11, 2025, 01:48 PM UTC
RXNT reported an issue regarding slowness with the software within the integration. They are investigating the issue and we will provide additional updates as they become available.
- resolved Jun 11, 2025, 01:59 PM UTC
RXNT notified us that this issue should now be resolved.
Minor June 10, 2025 Reporting Delay 16m RevolutionEHR United States
Started Jun 10, 2025, 07:33 PM UTC· resolved Jun 10, 2025, 07:50 PM UTC
- investigating Jun 10, 2025, 07:33 PM UTC
There is currently a delay of approximately 10 minutes as it relates to reports also when adding inventory. Any new data entered can take up to 10 minutes to appear in an associated reports. For example, when receiving a payment or adding a new inventory item it may take up to 10 minutes appear.
- resolved Jun 10, 2025, 07:50 PM UTC
This incident has been resolved.
Minor May 20, 2025 Unable to access the PHR 25m RevolutionEHR United States
Started May 20, 2025, 09:34 PM UTC· resolved May 20, 2025, 10:00 PM UTC
- investigating May 20, 2025, 09:34 PM UTC
We are currently investigating this issue.
- monitoring May 20, 2025, 09:41 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved May 20, 2025, 10:00 PM UTC
This incident has been resolved.
Critical April 17, 2025 Investigating lag and errors when logging in 5h 37m RevolutionEHR United States
Started Apr 17, 2025, 01:06 PM UTC· resolved Apr 17, 2025, 06:44 PM UTC
- investigating Apr 17, 2025, 01:06 PM UTC
We are currently investigating this issue.
- investigating Apr 17, 2025, 01:54 PM UTC
Our engineers are continuing to troubleshoot this issue.
- investigating Apr 17, 2025, 03:09 PM UTC
We are continuing to investigate this issue.
- 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
- monitoring Apr 17, 2025, 04:45 PM UTC
A fix has been implemented and we are monitoring the results.
- monitoring Apr 17, 2025, 04:45 PM UTC
We are continuing to monitor for any further issues.
- 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
Critical April 16, 2025 Unable to access RevolutionEHR 1h 51m RevolutionEHR United States
Started Apr 16, 2025, 11:30 PM UTC· resolved Apr 17, 2025, 01:22 AM UTC
- 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.