LeadSquared Outage History

LeadSquared is up right now

Pingoru has recorded 34 incidents for LeadSquared: 3 in the last 12 months and 0 in the last 90 days.

Source: status.leadsquared.com

34incidents recorded
3last 12 months
0last 90 days
6 daystypical duration
Incidents per month
012AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking LeadSquared in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202617 of 720 (1%)
May 202600 of 744 (0%)
June 202600 of 720 (0%)
July 202600 of 744 (0%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 202600 of 517 (0%)

Incidents, newest first

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. 7h 9m API, Web Application, Mobile Application

Started Apr 02, 2026, 02:46 PM UTC· resolved Apr 02, 2026, 09:55 PM UTC

  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.

Read the full incident report →

Critical March 1, 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. 18d 4h API, Web Application

Started Mar 01, 2026, 01:57 PM UTC· resolved Mar 19, 2026, 06:08 PM UTC

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

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

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

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

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

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

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

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

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

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

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

Critical January 2, 2026 Login failures were observed in SGP region 1h 1m API, Web Application, Mobile Application

Started Jan 02, 2026, 05:58 AM UTC· resolved Jan 02, 2026, 07:00 AM UTC

  1. investigating Jan 02, 2026, 06:49 AM UTC

    We are actively investigating that Leadsquared customers in SGP region may be experiencing issues logging into their accounts. Our engineers are working to resolve the issue and will provide another update shortly.

  2. monitoring Jan 02, 2026, 06:56 AM UTC

    Mitigation actions were implemented and issue is resolved at 12:08 PM. It is currently under active monitoring.

  3. resolved Jan 02, 2026, 08:37 AM UTC

    This incident has been resolved as of 12:08 PM IST.

Read the full incident report →

Major October 20, 2025 Degradation for some LeadSquared services due to an ongoing issue with AWS in the us-east-1 20h 40m API, Web Application, Mobile Application

Started Oct 20, 2025, 07:11 AM UTC· resolved Oct 21, 2025, 03:52 AM UTC

  1. identified Oct 20, 2025, 09:51 AM UTC

    We are currently observing service degradation for some LeadSquared services due to an ongoing issue with AWS in the us-east-1 region. As a result, US customers may experience downtime or degraded performance. Our team is actively monitoring the situation and working closely with AWS to restore full functionality as soon as possible. Follow the below link to check the AWS health status. https://health.aws.amazon.com/health/status?eventID=arn:aws:health:us-east-1::event/MULTIPLE_SERVICES/AWS_MULTIPLE_SERVICES_OPERATIONAL_ISSUE/AWS_MULTIPLE_SERVICES_OPERATIONAL_ISSUE_BA540_514A652BE1A

  2. monitoring Oct 21, 2025, 03:43 AM UTC

    Following AWS’s recovery from the outage in their US region, all LSQ operations have returned to normal as of 03:31 AM IST, October 21. While we do not expect any more instability, we will continue to monitor the situation. We appreciate your patience and understanding during this period.

  3. resolved Oct 21, 2025, 03:52 AM UTC

    The issue impacting LeadSquared services due to the AWS outage in the US region has been fully resolved. All systems have been stable and operating normally since 03:31 AM IST, October 21. Our team has verified service health across all affected components, and no further impact is expected. We will continue to monitor the environment closely to ensure continued stability. Thank you for your patience and understanding during this incident.

Read the full incident report →

Minor August 6, 2025 Performance degradation experienced in Middle East Region 1h 44m API, Web Application

Started Aug 06, 2025, 04:00 AM UTC· resolved Aug 06, 2025, 05:45 AM UTC

  1. investigating Aug 06, 2025, 04:40 AM UTC

    We are currently experiencing slowness in Middle East Region. The team is working on it and we will keep you posted. Apologies for the inconvenience.

  2. identified Aug 06, 2025, 05:21 AM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Aug 06, 2025, 05:24 AM UTC

    A fix has been implemented and we are monitoring the results

  4. resolved Aug 06, 2025, 05:45 AM UTC

    This incident has been resolved.

Read the full incident report →

Major July 29, 2025 Performance degradation experienced in Mumbai Region 56m API, Web Application, Mobile Application

Started Jul 29, 2025, 10:52 AM UTC· resolved Jul 29, 2025, 11:49 AM UTC

  1. investigating Jul 29, 2025, 10:52 AM UTC

    We are currently experiencing slowness in Mumbai Region. The team is working on it and we will keep you posted. Apologies for the inconvenience.

  2. identified Jul 29, 2025, 11:20 AM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Jul 29, 2025, 11:33 AM UTC

    A fix has been implemented and we are monitoring the results

  4. resolved Jul 29, 2025, 11:49 AM UTC

    This incident has been resolved.

Read the full incident report →

Major October 25, 2024 Performance issue in Mumbai Region 3h 47m API, Web Application, Mobile Application

Started Oct 25, 2024, 08:24 AM UTC· resolved Oct 25, 2024, 12:11 PM UTC

  1. investigating Oct 25, 2024, 08:24 AM UTC

    We are observing Partial Outage with one of the DataBase which is impacting Mumbai Region LSQ Application. Backend teams are working on restoring the service.

  2. identified Oct 25, 2024, 08:36 AM UTC

    Teams have identified the issue and working on implementing the fix to restore the Application and services.

  3. monitoring Oct 25, 2024, 10:12 AM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Oct 25, 2024, 12:11 PM UTC

    This incident has been resolved.

Read the full incident report →