Roadie Outage History

Roadie is up right now

Roadie had 5 outages in the last 2 years totaling 3h 57m of downtime — averaging 0.2 incidents per month.

There were 5 Roadie outages since June 3, 2025 totaling 3h 57m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.roadie.com

Minor September 4, 2025

Core Platform Degradation

Detected by Pingoru
Sep 04, 2025, 01:41 PM UTC
Resolved
Sep 04, 2025, 02:07 PM UTC
Duration
25m
Affected: Core Platform
Timeline · 3 updates
  1. investigating Sep 04, 2025, 01:41 PM UTC

    We are currently investigating an issue with consolidation creation.

  2. monitoring Sep 04, 2025, 01:48 PM UTC

    A fix has been implemented and we are monitoring.

  3. resolved Sep 04, 2025, 02:07 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 19, 2025

Driver Routes Degraded Performance

Detected by Pingoru
Aug 19, 2025, 02:54 PM UTC
Resolved
Aug 19, 2025, 04:34 PM UTC
Duration
1h 40m
Affected: Core Platform
Timeline · 4 updates
  1. investigating Aug 19, 2025, 02:54 PM UTC

    We are currently investigating a service disruption affecting real-time driver route updates. Drivers are able to offer and be assigned but cannot move forward with starting gigs.

  2. identified Aug 19, 2025, 03:38 PM UTC

    We identified an issue with route creation. We see that routes are currently being created properly.

  3. monitoring Aug 19, 2025, 03:50 PM UTC

    We are seeing improvements on routes being created. The core platform is stable and we will continue to monitor.

  4. resolved Aug 19, 2025, 04:34 PM UTC

    This incident has been resolved. Driver routes are stable.

Read the full incident report →

Minor June 6, 2025

Core Platform Service Degradation

Detected by Pingoru
Jun 06, 2025, 11:03 PM UTC
Resolved
Jun 06, 2025, 11:41 PM UTC
Duration
38m
Affected: Core Platform
Timeline · 5 updates
  1. investigating Jun 06, 2025, 11:03 PM UTC

    On June 6th 2025 at approximately 6:45pm EST, our platform began experiencing a brief service degradation. An unexpected resource constraint on one of our internal servers resulted in a degradation of services, affecting gig creation. While the system remains stable overall, this degradation is affecting gig creation and general performance. We will keep you informed as we gather more information about the cause and scope of this incident. Roadie Support and Operations teams will be available to help facilitate any delivery challenges you experience due to the incident. Roadie appreciates your patience and apologizes for the inconvenience. If you have any questions or concerns please reach out to your Roadie Account Manager or [email protected].

  2. investigating Jun 06, 2025, 11:25 PM UTC

    Roadie engineers are continuing to investigate this issue.

  3. identified Jun 06, 2025, 11:27 PM UTC

    Roadie engineers have identified the issue, implemented a fix, and are monitoring the platform closely.

  4. resolved Jun 06, 2025, 11:41 PM UTC

    The incident has been resolved and core platform services are restored to normal functioning. We appreciate your patience and apologize for the inconvenience.

  5. postmortem Jun 10, 2025, 04:44 AM UTC

    **Service Disruption Summary – June 6th 2025** On June 6th 2025 beginning at approximately 6:45pm EDT, our platform experienced a partial service degradation. An unexpected resource constraint on one of our internal servers resulted in a degradation of services, affecting gig creation and overall performance. The underlying issue was identified quickly, but resolution required safely restarting all affected services which was completed by 7:41pm 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]).

Read the full incident report →