Sprinklr Outage History

We would like to inform you that the dashboard is currently displaying an "Oops" error due to ongoing infrastructure issues. We are actively working on resolving this issue and will keep you informed with further updates. We apologize for the inconvenience caused and appreciate your patience during this time. If you have any questions or need further assistance, please don't hesitate to reach out to Sprinklr Support.

We are pleased to inform you that the issue causing the "Oops" error on the dashboard has now been resolved. Our team has addressed the underlying infrastructure problem, and the dashboards should now be functioning as expected. We will continue to monitor the system to ensure stability. We sincerely apologize for any inconvenience caused and appreciate your patience throughout this process. If you have any further questions or require assistance, please feel free to reach out to Sprinklr Support.

Hi Team, We’d like to inform you that an issue has been observed with the URL services in Prod3, which may result in errors while loading URLs. we recommend performing a hard refresh, clearing browser cookies, or re-logging into the platform. Our team is actively investigating this with high priority to identify the root cause and restore full functionality as soon as possible. We’ll keep you posted with further updates as we make progress. Thank you for your understanding and support.

Hi Team, We have observed intermittent access issues affecting some of our services. Upon investigation, we’ve identified that this behavior is related to an ongoing incident reported by AWS UAE region. According to AWS's latest status update (https://health.aws.amazon.com/health/status), there is an active issue impacting multiple AWS services (Glue, Resource Groups, Service Catalog, EC2, and RDS) Our team is closely monitoring the situation and coordinating with AWS to track the resolution progress. We will continue to provide updates as new information becomes available or once normal service is fully restored.

Hi Team , As of Mar 01, 5:19 AM PST, AWS is investigating connectivity and power issues impacting APIs and instances in a single Availability Zone (mec1-az2) within the ME-CENTRAL-1 region. The issue is due to a localized power disruption. Existing instances within mec1-az2 are affected. Other AWS services may also experience increased error rates and latency for workflows operating in this Availability Zone. AWS is actively working to reroute traffic away from the impacted AZ. Instances running in other Availability Zones remain unaffected. Customers are advised to utilize alternate AZs for new launches, as RunInstances operations in the remaining AZs are expected to succeed. We are continuing to monitor the situation and will provide further updates as available.

We are continuing to work on a fix for this issue.

Hi All, We are actively working internally in coordination with AWS on the ongoing recovery efforts. The next update is expected in approximately 30 minutes. We will continue to share further updates as progress is made.

Hi Team, AWS is currently working on recovery as per the latest update on the AWS Health Dashboard (https://health.aws.amazon.com/health/status) . While we have redundancy across Availability Zones, a few services are experiencing cross-zone impact from the AWS side. We are closely coordinating with AWS to monitor the situation and minimize impact. Further updates will be shared as they become available.

Hi Team, As per the latest update from AWS, the primary impact remains on mec1-az2. However, networking and API-related errors from AWS are affecting functionality across multiple Availability Zones within the region, impacting our major services. We have attempted to migrate services across multiple Availability Zones in the UAE region as an alternative approach suggested by AWS however, API errors are still being observed. Our team is currently on a live call with the AWS team to explore alternative mitigation approaches and closely monitor error rates. We will share another update shortly if any improvement is observed.

Hi Team, This is to inform you that the services impacted earlier are now partially restored, and we are observing improved stability across the environment. Error rates have reduced significantly, and most functionalities are recovering. However, we continue to monitor the platform closely as recovery activities are still in progress to ensure complete stability. Our team remains engaged with the cloud provider and will share further updates once full restoration is confirmed. Thank you for your continued patience and support.

Hi Team, We are currently experiencing an issue where posts are failing with error "PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target" Bitly Shortner Service is failing because of SSL certificate issue. Our team is actively investigating the issue and working to resolve it as quickly as possible. Meanwhile as a workaround we request you to please remove Bitly URL shortner from account level and Quick publish window. We apologize for any inconvenience this may cause and appreciate your patience.

Hi Team, The issue related to the Bitly URL Shortener service has now been resolved. Earlier, post publishing was failing with the error: "PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target." This occurred due to an SSL certificate validation issue while connecting to the Bitly service. You may re-enable the Bitly URL shortener at the account level and in the Quick Publish window if it was previously disabled as a workaround. We apologize for the inconvenience caused and thank you for your patience.

Hi Team, We would like to provide an update regarding the earlier spike in IVR failures and Live Chat errors. We are pleased to inform you that the error rates are steadily decreasing, and services are gradually recovering. Our teams continue to closely monitor the systems and are actively working to ensure full stability as soon as possible. At this time, performance is improving, and we will continue to share updates until the issue is fully resolved. If you encounter any further issues related to this incident, please contact the Sprinklr Support Team. Thank you

Hi Team, We are writing to proactively inform you that our monitoring system has identified alerts related to an assignment issue. Our Engineering team is actively investigating the matter and working towards resolution. We will keep you informed as soon as we have further updates. Please rest assured that we are closely monitoring the situation.

Hi Team, We would like to proactively inform you that our monitoring systems have detected intermittent slowness on the Prod15 environment. Our engineering teams are currently investigating the underlying cause and working on mitigation with the highest priority. At this time, you may experience some latency in platform performance or UI responsiveness intermittently. We are closely monitoring the situation and will share further updates as we make progress. Please rest assured that restoring optimal performance remains our top priority. If you have any questions or require additional assistance, please feel free to reach out to Sprinklr

Hi Team, We would like to share an update regarding the intermittent slowness observed on the Prod15 environment. Our monitoring indicates that the platform is currently recovering, and performance has shown noticeable improvement. The engineering teams continue to closely monitor the environment and are working to ensure full stability. We will provide a confirmation update once the issue is completely resolved and normal performance is fully restored. Thank you for your patience and understanding. If you have any questions or continue to experience any issues, please feel free to reach out to Sprinklr Support.