LeadSquared incident
Degradation for some LeadSquared services due to an ongoing issue with AWS in the us-east-1
LeadSquared experienced a major incident on October 20, 2025 affecting API and Web Application and 1 more component, lasting 20h 40m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- 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
- 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.
- 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.