Smartcar incident

Smartcar Connect and API 5xx Errors

Critical Resolved View vendor source →

Smartcar experienced a critical incident on February 27, 2025 affecting Smartcar Webhooks and API and Smartcar Connect, lasting 3h 5m. The incident has been resolved; the full update timeline is below.

Started
Feb 27, 2025, 12:48 AM UTC
Resolved
Feb 27, 2025, 03:53 AM UTC
Duration
3h 5m
Detected by Pingoru
Feb 27, 2025, 12:48 AM UTC

Affected components

Smartcar Webhooks and APISmartcar Connect

Update timeline

  1. investigating Feb 27, 2025, 12:48 AM UTC

    We are currently investigating an outage resulting in 5xx errors in Connect and API. We will provide updates as soon as more information becomes available. Thank you for your patience.

  2. monitoring Feb 27, 2025, 12:55 AM UTC

    We have identified the cause of the issue affecting Connect and API requests. The outage was caused by an issue introduced in a recent code update. The change has been reverted and services are returning to normal. We are monitoring the system to ensure stability.

  3. resolved Feb 27, 2025, 03:53 AM UTC

    We experienced a brief period of downtime for Connect and API services between 4:32 PM and 4:50 PM PST due to an issue introduced in a recent code update. A fix has been implemented, and all services are now fully operational. We are closely monitoring the system to ensure continued stability and will share additional details as we complete our investigation. Thank you for your patience and understanding.

  4. postmortem Feb 28, 2025, 06:42 PM UTC

    Smartcar API service had a downtime from 2/26/2025 04:32:00 PM PST - 04:50:00 PM PST for a total of 18 minutes of service impact. During this time API service experience a partial outage. A small portion of our incoming request were being serviced. The partial outage was caused by a bad code merge in API. This lead to a out memory error for our containers. The issue was resolved by rolling back the deployment. If you have any additional questions, feel free to reach out to us at [[email protected]](mailto:[email protected]).