Spare experienced a minor incident on October 8, 2025 affecting [United States 1] and [Canada], lasting 57m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Oct 08, 2025, 12:42 AM UTC
We are currently investigating a service disruption affecting the dispatch of rides to our External Fleet (UZURV). Organizations that utilize UZURV for open-fleets are impacted, as rides are not being dispatched or matched to UZURV drivers at this time. Our Engineering team is actively working to identify the root cause and implement a fix as quickly as possible. We will share more details as soon as they are available. Thank you for your patience as we address this. We will post an update within the next 15 minutes.
- investigating Oct 08, 2025, 01:04 AM UTC
We have successfully identified the cause of the service disruption impacting ride dispatch to our External Fleet (UZURV) and are now deploying a fix. The disruption was caused by a recent code change that introduced new calls to a related service without the necessary permissions, preventing ride creation for our UZURV partners. Organizations that rely on UZURV for open-fleets remain affected at this time, as ride matching is currently failing. Our team has temporarily updated the code to remove the problematic call and is in the process of redeploying the service. We anticipate this rolling deployment will be complete and functionality will be restored within the next 10 minutes. As soon as the deployment is finished, affected organizations should see an immediate improvement in ride dispatch performance. We appreciate your continued patience while we finalize this resolution. We will post our next update in 15 minutes or sooner if the fix is fully deployed.
- monitoring Oct 08, 2025, 01:15 AM UTC
We are continuing to implement the fix for the service disruption affecting ride dispatch to our External Fleet (UZURV). The code update is currently being deployed across our production environment. We anticipate that organizations utilizing UZURV will start to see gradual improvements in ride dispatch performance as the rollout completes over the next few minutes. Some features may remain affected until the full deployment is finished. Our team is closely monitoring the process to ensure a successful recovery. We appreciate your continued patience during this final deployment stage. We will share another update within 15 minutes or as soon as the fix is confirmed to be fully applied.
- monitoring Oct 08, 2025, 01:17 AM UTC
We are continuing to implement the fix for the service disruption affecting ride dispatch to our External Fleet (UZURV). The code update is currently being deployed across our production environment. We anticipate that organizations utilizing UZURV will start to see gradual improvements in ride dispatch performance as the rollout completes over the next few minutes. Some features may remain affected until the full deployment is finished. Our team is closely monitoring the process to ensure a successful recovery. We appreciate your continued patience during this final deployment stage. We will share another update within 15 minutes or as soon as the fix is confirmed to be fully applied.
- monitoring Oct 08, 2025, 01:32 AM UTC
We are continuing to implement the fix for the service disruption affecting ride dispatch to our External Fleet (UZURV). The code update is now being deployed across our production environment. We expect organizations using UZURV to see gradual improvements in ride dispatch performance as the rollout completes over the next few minutes. Some features may still experience minor impact until the deployment is fully finalized. Our team is actively monitoring the rollout to ensure a smooth and successful recovery. We appreciate your continued patience during this final stage and will provide another update within 15 minutes, or sooner if the fix is fully confirmed.
- resolved Oct 08, 2025, 01:40 AM UTC
The production rollout of the fix is now complete. We have confirmed that ride dispatch performance to our External Fleet (UZURV) has fully returned to normal levels. Our monitoring confirms that affected organizations should see an immediate and complete restoration of ride creation and matching functionality. No action is required by our partners or end-users. We will follow up with a detailed Root Cause Analysis (RCA) within 72 hours. We sincerely apologize for the disruption and appreciate your continued patience.