Redox Status Page

May 6, 2026 · resolved May 6

### 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 transmissions for MLLP traffic. Service was fully restored by **6:10 PM CT** after configuration settings were corrected and gateway services were restarted. ### What Happened The service interruption was triggered during a planned migration of our network configuration management system. * **Summary of Causes:** During the transition to a new configuration framework, an authentication credential used by the network proxy service was incorrectly identified as unused and subsequently removed. While pre-deployment testing appeared successful, the removal of this credential caused authorization failures once applied across the broader production environment. * **Summary of Impact:** VPN-based connections for outbound data experienced a loss of egress connectivity. They would get an error on the first outbound message on a subscription to a VPN destination. Transmissions were queued during the issue and sent after the problem was resolved; no transmissions were dropped. ### What we are doing about this: * **Enhanced Testing Protocols:** We are developing new end-to-end tests specifically for outbound MLLP traffic to ensure that connectivity is verified across all gateways during configuration changes. * **Improved Service Observability:** We are updating our alerting logic for our proxy services to trigger more immediate notifications if egress traffic volume drops below expected thresholds, ensuring faster detection.

Apr 13, 2026 · resolved Apr 13

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 [email protected]

Mar 16, 2026 · resolved Mar 16

The incident has been resolved and logs delays are at nominal levels. If you have any additional questions please reach out to [email protected]

Mar 5, 2026 · resolved Mar 10

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 [email protected]

Feb 27, 2026 · resolved Feb 27

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 [email protected]