LeadSquared Outage History — 2026

Minor April 2, 2026

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.

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

Affected: APIWeb ApplicationMobile Application

Timeline · 4 updates

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.
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.
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.
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.

Read the full incident report →

Critical March 3, 2026

Due to two (earlier one) of the AWS AZs being down in ME region and third AZ experiencing high error rates, LeadSquared is facing high error rates too in ME region.

Detected by Pingoru: Mar 03, 2026, 06:47 PM UTC
Resolved: Mar 19, 2026, 06:08 PM UTC
Duration: 15d 23h

Affected: APIWeb Application

Timeline · 11 updates

investigating Mar 01, 2026, 01:57 PM UTC

We are actively working with AWS to resolve the issue. More details can be referred at below link: https://health.aws.amazon.com/health/status
monitoring Mar 01, 2026, 11:04 PM UTC

Following mitigation actions been taken in the ME region, all LSQ operations have returned to normal as of 03:30 AM IST, March 2. While we do not expect any more instability, we will continue to monitor the situation. We appreciate your patience and understanding during this period.
investigating Mar 02, 2026, 07:38 AM UTC

Due to two of the AWS AZs being down in ME region and third AZ experiencing high error rates, LeadSquared is facing high error rates too in ME region. We are actively working with AWS to resolve the issue. More details can be referred at below link: https://health.aws.amazon.com/health/status
identified Mar 03, 2026, 03:02 PM UTC

March 3, 1:37 PM IST, We have successfully restored select critical functionalities, including Login and read access to key entities. The team is actively working on restoring the remaining functionalities and continues to prioritize full service recovery at the earliest. Further updates will be shared as progress continues.
identified Mar 03, 2026, 06:47 PM UTC

March 3, 10:00 PM IST, We have successfully restored one more critical functionality, related to backend workflows. We are actively working with AWS to resolve the issue. More details can be referred at below link: https://health.aws.amazon.com/health/status
identified Mar 04, 2026, 11:09 AM UTC

March 4, 01:24 AM IST, We have successfully restored critical backend services. We are actively working with AWS to resolve the issue. More details can be referred at below link: https://health.aws.amazon.com/health/status
identified Mar 05, 2026, 05:16 AM UTC

As of March 4, 08:25 PM IST, We have successfully restored reporting capabilities. We are actively working with AWS to resolve the issue. More details can be referred at below link: https://health.aws.amazon.com/health/status
identified Mar 05, 2026, 12:31 PM UTC

While we have successfully restored many critical capabilities, we are actively working with AWS to resolve the issue completely. More details can be referred at below link: https://health.aws.amazon.com/health/status
identified Mar 07, 2026, 03:04 AM UTC

Most critical capabilities have been restored and are currently operating as expected. Our teams continue to work closely with AWS to complete the remaining remediation steps and ensure full service stability. At this point, we will transition to a more targeted communication model, with updates being provided directly to customers who may still be impacted. Customers requiring assistance related to this event are encouraged to contact our Support team. We appreciate your patience and understanding while we worked to restore services. More details can be referred at below link: https://health.aws.amazon.com/health/status
monitoring Mar 18, 2026, 01:33 PM UTC

Critical capabilities have been restored and are currently operating as expected. 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. More details can be referred at below link: https://health.aws.amazon.com/health/status
resolved Mar 26, 2026, 01:02 PM UTC

All LSQ operations have returned to normal as of 11:38 PM IST, March 19. 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.

Read the full incident report →

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.

Due to two (earlier one) of the AWS AZs being down in ME region and third AZ experiencing high error rates, LeadSquared is facing high error rates too in ME region.

Looking to track LeadSquared downtime and outages?