All Systems Operational

About This Site

During planned maintenance or downtime, system availability may deviate from normal, but message flow through Redox shouldn’t be impacted. In the rare case of disruption, most messages will queue and be delivered after downtime since we don’t manually pause queues during maintenance.

You shouldn’t need to do anything since a Redoxer is always on call during and after the maintenance window to make sure traffic flow is normal. But if needed, you can proactively monitor your queues after downtime.

Traffic Processing ? Operational
Logs (view/search) Operational
Alerting Operational
Dashboard Tools ? Operational
Platform API ? Operational
Developer Docs ? Operational
Hosting Operational
Hosting Operational
AWS ec2-us-west-2 Operational
AWS ec2-us-west-1 Operational
AWS ec2-us-east-1 Operational
Third Party Services Operational
Verato EMPI ? Operational
IMO Codeset Normalization ? Operational
ScienceIO ScienceIO API Operational
Clinical Networks Operational
RLS Operational
Carequality Operational
CommonWell Operational
DirectTrust Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance

Scheduled Maintenance

Monthly Maintenance - October 2025 Oct 18, 2025 02:30-04:30 CDT

We will be undergoing scheduled maintenance during this time.
Posted on Jan 10, 2025 - 09:26 CST

Monthly Maintenance - November 2025 Nov 15, 2025 02:30-04:30 CST

We will be undergoing scheduled maintenance during this time.
Posted on Jan 10, 2025 - 09:27 CST

Redox FHIR Sandbox Refresh Dec 1, 2025 08:00-16:00 CST

The Redox FHIR Sandbox will be refreshed to it's original state. Any unique data created by customers in the Sandbox environment over the past 6 months will be removed. Customers may continue to create unique data on seeded test patients once the refresh is completed.
Posted on Jun 17, 2024 - 08:37 CDT

Redox FHIR Sandbox Refresh Jun 1, 2026 08:00-16:00 CDT

The Redox FHIR Sandbox will be refreshed to it's original state. Any unique data created by customers in the Sandbox environment over the past 6 months will be removed. Customers may continue to create unique data on seeded test patients once the refresh is completed.
Posted on Jun 17, 2024 - 08:37 CDT

Redox FHIR Sandbox Refresh Dec 1, 2026 08:00-16:00 CST

The Redox FHIR Sandbox will be refreshed to it's original state. Any unique data created by customers in the Sandbox environment over the past 6 months will be removed. Customers may continue to create unique data on seeded test patients once the refresh is completed.
Posted on Jun 17, 2024 - 08:38 CDT
Oct 2, 2025

No incidents reported today.

Oct 1, 2025

No incidents reported.

Sep 30, 2025
Resolved - Logs should now be visible across the entire Redox platform. If you have any addition questions or are still experiencing issues, please reach out to support@redoxengine.com
Sep 30, 13:23 CDT
Monitoring - A fix has been implemented for the log visibility issues and most logs should now be visible. We are actively monitoring the situation and ensuring that all affected customers' logs are visible again. The previously mentioned processing delays have been resolved.

If you have questions or are still experiencing issues, please reach out to support@redoxengine.com

Sep 30, 13:01 CDT
Identified - We are currently aware of an issue in which the the last one hour of logs are not properly displaying on the dashboard. Some processing for synchronous traffic may also be delayed.

What this means: While asynchronous logs are still processing properly, the dashboard is not displaying them as expected. Search within the dashboard will not work as expected until a fix has been implemented. Additionally, synchronous logs may take longer to process than normal.

If you have questions about specific logs or your connection and whether it has been affected, please contact us at support@redoxengine.com

Sep 30, 11:54 CDT
Sep 29, 2025
Resolved - Redox was made aware of an incident in which Flat File SFTP messages were succeeding but not processing correctly. A fix has already been implemented and all traffic is now up to date and processed. If you have any additional questions please reach out to support@redoxengine.com
Sep 29, 19:30 CDT
Resolved - The incident has been resolved. If you have any additional questions please reach out to support@redoxengine.com
Sep 29, 15:35 CDT
Monitoring - A fix has been implemented for the processing delay and visibility issues and we are actively monitoring our logs. Processing and visibility should be back to normal. If you have questions please reach out to support@redoxengine.com
Sep 29, 12:35 CDT
Identified - We have identified the cause for the log delays and are actively working on a fix. Traffic processing latency is mostly caught up, but visibility may still be delayed. We will continue to update as we have more information.
Sep 29, 11:40 CDT
Update - Please note that log visibility may also be delayed. We are continuing to investigate this issue.
Sep 29, 11:17 CDT
Investigating - At approximately 10:39am CT, Redox became aware of an issue in which logs are delayed.

What this means: you may experience a delay before receiving traffic from Redox. However, please be aware that the actual processing of logs is unaffected; message flow is still occurring, albeit at a slower pace. We are actively looking into this issue and will have a fix available as soon as possible.

If you are concerned that your logs have been impacted or have any additional questions, please reach out to support@redoxengine.com

Sep 29, 11:11 CDT
Sep 28, 2025

No incidents reported.

Sep 27, 2025

No incidents reported.

Sep 26, 2025

No incidents reported.

Sep 25, 2025

No incidents reported.

Sep 24, 2025

No incidents reported.

Sep 23, 2025

No incidents reported.

Sep 22, 2025

No incidents reported.

Sep 21, 2025

No incidents reported.

Sep 20, 2025

No incidents reported.

Sep 19, 2025

No incidents reported.

Sep 18, 2025

No incidents reported.