Redox incident

Increased message traffic latency

Minor Resolved View vendor source →

Redox experienced a minor incident on January 14, 2026 affecting Logs (view/search), lasting 12m. The incident has been resolved; the full update timeline is below.

Started
Jan 14, 2026, 03:38 PM UTC
Resolved
Jan 14, 2026, 03:50 PM UTC
Duration
12m
Detected by Pingoru
Jan 14, 2026, 03:38 PM UTC

Affected components

Logs (view/search)

Update timeline

  1. monitoring Jan 14, 2026, 03:38 PM UTC

    At approximately 8:30am CT, Redox became aware of an issue in which some logs were delayed. What this means: you may have experienced a delay before receiving traffic from Redox. However, please be aware that the actual processing of logs was unaffected; message flow was still occurring, albeit at a slower pace. 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 are concerned that your logs have been impacted or have any additional questions, please reach out to [email protected]

  2. resolved Jan 14, 2026, 03:50 PM UTC

    The incident has been resolved and logs delays are declining; the delay is expected to be gone by end of day. If you have any additional questions please reach out to [email protected]