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.

Update timeline

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.