Roadie incident

Core Platform Degradation

Notice Resolved View vendor source →

Roadie experienced a notice incident on June 7, 2025, lasting —. The incident has been resolved; the full update timeline is below.

Started
Jun 07, 2025, 04:30 PM UTC
Resolved
Jun 07, 2025, 04:30 PM UTC
Duration
Detected by Pingoru
Jun 07, 2025, 04:30 PM UTC

Update timeline

  1. resolved Jun 10, 2025, 04:47 AM UTC

    Service Disruption Summary – June 7th 2025 On June 7th beginning at approximately 12:25pm EDT, our alerting notified us of a second, unrelated service interruption for our broker service. Underlying cloud network configuration began causing connection timeouts for the broker service. Roadie engineers quickly identified the cause and pushed a fix. Service was fully restored by 12:45pm EDT. To reduce the likelihood of similar disruptions in the future, we have implemented the following measures: - Adjusted workload requests/limits to avoid further resource constraints. - Added additional alerting on the affected workloads. We apologize for any disruption this may have caused. If you have any questions, please feel free to reach out to us at [email protected].

  2. postmortem Jun 10, 2025, 04:51 AM UTC

    On June 7th beginning at approximately 12:25pm EDT, our alerting notified us of a second, unrelated service interruption for our broker service. Underlying cloud network configuration began causing connection timeouts for the broker service. Roadie engineers quickly identified the cause and pushed a fix. Service was fully restored by 12:45pm EDT. To reduce the likelihood of similar disruptions in the future, we have implemented the following measures: * Adjusted workload requests/limits to avoid further resource constraints. * Added additional alerting on the affected workloads. We apologize for any disruption this may have caused. If you have any questions, please feel free to reach out to us at [[email protected]](mailto:[email protected]).