Spare Outage History

Spare is up right now

Spare had 48 outages in the last 2 years totaling 26h 48m of downtime, averaging 2 incidents per month.

There were 48 Spare outages since August 18, 2025 totaling 26h 48m of downtime. Each is summarised below. Incident details, duration, and resolution information.

Source: sparestatus.com

Major September 30, 2026

Temporary Interruption with Support Email Delivery

Detected by Pingoru
Sep 30, 2026, 04:59 PM UTC
Resolved
Sep 30, 2026, 05:06 PM UTC
Duration
6m
Affected: Intercom Email
Timeline · 2 updates
  1. investigating Sep 30, 2026, 04:59 PM UTC

    We are currently investigating a temporary interruption affecting our support email contact channels. At this time, customers may experience difficulties or receive delivery failures when attempting to reach our team via [email protected] and [email protected]. Our team is actively working with our IT department to restore full email functionality as quickly as possible. In the meantime, please reach out to support through our chat channel, and we will be here to help. Thank you for your patience as we work to get this resolved.

  2. resolved Sep 30, 2026, 05:06 PM UTC

    We are pleased to share that the service disruption affecting our support email channels, including [email protected] and [email protected], has been successfully resolved. Our team has worked closely with IT to restore full email functionality, meaning you can once again reach us directly via email. As our systems catch up, please note that if you sent an email to our support team yesterday, you may receive a delayed bounce-back or delivery failure message right now. If you receive one of these delayed notifications, we kindly ask that you resend your message. This will ensure we successfully receive your inquiry so we can continue collaborating and assist you without further delay. Thank you for your patience and understanding throughout this service disruption. We appreciate you bearing with us and look forward to continuing to support you.

Read the full incident report →

Major September 17, 2026

Multimodal bookings failing when a start address contains special characters

Detected by Pingoru
Sep 17, 2026, 02:28 PM UTC
Resolved
Sep 17, 2026, 04:00 PM UTC
Duration
1h 32m
Affected: [United States 1][Canada][United States 2][Japan][European Union]
Timeline · 3 updates
  1. investigating Sep 17, 2026, 02:28 PM UTC

    We're investigating reports that some Multimodal trip bookings fail to complete when a rider confirms a booking whose start address contains special characters. Affected riders see the following error at the confirmation step and the trip is not created: Parameter 'startAddress' must be url encoded. Its value may not contain reserved characters. It has been escalated to our engineering team and is under active investigation. We'll post an update here as we learn more.

  2. identified Sep 17, 2026, 02:59 PM UTC

    We've identified the cause of the Multimodal booking errors and a fix is in progress. Some users may still encounter the error below. If you are booking a non-Multimodal trip and still see this error, refreshing your browser will clear it. Parameter 'startAddress' must be url encoded. Its value may not contain reserved characters. A fix is being deployed that fully resolves this issue for both Multimodal and non-Multimodal bookings, and no browser refresh will be required afterwards. We expect it to be live in approximately 10 minutes and will confirm here once it's out.

  3. resolved Sep 17, 2026, 04:00 PM UTC

    Multimodal and non-Multimodal bookings are both fully resolved — no browser refresh is required. Our logs are healthy following the release, and the error should now be fully mitigated. If you or a rider still encounters the error below, please contact support so we can look into it. We're sorry for the disruption this caused and appreciate your patience.

Read the full incident report →

Minor May 19, 2026

Performance Degradation Across CA (Canada) Service Region

Detected by Pingoru
May 19, 2026, 11:58 PM UTC
Resolved
May 20, 2026, 12:34 AM UTC
Duration
35m
Affected: [iOS][Canada][Android]
Timeline · 4 updates
  1. investigating May 19, 2026, 11:58 PM UTC

    We are currently observing increased latencies across the CA region, which may result in slower-than-expected platform performance and delayed request processing. Our engineering team is actively investigating the issue and working to mitigate the impact as quickly as possible. Further updates will be shared as they become available.

  2. investigating May 20, 2026, 12:08 AM UTC

    We are continuing to investigate increased latencies affecting the CA region. Users may experience intermittent command timeout errors, degraded platform performance, and delays when scheduling or managing rides. Our engineering team remains actively engaged and is working to mitigate the issue as quickly as possible. We will provide additional updates as more information becomes available.

  3. monitoring May 20, 2026, 12:26 AM UTC

    A fix has been applied for the increased latencies affecting the CA region, and platform performance has shown improvement. Our engineering team is continuing to closely monitor the environment to ensure stability and confirm full recovery. We appreciate your patience while we worked through this issue.

  4. resolved May 20, 2026, 12:34 AM UTC

    The incident impacting platform performance and causing increased latencies in the CA (Canada) service region has been resolved as of 17:20 PDT. Our engineering team has confirmed that services have returned to normal operation, and we will continue monitoring to ensure ongoing stability. Thank you for your patience throughout this incident.

Read the full incident report →

Minor April 23, 2026

Manual entries in the break fields were non-editable.

Detected by Pingoru
Apr 23, 2026, 01:59 PM UTC
Resolved
Apr 23, 2026, 01:59 PM UTC
Duration
–
Affected: [United States 1][Canada][United States 2][Japan][European Union]
Timeline · 1 update
  1. resolved Apr 23, 2026, 01:59 PM UTC

    Some agencies experienced issues entering data into the break fields, which affected all break components during manual data entry. Our engineering team identified the root cause and resolved the issue quickly; the feature should be fully operational now.

Read the full incident report →

Minor March 26, 2026

Scout AI Experiencing Performance Issues

Detected by Pingoru
Mar 26, 2026, 10:30 PM UTC
Resolved
Mar 26, 2026, 11:20 PM UTC
Duration
49m
Affected: Scout AI
Timeline · 4 updates
  1. monitoring Mar 26, 2026, 11:01 PM UTC

    A Service Disruption within the third-party provider for Scout AI has been identified and our Engineering Team is monitoring the issue. This might result in delays or disruptions when trying to use the Scout AI Agent, we apologize for any inconveniences this might stem on your side.

  2. monitoring Mar 26, 2026, 11:04 PM UTC

    An ongoing Service Disruption within the third-party provider for Scout AI is active and our Engineering Team is monitoring the issue. This might result in delays or disruptions when trying to use the Scout AI Agent, we apologize for any inconveniences this might stem on your side.

  3. monitoring Mar 26, 2026, 11:05 PM UTC

    An ongoing Service Disruption within the third-party provider for Scout AI is active and our Engineering Team is monitoring the issue. This might result in delays or disruptions when trying to use the Scout AI Agent, we apologize for any inconveniences this might stem on your side.

  4. resolved Mar 26, 2026, 11:20 PM UTC

    The Service Disruption affecting Scout AI agent has been resolved on our third-party vendor's end. Partner Success Managers will follow up in the coming days with additional details. We apologize for any inconveniences this may have created — and appreciate your partnership & patience while we worked on this.

Read the full incident report →

Minor March 26, 2026

Performance Issues on Spare Admin Platform

Detected by Pingoru
Mar 26, 2026, 05:34 PM UTC
Resolved
Mar 26, 2026, 06:22 PM UTC
Duration
48m
Affected: [United States 1]
Timeline · 5 updates
  1. investigating Mar 26, 2026, 05:34 PM UTC

    We are currently investigating an issue impacting platform performance. Users may experience slower response times or intermittent issues across the application. Our engineering team has identified the area of impact and is actively working to mitigate the issue. We will provide further updates as soon as more information becomes available.

  2. investigating Mar 26, 2026, 05:49 PM UTC

    We are continuing to investigate the issue impacting platform performance. At this time, we have not received additional updates, but our engineering team remains actively engaged. We’ll share more information as soon as it becomes available or in the next 15 minutes.

  3. monitoring Mar 26, 2026, 06:04 PM UTC

    The issue impacting platform performance has stabilized, and we are currently seeing recovery across affected services. Our team is continuing to monitor closely to ensure stability, while we conduct a root cause analysis. Further updates will be shared as more information becomes available.

  4. monitoring Mar 26, 2026, 06:21 PM UTC

    The issue impacting platform performance has stabilized, and we are currently seeing recovery across affected services. Our team is continuing to monitor closely to ensure stability, while we conduct a root cause analysis. Further updates will be shared as more information becomes available.

  5. resolved Mar 26, 2026, 06:22 PM UTC

    Platform performance has returned to normal, and all services are operating as expected. Our team will continue conducting a deeper root cause analysis, and Partner Success Managers will follow up in the coming days with additional details. We apologize for any inconveniences this may have created — and appreciate your partnership & patience while we worked on this.

Read the full incident report →

Notice March 10, 2026

Service Slowdowns: Performance Impacted.

Detected by Pingoru
Mar 10, 2026, 04:20 PM UTC
Resolved
Mar 10, 2026, 05:21 PM UTC
Duration
1h
Affected: [Canada]
Timeline · 5 updates
  1. monitoring Mar 10, 2026, 05:13 PM UTC

    We identified an issue causing intermittent platform latency. We will continue to monitor the environment for the next hour to ensure ongoing reliability. Thank you for your patience while we resolve this.

  2. identified Mar 10, 2026, 05:16 PM UTC

    We're still investigating - We identified an issue causing intermittent platform latency. We will continue to monitor the environment for the next hour to ensure ongoing reliability. Thank you for your patience while we resolve this.

  3. identified Mar 10, 2026, 05:18 PM UTC

    We're still investigating - We identified an issue causing intermittent platform latency. We will continue to monitor the environment for the next hour to ensure ongoing reliability. Thank you for your patience while we resolve this.

  4. identified Mar 10, 2026, 05:20 PM UTC

    We identified an issue causing intermittent platform latency. We have since implemented a fix, and our engineering team confirms that performance has stabilized. All services are now operating within normal parameters. We will continue to monitor the environment for the next hour to ensure ongoing reliability. Thank you for your patience while we resolved this.

  5. resolved Mar 10, 2026, 05:21 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 18, 2026

Uber - Open Fleets Connector Issues

Detected by Pingoru
Feb 18, 2026, 06:58 PM UTC
Resolved
Feb 18, 2026, 07:28 PM UTC
Duration
30m
Affected: Third-Party Integrations
Timeline · 3 updates
  1. investigating Feb 18, 2026, 06:58 PM UTC

    We are currently investigating an issue that is affecting trips being dispatched to Uber, causing an NDA outcome. Your organization might also see that vehicles for the Uber Open Fleet are showing an Offline status. We will provide updates in the next 15 minutes or when the Root Cause Analysis has been completed, appreciate your continued patience throughout this process.

  2. monitoring Feb 18, 2026, 07:56 PM UTC

    The issue affecting trips being dispatched to Uber has seen improvements, as we observe the error messages have diminished over the last minutes. We will be actively monitoring for the next 15 minutes, appreciate your continued patience throughout this process.

  3. resolved Feb 18, 2026, 08:00 PM UTC

    Thanks for your continued patience while we’ve been monitoring the Uber – Open Fleets Connector issue. At this time, we’ve observed that the errors affecting trips being dispatched to Uber have significantly diminished, and the connector behavior has stabilized. We will continue to keep an eye on performance on our end to ensure everything remains steady. Your PSM will be reaching out shortly with additional insights and any broader context regarding this incident, including follow-up details once the Root Cause Analysis is finalized. If you notice any new irregularities in the meantime, please don’t hesitate to let us know. Appreciate your partnership and time.

Read the full incident report →

Notice January 19, 2026

Stop pages are unresponsive and loading slowly.

Detected by Pingoru
Jan 19, 2026, 02:21 PM UTC
Resolved
Jan 19, 2026, 02:21 PM UTC
Duration
–
Timeline · 1 update
  1. resolved Jan 19, 2026, 02:51 PM UTC

    Occasional unresponsive pages and loading delays have been reported within Service Planning > Stops. We are aware that pages might have either failed to load with increased latency. The issue is now resolved. Pages are loading correctly and populating as expected without further errors.

Read the full incident report →

Critical January 9, 2026

Spare Support Ticketing System Down

Detected by Pingoru
Jan 09, 2026, 07:50 PM UTC
Resolved
Jan 09, 2026, 09:05 PM UTC
Duration
1h 14m
Affected: Intercom EmailIntercom Chats and Posts
Timeline · 6 updates
  1. investigating Jan 09, 2026, 07:56 PM UTC

    Our Support Ticketing System provider is currently experiencing a Major Service Disruption affecting all of our Customer-facing communication channels. If you happen to have any service disruption related to Spare Platform or Rider/Driver Apps, please contact us at our Outage Phone Line. We apologize for any inconveniences or delays in communication.

  2. investigating Jan 09, 2026, 08:03 PM UTC

    Our Support Ticketing System provider continues to experience a Major Service Disruption, and all customer-facing communication channels remain unavailable. We are monitoring the situation closely as the provider works toward a resolution. If you experience any service disruption related to the Spare Platform or Rider/Driver Apps, please continue to contact us via our Outage Phone Line.

  3. investigating Jan 09, 2026, 08:28 PM UTC

    Our Support Ticketing System provider continues to experience a Major Service Disruption, and all customer-facing communication channels remain unavailable. We are monitoring the situation closely as the provider works toward a resolution. If you experience any service disruption related to the Spare Platform or Rider/Driver Apps, please continue to contact us via our Outage Phone Line.

  4. investigating Jan 09, 2026, 08:43 PM UTC

    Our Support Ticketing System provider continues to experience a Major Service Disruption, and all customer-facing communication channels remain unavailable. We are monitoring the situation closely as the provider works toward a resolution. If you experience any service disruption related to the Spare Platform or Rider/Driver Apps, please continue to contact us via our Outage Phone Line.

  5. investigating Jan 09, 2026, 08:53 PM UTC

    Our Support Ticketing System provider continues to experience a Major Service Disruption, and all customer-facing communication channels remain unavailable. We are monitoring the situation closely as the provider works toward a resolution. If you experience any service disruption related to the Spare Platform or Rider/Driver Apps, please continue to contact us via our Outage Phone Line.

  6. resolved Jan 09, 2026, 10:17 PM UTC

    Our Support Ticketing System is now fully back online, and all communication channels have been restored. Thank you for your patience.

Read the full incident report →