All Systems Operational

Uptime over the past 90 days. View historical uptime.
Administrator Portal Operational
[United States 1] Operational
[Canada] Operational
[United States 2] Operational
[Japan] Operational
[European Union] Operational
Spare Rider Application Operational
[iOS] Operational
[Android] Operational
Spare Driver Application Operational
[iOS] Operational
[Android] Operational
Third-Party Integrations Operational
Twilio Conversations [Driver-Dispatch Messaging] Operational
Third-Party Integrations Operational
AI-Voice Operational
Customer Support Operational
Intercom Email Operational
Intercom Chats and Posts Operational
Scout AI Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

Sep 18, 2026

No incidents reported today.

Sep 17, 2026

Multimodal bookings failing when a start address contains special characters
Resolved - 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.
Sep 17, 09:00 PDT
Identified - 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.
Sep 17, 07:59 PDT
Investigating - 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.
Sep 17, 07:28 PDT

Sep 16, 2026

No incidents reported.

Sep 15, 2026

No incidents reported.

Sep 14, 2026

No incidents reported.

Sep 13, 2026

No incidents reported.

Sep 12, 2026

No incidents reported.

Sep 11, 2026

No incidents reported.

Sep 10, 2026

AI Voice Temporarily Down
Postmortem - Read details
Sep 17, 07:30 PDT
Resolved - We have fully resolved the service disruption that impacted our AI Voice feature between 2:00 PM and 2:55 PM CST today. During this window, users may have been unable to access or utilize AI Voice services.

Our Engineering team has successfully implemented a solution and monitored the system to ensure full stability. The feature is now fully recovered and operating normally.

We truly appreciate your patience and understanding while we worked to restore this service.
Sep 10, 13:19 PDT

Sep 9, 2026

No incidents reported.

Sep 8, 2026

No incidents reported.

Sep 7, 2026

No incidents reported.

Sep 6, 2026

No incidents reported.

Sep 5, 2026

No incidents reported.

Sep 4, 2026

No incidents reported.

Incident History Powered by Atlassian Statuspage