Pricing
Status historyRSS updatesStatus API

Powered by Uptimus

    История сбоев Leadsquared

    34 Leadsquared incidents · июль 2019 г. — 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.

    Начало 2 апреля 2026 г. в 14:46 UTC · 7h 9m

    IssuesНезначительный инцидент
    Затронутые компоненты
    Web ApplicationMobile ApplicationAPI
    1. 2 апреля 2026 г. в 14:46 UTCidentified

      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. 2 апреля 2026 г. в 18:47 UTCidentified

      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. 2 апреля 2026 г. в 21:53 UTCmonitoring

      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. 2 апреля 2026 г. в 21:55 UTCresolved

      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.

    Начало 1 марта 2026 г. в 13:57 UTC · 18d 4h

    OutageКритический инцидент
    Затронутые компоненты
    Web ApplicationAPI
    1. 1 марта 2026 г. в 13:57 UTCinvestigating

      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. 1 марта 2026 г. в 23:04 UTCmonitoring

      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. 2 марта 2026 г. в 07:38 UTCinvestigating

      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. 3 марта 2026 г. в 15:02 UTCidentified

      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. 3 марта 2026 г. в 18:47 UTCidentified

      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. 4 марта 2026 г. в 11:09 UTCidentified

      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. 5 марта 2026 г. в 05:16 UTCidentified

      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. 5 марта 2026 г. в 12:31 UTCidentified

      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. 7 марта 2026 г. в 03:04 UTCidentified

      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. 18 марта 2026 г. в 13:33 UTCmonitoring

      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. 26 марта 2026 г. в 13:02 UTCresolved

      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

    Начало 2 января 2026 г. в 05:58 UTC · 1h 1m

    OutageКритический инцидент
    Затронутые компоненты
    Mobile ApplicationWeb ApplicationAPI
    1. 2 января 2026 г. в 06:49 UTCinvestigating

      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. 2 января 2026 г. в 06:56 UTCmonitoring

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

    3. 2 января 2026 г. в 08:37 UTCresolved

      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

    Начало 20 октября 2025 г. в 07:11 UTC · 20h 41m

    OutageСерьёзный инцидент
    Затронутые компоненты
    Web ApplicationMobile ApplicationAPI
    1. 20 октября 2025 г. в 09:51 UTCidentified

      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. 21 октября 2025 г. в 03:43 UTCmonitoring

      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. 21 октября 2025 г. в 03:52 UTCresolved

      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

    Начало 6 августа 2025 г. в 04:00 UTC · 1h 45m

    IssuesНезначительный инцидент
    Затронутые компоненты
    Web ApplicationAPI
    1. 6 августа 2025 г. в 04:40 UTCinvestigating

      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. 6 августа 2025 г. в 05:21 UTCidentified

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

    3. 6 августа 2025 г. в 05:24 UTCmonitoring

      A fix has been implemented and we are monitoring the results

    4. 6 августа 2025 г. в 05:45 UTCresolved

      This incident has been resolved.

    Performance degradation experienced in Mumbai Region

    Начало 29 июля 2025 г. в 10:52 UTC · 57m

    OutageСерьёзный инцидент
    Затронутые компоненты
    Web ApplicationMobile ApplicationAPI
    1. 29 июля 2025 г. в 10:52 UTCinvestigating

      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. 29 июля 2025 г. в 11:20 UTCidentified

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

    3. 29 июля 2025 г. в 11:33 UTCmonitoring

      A fix has been implemented and we are monitoring the results

    4. 29 июля 2025 г. в 11:49 UTCresolved

      This incident has been resolved.

    Performance degradation experienced in Mumbai Region

    Начало 7 апреля 2025 г. в 04:32 UTC · 5h 53m

    OutageСерьёзный инцидент
    Затронутые компоненты
    Web ApplicationMobile ApplicationAPI
    1. 7 апреля 2025 г. в 04:32 UTCinvestigating

      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. 7 апреля 2025 г. в 05:26 UTCidentified

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

    3. 7 апреля 2025 г. в 06:20 UTCmonitoring

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

    4. 7 апреля 2025 г. в 10:25 UTCresolved

      This incident has been resolved.

    Performance issue in Mumbai Region

    Начало 25 октября 2024 г. в 08:24 UTC · 3h 47m

    OutageСерьёзный инцидент
    Затронутые компоненты
    Web ApplicationMobile ApplicationAPI
    1. 25 октября 2024 г. в 08:24 UTCinvestigating

      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. 25 октября 2024 г. в 08:36 UTCidentified

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

    3. 25 октября 2024 г. в 10:12 UTCmonitoring

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

    4. 25 октября 2024 г. в 12:11 UTCresolved

      This incident has been resolved.

    Performance degradation experienced in Mumbai Region

    Начало 15 августа 2024 г. в 18:30 UTC · 12h 0m

    IssuesНезначительный инцидент
    1. 16 августа 2024 г. в 06:41 UTCresolved

      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

    Начало 7 августа 2024 г. в 03:30 UTC · 0m

    OutageСерьёзный инцидент
    1. 7 августа 2024 г. в 06:00 UTCresolved

      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

    Начало 24 декабря 2023 г. в 06:35 UTC · 0m

    Pending
    1. 24 декабря 2023 г. в 06:55 UTCresolved

      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

    Начало 3 ноября 2023 г. в 04:45 UTC · 2h 11m

    Pending
    Затронутые компоненты
    Mobile ApplicationWeb ApplicationAPI
    1. 3 ноября 2023 г. в 04:45 UTCinvestigating

      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. 3 ноября 2023 г. в 06:44 UTCidentified

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

    3. 3 ноября 2023 г. в 06:45 UTCmonitoring

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

    4. 3 ноября 2023 г. в 06:56 UTCresolved

      This incident has been resolved.

    Inaccessibility of a few components in MUM region

    Начало 9 сентября 2023 г. в 04:45 UTC · 0m

    Pending
    1. 9 сентября 2023 г. в 05:53 UTCresolved

      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

    Начало 24 июля 2023 г. в 05:57 UTC · 4h 33m

    Pending
    Затронутые компоненты
    Mobile ApplicationWeb ApplicationAPI
    1. 24 июля 2023 г. в 05:57 UTCinvestigating

      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. 24 июля 2023 г. в 06:26 UTCidentified

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

    3. 24 июля 2023 г. в 10:10 UTCmonitoring

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

    4. 24 июля 2023 г. в 12:19 UTCresolved

      This incident has been resolved.

    Inaccessibility of a few components in US region

    Начало 3 июля 2023 г. в 01:30 UTC · 0m

    IssuesНезначительный инцидент
    1. 3 июля 2023 г. в 02:46 UTCresolved

      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

    Начало 2 июня 2023 г. в 14:45 UTC · 2h 43m

    Pending
    Затронутые компоненты
    Mobile ApplicationWeb ApplicationMobile ApplicationAPIWeb ApplicationAPI
    1. 2 июня 2023 г. в 14:57 UTCinvestigating

      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. 2 июня 2023 г. в 15:39 UTCidentified

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

    3. 2 июня 2023 г. в 15:43 UTCmonitoring

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

    4. 2 июня 2023 г. в 17:28 UTCresolved

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

    Performance degradation experienced in Mumbai Region

    Начало 2 июня 2023 г. в 04:35 UTC · 2h 58m

    Pending
    Затронутые компоненты
    Web ApplicationMobile ApplicationAPI
    1. 2 июня 2023 г. в 05:52 UTCinvestigating

      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. 2 июня 2023 г. в 07:22 UTCidentified

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

    3. 2 июня 2023 г. в 07:28 UTCmonitoring

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

    4. 2 июня 2023 г. в 07:32 UTCresolved

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

    Performance degradation experienced in Mumbai Region

    Начало 23 марта 2023 г. в 06:18 UTC · 1h 46m

    OutageСерьёзный инцидент
    Затронутые компоненты
    Web ApplicationMobile Application
    1. 23 марта 2023 г. в 06:18 UTCidentified

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

    2. 23 марта 2023 г. в 07:06 UTCmonitoring

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

    3. 23 марта 2023 г. в 08:03 UTCresolved

      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

    Начало 22 марта 2023 г. в 06:00 UTC · 42m

    IssuesНезначительный инцидент
    1. 22 марта 2023 г. в 07:16 UTCresolved

      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

    Начало 28 октября 2022 г. в 12:58 UTC · 2h 33m

    IssuesНезначительный инцидент
    Затронутые компоненты
    Web ApplicationMobile Application
    1. 28 октября 2022 г. в 12:58 UTCinvestigating

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

    2. 28 октября 2022 г. в 15:04 UTCinvestigating

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

    3. 28 октября 2022 г. в 15:31 UTCresolved

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