Redox incident
Message processing capacity reduced. Delays are expected.
Redox experienced a major incident on October 29, 2025 affecting Traffic Processing, lasting 2h 34m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Oct 29, 2025, 04:07 PM UTC
At approximately 10:37 AM Central Time, Redox became aware of an issue with our message processing. The exact number of messages impacted is currently unknown What this means: Messages are presently not processing as expected. This appears to be impacting both synchronous and asynchronous messages. Please expect delays in message receipt until we have identified the issue and implemented a fix. What we will do: After a fix has been implemented, Redox will go through affected messages and determine what action can be taken to rectify the situation If you have any additional questions please reach out to us at [email protected]
- identified Oct 29, 2025, 04:16 PM UTC
We have identified the cause for the message processing issues. This is related to 3rd party vendors experiencing interruptions. They seem to be recovering and our systems are getting working through getting caught up. We are actively working with these vendors to help monitor and resolve the issue. We will update the status of this incident when said fix has been deployed.
- monitoring Oct 29, 2025, 04:50 PM UTC
Our third party vendor has stabilized. Message processing is now performant and our queues are caught up. We will continue monitoring with the help from our vendors. If you have any questions, please contact us at [email protected]
- resolved Oct 29, 2025, 06:41 PM UTC
Messages are now processing normally. If you have any additional questions or are not seeing expected logs, please reach out to [email protected]