Redox incident

Polling traffic delayed

Resolved after 2 hours 23 minutes, on February 10, 2026.

monitoring Feb 10, 2026, 12:50 PM UTC

At approximately 6:25am ET, Redox became aware of an issue with polling workflows for third-party APIs. What this means: Any messages that would have been generated by these polling workflows would see latency in being delivered to customers by up to an hour. What we're doing: We have implemented a fix and are monitoring the results. You may continue to experience delays as queues catch up. Please contact us at [email protected] if you have any questions.

Started
Feb 10, 2026, 12:50 PM UTC
Resolved
Feb 10, 2026, 03:13 PM UTC
Duration
2h 23m
Detected by Pingoru
Feb 10, 2026, 12:50 PM UTC

Update timeline

  1. monitoring Feb 10, 2026, 12:50 PM UTC

    At approximately 6:25am ET, Redox became aware of an issue with polling workflows for third-party APIs. What this means: Any messages that would have been generated by these polling workflows would see latency in being delivered to customers by up to an hour. What we're doing: We have implemented a fix and are monitoring the results. You may continue to experience delays as queues catch up. Please contact us at [email protected] if you have any questions.

  2. resolved Feb 10, 2026, 03:13 PM UTC

    This incident has been resolved.

Your product runs on more than Redox

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →