Störungsverlauf von Leadsquared

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.

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.

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.

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.

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

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.

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

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.

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

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

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

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

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

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

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.

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.

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

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

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

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.

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.

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.

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

A fix has been implemented and we are monitoring the results

This incident has been resolved.

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

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

A fix has been implemented and we are monitoring the results

This incident has been resolved.

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

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

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

This incident has been resolved.

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.

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

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

This incident has been resolved.

We observed performance degradation for Web Application in Mumbai Region. Issue was identified by the monitoring systems and backend engineering team have implemented the corrective actions to restore the application. Apologies for the inconvenience.

We experienced inaccessibility of a few components in MUM region for a brief amount of time. The issue was fixed, Apologies for the inconvenience.

We experienced inaccessibility of a few components in MUM region for a brief amount of time. The issue was fixed immediately. Apologies for the inconvenience.

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

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

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

This incident has been resolved.

We experienced inaccessibility of a few components in MUM region for a brief amount of time. The issue was fixed immediately. Apologies for the inconvenience.

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

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

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

This incident has been resolved.

We experienced inaccessibility of a few components in US region for a brief amount of time. The issue was fixed immediately. Apologies for the inconvenience.

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

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

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

The incident has been resolved. Apologies for the inconvenience caused.

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

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

A fix has been implemented and we are monitoring the Database performance.

The incident has been resolved. Apologies for the inconvenience caused.

We are currently experiencing slowness in application hosted in Mumbai Region. The team is working on it and we will keep you posted.

The issue has been identified and a fix has applied. The application is working in normal conditions. We will continue to monitor.

The issue is now resolved and users are able to access the application. We apologize for the inconvenience caused.

Few customers in Mumbai region faced issues accessing LeadSquared application between 11:30 AM IST and 12:12 PM IST. We have identified the issue and applied the patch. The issue is now resolved and users are able to access the application. We apologize for the inconvenience caused.

A few of our customers are experiencing slowness in MUM Region. The team is on it and we will keep you posted.

We have identified the issue and a fix has been applied. We are monitoring the results.

The incident has been resolved and the application is working in normal condition. Thank you for your patience