LeadSquared incident

Degraded performance is observed in the US region for certain features due to an ongoing AWS OpenSearch Service issue in the us-east-1 region.

Minor Resolved View vendor source →

LeadSquared experienced a minor incident on April 2, 2026 affecting API and Web Application and 1 more component, lasting 7h 9m. The incident has been resolved; the full update timeline is below.

Started
Apr 02, 2026, 02:46 PM UTC
Resolved
Apr 02, 2026, 09:55 PM UTC
Duration
7h 9m
Detected by Pingoru
Apr 02, 2026, 02:46 PM UTC

Affected components

APIWeb ApplicationMobile Application

Update timeline

  1. identified Apr 02, 2026, 02:46 PM UTC

    We are observing degraded performance in some functionalities of the LeadSquared application in the US region due to an ongoing AWS OpenSearch Service issue in the us-east-1 region. We are actively working with AWS to restore performance.

  2. identified Apr 02, 2026, 06:47 PM UTC

    We have restored functionality for a subset of customers and are actively working to restore service for the remaining users. We appreciate your patience as we continue to resolve this issue.

  3. monitoring Apr 02, 2026, 09:53 PM UTC

    We have restored functionality and are actively monitoring. Customers requiring assistance related to this event are encouraged to contact our Support team. We appreciate your patience and understanding while we have worked to restore services.

  4. resolved Apr 02, 2026, 09:55 PM UTC

    All LSQ operations have returned to normal as of 1:57 AM IST, April 3. Customers requiring assistance related to this event are encouraged to contact our Support team. We appreciate your patience and understanding while we have worked to restore services.