Redox

Cyber and operational findings

Analyst-reviewed records. The grade states how well the cause is established; event, first public observation and acknowledgement are separate dates.

No public findings for this organisation.

Provider status posts

Collected from the organisation's own public status page. These are its words; DFX adds only the wording classification.

• Log visibility is delayedSep 9 12:54 UTC · postmortem · minor impact
  Service restricted or degradedInvestigation mentionedRestoration reported
  1. Sep 9 12:54 UTC investigating: We are aware of an issue where logs are not visible in the dashboard. While logs are still processing properly, the dashboard is not displaying them as expected. If you have questions about specific logs or your connection and whether it has been affected, please contact us...
  2. Sep 9 13:21 UTC identified: We have identified the cause for the log visibility issues and are actively working on a fix. We will update the status of this incident when the fix has been deployed.
  3. Sep 9 13:51 UTC identified: We have pushed a fix that will make new logs visible, however logs received between approximately 5:45PM and 8:40AM will still not be viewable. The backlogs of logs will continue to process through the queue while it catches up.
  4. Sep 9 14:38 UTC monitoring: A fix has been implemented and visibility for the logs in the backlog is returning. We are actively monitoring the situation and ensuring that all affected logs are visible again.
  5. Sep 9 18:51 UTC resolved: This incident has been resolved. Log visibility is restored. If you have any questions, please reach out to support@redoxengine.com
  6. Sep 14 22:27 UTC postmortem: ## Summary Following an emergency failover carried out in response to a third-party outage on September 8, a configuration change made to stabilize that failover infrastructure reduced capacity on the system powering dashboard and log visibility. Message processing itself was...
  View on the provider's status page
• Unexpected API and Dashboard Outage - 3rd party service outageSep 8 18:59 UTC · postmortem · minor impact
  Service restricted or degradedInvestigation mentionedRestoration reported
  1. Sep 8 18:59 UTC investigating: Our automated monitoring tools detected a major outage affecting the API and main site/dashboard at 1:34pm Central. Our team is currently investigating the cause and working on a solution. Please work with your teams to implement downtime procedures. If you have any additional...
  2. Sep 8 19:25 UTC monitoring: We applied a fix at 2:23pm Central and processing appears to be operating as normal. We are still seeing delays in log visibility. We will continue to monitor to verify that the issues are fully resolved with our 3rd party vendor.
  3. Sep 8 21:04 UTC resolved: The incident has been resolved. Please do not hesitate to reach out to support@redoxengine.com if you are continuing to run into anything unexpected.
  4. Sep 14 22:23 UTC postmortem: ## Summary On September 8, an outage at a third-party infrastructure provider we rely on for message processing disrupted our platform for approximately 40 minutes, delaying asynchronous processing and returning errors on synchronous requests. Additionally, this slowed down our...
  View on the provider's status page
• Documents are not returned in Carequality DocumentGet requestsJul 9 16:59 UTC · postmortem · minor impact
  Investigation mentionedRestoration reported
  1. Jul 9 16:59 UTC investigating: At approximately 11:43am CT, Redox became aware of an issue with DocumentGet requests sent outbound to other organizations on the Carequality network. What this means: DocumentGet requests to retrieve documents from other organizations on the Carequality network might not...
  2. Jul 9 17:32 UTC monitoring: A fix has been implemented for and document requests are now working as expected. We're actively monitoring the situation to ensure continued successes. If you had failed DocumentGet queries for Carequality you can re-query and you will now get responses. If you have any...
  3. Jul 9 18:16 UTC resolved: The incident has been resolved and the Redox Engine has resumed normal operations. If you have any additional questions please reach out to support@redoxengine.com
  4. Jul 15 16:51 UTC postmortem: ## Summary Between Wednesday, July 8, 2026 at approximately 1:00 PM CT and Thursday, July 9, 2026 at 12:47 PM CT, customers using Carequality DocumentGet received empty document data in responses. Requests appeared to complete successfully on both ends, but document content was...
  View on the provider's status page
• Delayed Dashboard message/transmission logsJun 22 16:02 UTC · resolved · minor impact
  Service restricted or degradedInvestigation mentionedRestoration reported
  1. Jun 22 16:02 UTC investigating: The visibility of RedoxEngine message/transmission logs in the dashboard have fallen behind starting at 10:15 AM Central. Our team is currently investigating the cause and working on a solution. Overall message traffic is unaffected. If you have any additional questions,...
  2. Jun 22 16:27 UTC investigating: We are continuing to investigate this issue.
  3. Jun 22 17:59 UTC identified: We have identified the cause for the log visibility issues and are actively working on a fix. We are seeing the number of messages with delays decrease. We will update the status of this incident when said fix has been deployed.
  4. Jun 22 18:50 UTC monitoring: A fix has been implemented and we are monitoring the results.
  5. Jun 23 15:07 UTC resolved: This incident has been resolved.
  View on the provider's status page
• Issue with outgoing VPN trafficMay 6 22:20 UTC · postmortem · major impact
  Service restricted or degradedSign-in disruptionRestoration reported
  1. May 6 22:20 UTC investigating: At approximately 4:45pm CT, Redox became aware of an issue impacting VPN tunnels. Impacted tunnels will see errors in attempts to deliver messages to destinations. What this means: you may experience a delay before receiving traffic from Redox. We are actively looking into...
  2. May 6 22:38 UTC identified: The issue has been identified and a fix is being implemented.
  3. May 6 22:55 UTC monitoring: A fix has been implemented and we are monitoring the results. VPN message traffic is resuming as normal.
  4. May 6 23:14 UTC resolved: Messages are now processing normally. While we were unable to send VPN traffic we queued messages and now that VPNs are up and stable we are sending out all those messages. If you have any additional questions or are not seeing expected logs, please reach out to...
  5. May 22 21:56 UTC postmortem: ### Summary Between **4:20 PM CT and 5:38 PM CT** on May 6, 2026, some customers experienced an interruption in outbound traffic for VPN-based connections. During this window, data egressing via the network proxy service failed to authorize, resulting in unsuccessful...
  View on the provider's status page
• Increased rate of errors for Carequality queriesApr 13 16:12 UTC · resolved · minor impact
  No classified wording
  1. Apr 13 16:12 UTC investigating: We are aware of an issue with organizations querying the Redox Gateway over the Carequality network. Queries may receive an increased rate of HTTP 500 responses. All traffic not related to Carequality is unaffected. If you have further questions regarding this issue, please...
  2. Apr 13 21:11 UTC resolved: A fix has been implemented and we are monitoring the results. Error rates have returned to a normal range. If you have further questions, please reach out to support@redoxengine.com
  View on the provider's status page
• Partial Log DelayMar 16 14:51 UTC · resolved · minor impact
  Service restricted or degradedRestoration reported
  1. Mar 16 14:51 UTC investigating: Redox is currently experiencing a delay in some logs. About an eighth of logs are delayed by under and hour. 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...
  2. Mar 16 15:06 UTC monitoring: A fix has been implemented for the delay issues and Redox is actively monitoring our logs. You may continue to experience delays as queues catch up to the present. If you have questions please reach out to support@redoxengine.com
  3. Mar 16 15:37 UTC resolved: The incident has been resolved and logs delays are at nominal levels. If you have any additional questions please reach out to support@redoxengine.com
  View on the provider's status page
• Unexpected Dashboard Alerting OutageMar 5 20:48 UTC · resolved · major impact
  Service restricted or degradedInvestigation mentionedRestoration reported
  1. Mar 5 20:48 UTC investigating: Our automated monitoring tools detected a partial outage affecting the dashboard at ~2:00 PM Central. Intermittently, alert rules are unable to be loaded within the dashboard and a subset of alerts are not triggering as expected. Our team is currently investigating the cause and...
  2. Mar 5 22:25 UTC identified: We're continuing to investigate the root cause of the issue. It appears to be related to a third-party vendor. We are seeing degraded performance rather than an outage at this time. We are reaching out to this partner to assist with additional troubleshooting. Additionally, we...
  3. Mar 5 23:40 UTC identified: A fix has been put in place for the dashboard so it now reflects current alert statuses as expected. We are continuing to work toward more reliable alert notification services.
  4. Mar 6 14:26 UTC identified: We have identified the cause for the ongoing notification issue and are actively implementing a fix. We will update the status of this incident when this fix has been fully deployed.
  5. Mar 6 16:48 UTC identified: The fix was deployed but we are still seeing intermittent errors on our end. We have been communicating with our 3rd party vendor to assist further. We will continue to provide updates as they become available.
  6. Mar 6 16:49 UTC identified: The fix was deployed but we are still seeing intermittent errors on our end. We have been communicating with our 3rd party vendor to assist further. We will continue to provide updates as they become available.
  7. Mar 6 21:33 UTC identified: Our third-party vendor is in the process of recovering from an incident on their end. We are doing everything within our power on the Redox side to mitigate from our end. We will continue to provide updates as they become available and will have more information available on...
  8. Mar 9 14:56 UTC identified: Our third party vendor has completed their recovery and is monitoring things as are we. Alerts are working as expected and we closing monitoring the situation to ensure this continues. If you have any additional questions, please contact support@redoxengine.com
  9. Mar 9 14:56 UTC monitoring: Our third party vendor has completed their recovery and is monitoring things as are we. Alerts are working as expected and we closing monitoring the situation to ensure this continues. If you have any additional questions, please contact support@redoxengine.com
  10. Mar 10 16:36 UTC resolved: This issue has been resolved as our third party vendor has resolved the issue and our alerts stayed operational through our monitoring process. If you have any additional questions please reach out to support@redoxengine.com
  View on the provider's status page
• Delays in message processing for Data on DemandFeb 27 18:14 UTC · resolved
  Service restricted or degradedRestoration reported
  1. Feb 27 18:14 UTC investigating: Redox is aware of an issue with our message processing for Data on Demand. What this means: We see ~15 min delay in processing than expected. We’ve found the source of the trouble and the fix is in place. Systems are returning to normal, and you should see full functionality...
  2. Feb 27 18:16 UTC monitoring: A fix has been implemented and we are monitoring the results.
  3. Feb 27 18:26 UTC resolved: Messages are now processing normally. All affected queues have been resumed. If you have any additional questions or are not seeing expected logs, please reach out to support@redoxengine.com
  View on the provider's status page
• Log processing is delayedFeb 26 17:33 UTC · postmortem · minor impact
  Service restricted or degraded
  1. Feb 26 17:33 UTC identified: We are aware of an issue with our message processing. What this means: Messages are presently not processing as expected. Logs are taking longer to process than expected. Please expect delays in message receipt until we have identified the issue and implemented a fix. What...
  2. Feb 26 17:39 UTC monitoring: A fix has been implemented for the traffic processing issue and we are monitoring the results. Message processing latency is catching up. If you have any questions, please contact us at support@redoxengine.com
  3. Feb 26 17:47 UTC resolved: Messages are now processing normally. If you have any additional questions or are not seeing expected logs, please reach out to support@redoxengine.com
  4. Mar 10 22:56 UTC postmortem: **What Happened** On **February 26, 2026** at approximately **10:16 AM CT**, our production environment experienced elevated latency across all asynchronous traffic processing. The incident was triggered when core processing workers were unintentionally scaled to a minimal...
  View on the provider's status page
• VPN Degradation for subset of VPN tunnelsFeb 23 20:31 UTC · postmortem · major impact
  Service restricted or degradedInvestigation mentionedRestoration reported
  View on the provider's status page
• Latency in viewing logsFeb 23 16:16 UTC · resolved · minor impact
  No classified wording
  View on the provider's status page
• Issue With Message ProcessingFeb 23 07:09 UTC · postmortem · minor impact
  Service restricted or degradedRestoration reported
  View on the provider's status page
• Polling traffic delayedFeb 10 12:50 UTC · resolved
  Service restricted or degradedRestoration reported
  View on the provider's status page
• Increased errors on Carequality Location queriesFeb 6 19:19 UTC · resolved · minor impact
  Investigation mentionedRestoration reported
  View on the provider's status page
• Delayed Dashboard message/transmission logsFeb 2 08:11 UTC · resolved
  Service restricted or degradedInvestigation mentionedRestoration reported
  View on the provider's status page
• Delayed Dashboard message/transmission logsJan 21 19:11 UTC · resolved · minor impact
  Service restricted or degradedInvestigation mentioned
  View on the provider's status page
• Increased message traffic latencyJan 14 15:38 UTC · resolved · minor impact
  Service restricted or degradedRestoration reported
  View on the provider's status page
• Message Visibility and Customer Alerting IssueDec 1 16:20 UTC · resolved · minor impact
  Service restricted or degradedInvestigation mentioned
  View on the provider's status page
• Message processing capacity reduced. Delays are expected.Oct 29 16:06 UTC · resolved · major impact
  Service restricted or degradedRestoration reported
  View on the provider's status page
• Alert emails pausedOct 27 13:28 UTC · resolved · minor impact
  Service restricted or degradedRestoration reported
  View on the provider's status page
• Logs observability is delayed, some processing impactedSep 30 16:54 UTC · postmortem · minor impact
  Service restricted or degradedRestoration reported
  View on the provider's status page
• Flat File SFTP Not ProcessingSep 30 00:30 UTC · resolved
  No classified wording
  View on the provider's status page
• Increased message traffic latencySep 29 16:11 UTC · postmortem · minor impact
  Service restricted or degradedInvestigation mentionedRestoration reported
  View on the provider's status page
• Increased latency for traffic processingSep 10 13:33 UTC · resolved · minor impact
  Restoration reported
  View on the provider's status page