Pricing
Status historyRSS updatesStatus API

Powered by Uptimus

    Leadsquared 中断历史

    34 Leadsquared incidents · 2019年7月 — official updates, affected components, duration and resolution details.

    返回当前状态

    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.

    开始时间 2026年4月2日 UTC 14:46 · 7h 9m

    Issues轻微事件
    受影响的组件
    Web ApplicationMobile ApplicationAPI
    1. 2026年4月2日 UTC 14:46identified

      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. 2026年4月2日 UTC 18:47identified

      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. 2026年4月2日 UTC 21:53monitoring

      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. 2026年4月2日 UTC 21:55resolved

      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.

    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.

    开始时间 2026年3月1日 UTC 13:57 · 18d 4h

    Outage严重事件
    受影响的组件
    Web ApplicationAPI
    1. 2026年3月1日 UTC 13:57investigating

      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. 2026年3月1日 UTC 23:04monitoring

      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. 2026年3月2日 UTC 07:38investigating

      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. 2026年3月3日 UTC 15:02identified

      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. 2026年3月3日 UTC 18:47identified

      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. 2026年3月4日 UTC 11:09identified

      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. 2026年3月5日 UTC 05:16identified

      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. 2026年3月5日 UTC 12:31identified

      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. 2026年3月7日 UTC 03:04identified

      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. 2026年3月18日 UTC 13:33monitoring

      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. 2026年3月26日 UTC 13:02resolved

      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.

    Login failures were observed in SGP region

    开始时间 2026年1月2日 UTC 05:58 · 1h 1m

    Outage严重事件
    受影响的组件
    Mobile ApplicationWeb ApplicationAPI
    1. 2026年1月2日 UTC 06:49investigating

      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. 2026年1月2日 UTC 06:56monitoring

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

    3. 2026年1月2日 UTC 08:37resolved

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

    Degradation for some LeadSquared services due to an ongoing issue with AWS in the us-east-1

    开始时间 2025年10月20日 UTC 07:11 · 20h 41m

    Outage重大事件
    受影响的组件
    Web ApplicationMobile ApplicationAPI
    1. 2025年10月20日 UTC 09:51identified

      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. 2025年10月21日 UTC 03:43monitoring

      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. 2025年10月21日 UTC 03:52resolved

      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.

    Performance degradation experienced in Middle East Region

    开始时间 2025年8月6日 UTC 04:00 · 1h 45m

    Issues轻微事件
    受影响的组件
    Web ApplicationAPI
    1. 2025年8月6日 UTC 04:40investigating

      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. 2025年8月6日 UTC 05:21identified

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

    3. 2025年8月6日 UTC 05:24monitoring

      A fix has been implemented and we are monitoring the results

    4. 2025年8月6日 UTC 05:45resolved

      This incident has been resolved.

    Performance degradation experienced in Mumbai Region

    开始时间 2025年7月29日 UTC 10:52 · 57m

    Outage重大事件
    受影响的组件
    Web ApplicationMobile ApplicationAPI
    1. 2025年7月29日 UTC 10:52investigating

      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. 2025年7月29日 UTC 11:20identified

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

    3. 2025年7月29日 UTC 11:33monitoring

      A fix has been implemented and we are monitoring the results

    4. 2025年7月29日 UTC 11:49resolved

      This incident has been resolved.

    Performance degradation experienced in Mumbai Region

    开始时间 2025年4月7日 UTC 04:32 · 5h 53m

    Outage重大事件
    受影响的组件
    Web ApplicationMobile ApplicationAPI
    1. 2025年4月7日 UTC 04:32investigating

      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. 2025年4月7日 UTC 05:26identified

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

    3. 2025年4月7日 UTC 06:20monitoring

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

    4. 2025年4月7日 UTC 10:25resolved

      This incident has been resolved.

    Performance issue in Mumbai Region

    开始时间 2024年10月25日 UTC 08:24 · 3h 47m

    Outage重大事件
    受影响的组件
    Web ApplicationMobile ApplicationAPI
    1. 2024年10月25日 UTC 08:24investigating

      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. 2024年10月25日 UTC 08:36identified

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

    3. 2024年10月25日 UTC 10:12monitoring

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

    4. 2024年10月25日 UTC 12:11resolved

      This incident has been resolved.

    Performance degradation experienced in Mumbai Region

    开始时间 2024年8月15日 UTC 18:30 · 12h 0m

    Issues轻微事件
    1. 2024年8月16日 UTC 06:41resolved

      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.

    Performance degradation experienced in Mumbai Region

    开始时间 2024年8月7日 UTC 03:30 · 0m

    Outage重大事件
    1. 2024年8月7日 UTC 06:00resolved

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

    Inaccessibility of a few components in MUM region

    开始时间 2023年12月24日 UTC 06:35 · 0m

    Pending
    1. 2023年12月24日 UTC 06:55resolved

      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.

    Performance degradation experienced in Singapore Region

    开始时间 2023年11月3日 UTC 04:45 · 2h 11m

    Pending
    受影响的组件
    Mobile ApplicationWeb ApplicationAPI
    1. 2023年11月3日 UTC 04:45investigating

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

    2. 2023年11月3日 UTC 06:44identified

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

    3. 2023年11月3日 UTC 06:45monitoring

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

    4. 2023年11月3日 UTC 06:56resolved

      This incident has been resolved.

    Inaccessibility of a few components in MUM region

    开始时间 2023年9月9日 UTC 04:45 · 0m

    Pending
    1. 2023年9月9日 UTC 05:53resolved

      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.

    Performance degradation experienced in Singapore Region

    开始时间 2023年7月24日 UTC 05:57 · 4h 33m

    Pending
    受影响的组件
    Mobile ApplicationWeb ApplicationAPI
    1. 2023年7月24日 UTC 05:57investigating

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

    2. 2023年7月24日 UTC 06:26identified

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

    3. 2023年7月24日 UTC 10:10monitoring

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

    4. 2023年7月24日 UTC 12:19resolved

      This incident has been resolved.

    Inaccessibility of a few components in US region

    开始时间 2023年7月3日 UTC 01:30 · 0m

    Issues轻微事件
    1. 2023年7月3日 UTC 02:46resolved

      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.

    Performance degradation experienced in Mumbai & Singapore Region

    开始时间 2023年6月2日 UTC 14:45 · 2h 43m

    Pending
    受影响的组件
    Mobile ApplicationWeb ApplicationMobile ApplicationAPIWeb ApplicationAPI
    1. 2023年6月2日 UTC 14:57investigating

      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.

    2. 2023年6月2日 UTC 15:39identified

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

    3. 2023年6月2日 UTC 15:43monitoring

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

    4. 2023年6月2日 UTC 17:28resolved

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

    Performance degradation experienced in Mumbai Region

    开始时间 2023年6月2日 UTC 04:35 · 2h 58m

    Pending
    受影响的组件
    Web ApplicationMobile ApplicationAPI
    1. 2023年6月2日 UTC 05:52investigating

      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.

    2. 2023年6月2日 UTC 07:22identified

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

    3. 2023年6月2日 UTC 07:28monitoring

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

    4. 2023年6月2日 UTC 07:32resolved

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

    Performance degradation experienced in Mumbai Region

    开始时间 2023年3月23日 UTC 06:18 · 1h 46m

    Outage重大事件
    受影响的组件
    Web ApplicationMobile Application
    1. 2023年3月23日 UTC 06:18identified

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

    2. 2023年3月23日 UTC 07:06monitoring

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

    3. 2023年3月23日 UTC 08:03resolved

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

    Issue with accessing LeadSquared application in Mumbai region

    开始时间 2023年3月22日 UTC 06:00 · 42m

    Issues轻微事件
    1. 2023年3月22日 UTC 07:16resolved

      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.

    Performance degradation - MUM Region

    开始时间 2022年10月28日 UTC 12:58 · 2h 33m

    Issues轻微事件
    受影响的组件
    Web ApplicationMobile Application
    1. 2022年10月28日 UTC 12:58investigating

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

    2. 2022年10月28日 UTC 15:04investigating

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

    3. 2022年10月28日 UTC 15:31resolved

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