Clinic Aid 403 Error During Claim Submission
Monitoring - We are aware of an issue affecting some offices when submitting claims to ClinicAid. Impacted users may receive a 403 error during claim submission.

ClinicAid has advised that recent security updates on their end are causing this error for some users. Their development team is actively investigating the issue and working toward a resolution.

We will continue to monitor the situation and share additional updates as they become available from ClinicAid.
Jul 08, 2026 - 09:37 CDT
Uptime over the past 90 days. View historical uptime.
RevolutionEHR United States Operational
90 days ago
100.0 % uptime
Today
RevolutionEHR Canada Degraded Performance
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.

Jul 8, 2026

Unresolved incident: Clinic Aid 403 Error During Claim Submission.

Jul 7, 2026

No incidents reported.

Jul 6, 2026

No incidents reported.

Jul 5, 2026

No incidents reported.

Jul 4, 2026

No incidents reported.

Jul 3, 2026

No incidents reported.

Jul 2, 2026

No incidents reported.

Jul 1, 2026
Error on VisionWeb orders
Resolved - This was related to an issue on the VisionWeb side. VisionWeb was able to quickly identify and resolve the problem.
Jul 1, 08:54 CDT
Investigating - We are aware of an issue occurring when accessing or creating a new Order when the processor is set to VisionWeb. Our engineers are actively investigating. We will post additional information as it becomes available. The error will prevent additional work in the software without out logging out/in. Currently we advise that you do not open or create any VisionWeb orders to prevent disruption to your RevolutionEHR access
Jul 1, 08:35 CDT
Jun 30, 2026
RevIntake Sync Issues
Resolved - This incident has been resolved.
Jun 30, 08:42 CDT
Investigating - We are aware of an issue impacting some RevIntake users. Affected offices may see patients not appearing in the RevIntake Dashboard and/or patients not receiving RevIntake messages as expected.

We are aware of the issue actively working on a resolution. We will continue to monitor progress and provide an update as soon as additional information is available or the issue has been resolved.
Jun 29, 10:47 CDT
Jun 29, 2026
Jun 28, 2026

No incidents reported.

Jun 27, 2026

No incidents reported.

Jun 26, 2026
RevIntake Sync Issues
Resolved - This incident has been resolved.
Jun 26, 08:53 CDT
Monitoring - The underlying issue impacting some RevIntake users has been identified, and corrective measures have been implemented. As part of the resolution, a system refresh of RevIntake was required. As a result, a processing backlog remains, which may continue to cause delays in patient syncing, registration link delivery, and reminder notifications for some offices. New appointments continue to be processed, and both teams are actively monitoring progress as the backlog is cleared. Backlog processing is expected to be completed by June 25, 2026, at which time normal operation is expected to resume.
Jun 24, 15:17 CDT
Investigating - We are currently investigating an issue impacting some RevIntake offices. Reports indicate that some patients are not syncing back to RevolutionEHR after completing registration, and some patients are not receiving their RevIntake registration links. We will provide updates as more information becomes available.
Jun 24, 09:56 CDT
System Maintenance Thursday, June 25th at 11:00 pm CDT
Completed - The scheduled maintenance has been completed.
Jun 26, 00:00 CDT
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 25, 23:00 CDT
Scheduled - We will be performing scheduled maintenance Thursday, June 25th at 11:00 PM CST. The system will be unavailable for 1 hour during this time. If you are logged in at 11:00 PM CST on
Thursday, you will receive an error message and may lose data currently being entered. It is very important that you log off prior to 11:00 PM CST Thursday.
Jun 24, 09:54 CDT
Jun 25, 2026
Jun 24, 2026
← Incident History Powered by Atlassian Statuspage