Sprinklr Outage History

Started May 19, 2026, 11:01 AM UTC· resolved May 19, 2026, 11:36 AM UTC

1. investigating May 19, 2026, 11:01 AM UTC

   Hi Team, We are currently seeing impact across Voice services. Our engineering team is actively working on the issue, and we will provide updates as more information becomes available.

2. resolved May 19, 2026, 11:36 AM UTC

   Hi Team, The issue impacting Voice services has now been resolved, and services are operating normally at this time. We will continue to monitor the environment closely to ensure stability. Thank you for your patience and understanding.

Read the full incident report →

Started May 19, 2026, 04:38 AM UTC· resolved May 19, 2026, 05:01 AM UTC

1. investigating May 19, 2026, 04:38 AM UTC

   Hi Team, This is to inform you that we are currently observing issues on Whatsapp chatbot for prod4. We have raised this with Meta and shall keep you posted as soon as we have further updates.

2. resolved May 19, 2026, 05:01 AM UTC

   Hi Team, Our engineering team has confirmed that the issue with the WhatsApp chatbot for prod4 has now been resolved. Services are currently operating normally. Thank you for your patience. Please reach out to Sprinklr Support in case of any queries.

Read the full incident report →

Started May 11, 2026, 10:57 AM UTC· resolved May 11, 2026, 12:00 PM UTC

1. investigating May 11, 2026, 10:57 AM UTC

   Hi Team, This is to inform you that we are observing issues with respect to the Sprinklr platform for prod4 environment. We are checking this with our engineering team and shall keep you posted as soon as we have further updates.

2. monitoring May 11, 2026, 11:35 AM UTC

   Hi Team, This is to inform you that the platform is currently up and accessible. The backend services are currently being checked by our engineering team. We shall keep you posted as soon as we have further updates.

3. resolved May 11, 2026, 12:00 PM UTC

   Hi Team, This is to inform you that the issue with the platform is resolved. The platform and backend services are stable and should be functioning as expected. Thank you for your patience and understanding. Please feel free to reach out to Sprinklr Support in case of any queries

Read the full incident report →

Started May 08, 2026, 05:28 AM UTC· resolved May 11, 2026, 04:31 PM UTC

1. identified May 08, 2026, 05:28 AM UTC

   Hi Team, We would like to inform you that our voice provider, Twilio is currently investigating an issue causing degradation in voice services. Twilio has also acknowledged this on their status page: https://status.twilio.com/ . We will keep you updated as soon as we have further information. We apologize for the inconvenience caused. If you continue to face issues, please report them to Sprinklr Support. Please ignore this notification if you are not using the above voice provider.

2. identified May 08, 2026, 05:56 AM UTC

   Hi Everyone, We would like to share an update regarding AWS US East1 services. At this time, there is no impact observed, and all services are functioning as expected. However, we are closely monitoring the situation as a precautionary measure. We are aware of an ongoing issue impacting AWS US-East-1 services, as reflected on their public status page. This is currently being tracked at the provider level. We will continue to monitor the AWS incident and provide updates if there are any changes impacting Sprinklr services. AWS Status Page: https://health.aws.amazon.com/health/status Our teams are actively monitoring system performance and alerts to ensure any potential impact is identified at the earliest. We will continue to share updates as more information becomes available.

3. monitoring May 08, 2026, 06:35 AM UTC

   Hi Everyone, We would like to share an update regarding AWS US-East-1 services. AWS is showing signs of recovery, and services are stabilizing. At this time, there is no impact observed on Sprinklr services, and all systems continue to function as expected. We are continuing to monitor the situation closely and will keep you informed of any further developments. AWS Status Page: https://health.aws.amazon.com/health/status

4. monitoring May 08, 2026, 04:47 PM UTC

   This is to share an update regarding AWS US-East-1 services. As per the latest update from the AWS teams, the issue has been resolved and the services are now operating normally. The ongoing restoration activities are continuing separately. We are continuing to monitor the situation closely and will keep you informed of any further developments. AWS Status Page: https://health.aws.amazon.com/health/status

5. resolved May 11, 2026, 04:31 PM UTC

   Hi Everyone, As per the latest update from AWS, the issue on the AWS side has now been fully resolved and services in the AWS US-East-1 region have stabilized. At this time, no impact has been observed on Sprinklr services, and all systems are functioning normally. Our teams continuously monitored the environment throughout the event and no further concerns have been identified. We will continue monitoring to ensure ongoing stability. AWS Status Page: https://health.aws.amazon.com/health/status Thank you for your patience and understanding.

Read the full incident report →

Started May 06, 2026, 10:49 AM UTC· resolved May 06, 2026, 11:29 AM UTC

1. identified May 06, 2026, 10:49 AM UTC

   Hi Team We would like to inform you that we are currently observing an increase in webhook activity along with intermittent API failures on prod19. Our engineering team is actively investigating the issue to determine the root cause. We will continue to monitor the situation closely and provide updates as more information becomes available. We appreciate your patience and understanding.

2. resolved May 06, 2026, 11:29 AM UTC

   Hi Team, We would like to inform you that the issue has now been resolved. The increase in webhook activity along with intermittent API failures on prod19 has been addressed, and the system is now stable. Our engineering team has implemented the necessary fixes and will continue to monitor closely to ensure continued stability. Thank you for your patience and understanding.

Read the full incident report →

Started Apr 23, 2026, 12:18 PM UTC· resolved Apr 23, 2026, 02:50 PM UTC

1. investigating Apr 23, 2026, 12:18 PM UTC

   Hi team , We are currently seeing impact across multiple services related to data retrieval and updates. Our engineering team is actively working on the issue, and we will provide updates as more information becomes available.

2. investigating Apr 23, 2026, 01:59 PM UTC

   Hi Team, Our teams are actively investigating issues and are working to resolve them as quickly as possible. We will provide further updates as soon as they become available.

3. resolved Apr 23, 2026, 02:50 PM UTC

   Hi Team, The issue impacting data retrieval and updates across multiple services has now been fully resolved, and all services are operating normally. Our engineering team has addressed the problem, and systems are functioning as expected. We will continue to monitor to ensure stability. If you notice any further issues or need assistance, please feel free to reach out to our support team.

Read the full incident report →

Started Apr 20, 2026, 06:03 PM UTC· resolved Apr 27, 2026, 02:37 PM UTC

1. monitoring Apr 20, 2026, 06:03 PM UTC

   We are currently observing increased traffic on Twitter, which may result in the following message for some users: "We are currently experiencing a disruption with this channel API. Please re-try in a few minutes. If this error persists, please contact [email protected]" This indicates that the service is temporarily handling a high volume of requests. Users may experience delays or intermittent access. We recommend retrying after a short period. We are monitoring the situation and will provide updates as needed. Thank you.

2. resolved Apr 27, 2026, 02:37 PM UTC

   The increased traffic on Twitter that was causing intermittent API errors has now subsided. All services are operating normally. Thank you for your patience.

Read the full incident report →

Started Apr 13, 2026, 07:28 PM UTC· resolved Apr 13, 2026, 08:25 PM UTC

1. investigating Apr 13, 2026, 07:28 PM UTC

   We are currently investigating an issue in the production environment where survey responses are not being captured in Sprinklr as expected, even though customers have completed the surveys. Further analysis indicates that responses are being recorded but are getting updated with a delay We are actively working with the Engineering team on priority, We will continue to monitor the situation closely and share further updates as more information becomes available.

2. resolved Apr 13, 2026, 08:25 PM UTC

   The issue observed in the production environment, where survey responses were not being captured in Sprinklr despite customers completing them, has now been resolved. Upon investigation, it was identified that the responses were being recorded but were updated in the system with a delay. This delay has now been addressed in coordination with the Engineering team. Survey responses are now being captured and reflected correctly in the backend and associated cases. We will continue to monitor the system to ensure stability.

Read the full incident report →

Started Apr 09, 2026, 06:11 AM UTC· resolved Apr 20, 2026, 05:54 AM UTC

1. investigating Apr 09, 2026, 06:11 AM UTC

   Hi Team, We would like to inform you of an ongoing issue impacting reporting data for X ad accounts within Sprinklr. Issue : Following a recent ads platform revamp by X, we are observing instances where reporting data is not populating as expected across certain accounts. As per the latest update from X, while data continues to be stored on their end, it is currently not accessible via their API or native Ads Manager. As a result, metrics for the period following the migration are not being reflected in Sprinklr at this time. Next Steps : We are actively engaged with X to monitor the situation and drive resolution. We will continue to track progress closely and share updates as soon as data accessibility is restored. We understand the impact this may have on your reporting workflows and sincerely appreciate your patience and understanding while this issue is being addressed. Thank you.

2. investigating Apr 09, 2026, 06:22 AM UTC

   We are continuing to investigate this issue.

3. investigating Apr 09, 2026, 06:26 AM UTC

   We are continuing to investigate this issue.

4. resolved Apr 20, 2026, 05:54 AM UTC

   The reporting data issue impacting X ad accounts within Sprinklr has now been resolved. Reporting metrics are now populating in Sprinklr as expected. If you observe any discrepancies, please reach out to Sprinklr Support. We sincerely appreciate your patience and understanding while this issue was being addressed. Thank you.

Read the full incident report →

Started Apr 08, 2026, 03:01 AM UTC· resolved Apr 17, 2026, 06:44 AM UTC

1. identified Apr 08, 2026, 03:01 AM UTC

   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.

2. identified Apr 08, 2026, 12:09 PM UTC

   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.

3. resolved Apr 17, 2026, 06:44 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 06, 2026, 11:23 AM UTC· resolved Apr 07, 2026, 03:02 AM UTC

1. investigating Apr 06, 2026, 11:23 AM UTC

   This is to inform you that we have observed issues with listening data being grabbed into Sprinklr. Our engineering team is checking this and we will keep you informed as soon as more information becomes available. Thank you for your patience and understanding.

2. resolved Apr 07, 2026, 03:02 AM UTC

   We are pleased to inform you that the issue impacting the ingestion of listening data into Sprinklr has been resolved. Listening data is now being processed as expected. If you have any questions or need further support, please feel free to reach out to Sprinklr Support. Thank you for your patience.

Read the full incident report →

Started Apr 01, 2026, 07:32 AM UTC· resolved Apr 01, 2026, 08:07 AM UTC

1. identified Apr 01, 2026, 07:32 AM UTC

   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.

2. resolved Apr 01, 2026, 08:07 AM UTC

   We’re happy to inform you that the issue observed with the URL services in Prod3 has been successfully resolved, and services are now functioning as expected. Thank you for your patience and cooperation. Please let us know if you experience any further issues.

Read the full incident report →

Started Mar 30, 2026, 10:25 AM UTC· resolved Mar 30, 2026, 10:36 AM UTC

1. investigating Mar 30, 2026, 10:25 AM UTC

   We are currently experiencing an issue affecting the PROD21 environment. Our engineering team has identified the problem and is actively investigating. Some services may be unavailable or degraded at this time. We will provide further updates as soon as more information becomes available.

2. resolved Mar 30, 2026, 10:36 AM UTC

   We’re happy to inform you that the issue affecting the Sprinklr platform on the PROD21 environment has been successfully resolved. Our engineering team has addressed the issue, and all services are now functioning as expected. Thank you for your patience and cooperation. Please let us know if you experience any further issues.

Read the full incident report →

Started Mar 16, 2026, 06:18 PM UTC· resolved Mar 17, 2026, 08:28 AM UTC

1. investigating Mar 16, 2026, 06:18 PM UTC

   We are currently experiencing an issue where cases are not loading properly, adherence metrics are displaying incorrect values, and some bots are responding slower than expected. This may impact users when accessing cases and monitoring adherence data. Our technical team is actively investigating the root cause and working to restore normal system performance as quickly as possible.

2. resolved Mar 17, 2026, 08:28 AM UTC

   The issue where cases were not loading properly, adherence metrics were displaying incorrect values, and some bots were responding slower than expected has been resolved. System performance has returned to normal, and users should no longer experience any impact while accessing cases or monitoring adherence data. Our team will continue to monitor the platform closely to ensure stability. If you have any questions or require further assistance, please feel free to reach out to Sprinklr Support.

Read the full incident report →

Started Mar 15, 2026, 05:22 AM UTC· resolved Mar 15, 2026, 06:58 AM UTC

1. investigating Mar 15, 2026, 05:22 AM UTC

   Hi Team, We are writing to proactively keep you informed that our monitoring system has identified a few alerts indicating a delay in case reporting sync. We are diligently coordinating with our internal team and will keep you informed as soon as we have further updates. However, rest assured we are continuing to monitor the situation. If you have any questions or need further assistance, please don't hesitate to reach out to Sprinklr Support. Thank you.

2. resolved Mar 15, 2026, 06:58 AM UTC

   Hi Team, We would like to inform you that the issue related to the delay in case reporting sync has now been resolved, and recovery has been observed. Our team will continue to monitor the system to ensure stability. 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. Thank you.

Read the full incident report →

Started Mar 12, 2026, 03:35 PM UTC· resolved Mar 16, 2026, 11:54 AM UTC

1. investigating Mar 12, 2026, 03:35 PM UTC

   We are observing publishing failures for video posts. Posts are getting stuck in the "processing by channel" state and eventually failing with the error "There was a problem uploading your video file." The team is currently investigating the issue with the channel and will provide updates as soon as more information is available.

2. resolved Mar 16, 2026, 11:54 AM UTC

   Our engineering team and channel team have confirmed that the issue with video posts getting stuck in the "processing by channel" state has been resolved. The upload process is now functioning as expected, and videos are being processed and published without any issue. If you encounter any further issues, please feel free to reach out to Sprinklr Support.

Read the full incident report →

Started Mar 02, 2026, 05:32 AM UTC· resolved Mar 02, 2026, 05:53 AM UTC

1. investigating Mar 02, 2026, 05:32 AM UTC

   Hi Team, We are currently observing that the Prod 15 platform is down and services are not accessible. The team has started investigating the issue on priority and is actively checking all related components to identify the root cause. We are working to restore the platform as quickly as possible. We will share the next update shortly or once services are fully restored. Appreciate your patience and support.

2. investigating Mar 02, 2026, 05:52 AM UTC

   Hi Team, The issue impacting the Prod 15 platform has now been fully resolved. The platform is up and running, and all services have been restored successfully. Necessary validations and health checks have been completed to ensure system stability. At this time, no further impact is observed. We will continue to closely monitor the platform for some time to ensure consistent performance and prevent any recurrence. Thank you for your patience and support throughout this incident.

3. resolved Mar 02, 2026, 05:53 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 01, 2026, 09:39 PM UTC· resolved Jul 16, 2026, 10:29 AM UTC

1. identified Mar 01, 2026, 09:39 PM UTC

   We would like to inform you that AWS is currently experiencing GPU capacity limitations. AWS is actively working to arrange additional GPU capacity. In parallel, our team is evaluating alternate CPU-based options to mitigate the impact wherever feasible.Due to the limited GPU availability, the following key services are impacted: VoiceBots (LiveChat) RTS (Transcript Services) As a result, requests that require GPU processing may not be handled as expected and could be deflected to human agents, potentially leading to increased queue volumes. Our team continues to closely coordinate with AWS and monitor the situation. We will share further updates as soon as additional capacity is provisioned and service stability improves. Thank you for your continued patience and support.

2. identified Mar 02, 2026, 05:58 AM UTC

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

3. identified Mar 02, 2026, 07:14 AM UTC

   As a follow-up to our previous communication regarding AWS instability, we would like to provide an additional update. AWS region is impacted. This situation is currently impacting multiple services within the Middle East region. We remain in close coordination with AWS and are closely monitoring the situation. Further updates will be shared as soon as additional capacity is made available and service stability improves. Thank you for your continued patience and understanding.

4. identified Mar 02, 2026, 10:35 AM UTC

   AWS data center supporting your environment is currently experiencing a power outage, resulting in service impact within the region. AWS is actively working on the issue, and we are currently awaiting further updates from their team. Please be assured that we are closely monitoring the situation and will share updates as soon as more information becomes available Thank you for your understanding.

5. identified Mar 02, 2026, 10:46 AM UTC

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

6. identified Mar 02, 2026, 10:47 AM UTC

   AWS data center supporting your environment is currently experiencing a power outage, resulting in service impact within the region. AWS is actively working on the issue, and we are currently awaiting further updates from their team. Please be assured that we are closely monitoring the situation and will share updates as soon as more information becomes available

7. identified Mar 02, 2026, 05:14 PM UTC

   We hope you and your loved ones remain safe and well during this difficult time. We, like many other vendors in the region, are working hard to assess impact and restore platform availability as quickly as possible. We continue to monitor the situation closely and will share further updates as soon as we are able to take concrete action or have meaningful progress to report. We understand the importance of platform reliability to your business and appreciate your patience and understanding as we work through this technical challenge. Thank you for your continued partnership.

8. identified Mar 03, 2026, 12:18 PM UTC

   We are continuing to actively manage the ongoing AWS outage impacting the UAE region. Our incident response and crisis management teams remain fully engaged, and we are working closely with AWS while validating recovery and continuity options. At this stage, conditions remain fluid and dependent on third‑party infrastructure availability. Our priority is to restore service safely while preserving data integrity and avoiding unnecessary risk. We will provide further updates as soon as there is confirmed progress or a change in status. Thank you for your patience and understanding. We remain fully committed to keeping you informed and supporting you through this incident.

9. identified Mar 04, 2026, 09:39 PM UTC

   To our valued customer, We hope you and your teams are safe and doing as well as possible under the circumstances. We fully recognize how difficult the situation on the ground is, with the level of uncertainty and disruption your community is experiencing. Our thoughts are with you, and we appreciate the resilience you and your teams continue to show. We are writing to update you on the service instability affecting the infrastructure supporting your environment on our platform. As you are aware, the AWS data centers hosting your environment have experienced significant disruption in recent days following the military strikes across the region. These extraordinary events have resulted in outages impacting the availability and reliability of services across multiple global software providers, including ours. To safeguard the ongoing availability and integrity of your data, we have taken immediate and necessary actions to initiate migration of your data to AWS Ireland, consistent with guidance provided by AWS. This migration is well underway and remains in progress to reduce the risk of permanent data loss. We are encouraged by early progress. Please know that throughout this temporary migration our operational practices and commitments related to security, privacy, and data protection remain fully in place and unchanged. We remain committed to the protection and security of your data. Your account team will be reaching out soon with additional information and next steps. In the meantime, if you have any questions or concerns, please do not hesitate to reach out. Thank you for your understanding and partnership during this evolving situation. We are committed to keeping you informed and supported.

10. identified Mar 11, 2026, 09:15 AM UTC

    Platform Migration Progress and Service Availability Following the AWS outage in the UAE region, Sprinklr has successfully migrated the majority of customer environments and data to our AWS infrastructure in Ireland. Historical and recent data for these environments has been restored and validated. Current Status: Platform services for all migrated environments are operating normally. A limited number of features remain in restoration and may show intermittent limitations. All restored data remains protected under existing contractual, technical, and organizational safeguards, including in line with our security and privacy commitments to you . No changes have been made to data access controls, security measures, or sub‑processor arrangements. We appreciate your patience and partnership as we work to complete the remaining restoration steps. Our teams remain fully engaged, and we will continue to post updates here as status changes. For assistance, please contact [email protected].

11. resolved Jul 16, 2026, 10:29 AM UTC

    This incident has been resolved.

Read the full incident report →

Started Mar 01, 2026, 01:17 PM UTC· resolved Mar 01, 2026, 07:44 PM UTC

1. identified Mar 01, 2026, 01:17 PM UTC

   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.

2. identified Mar 01, 2026, 02:00 PM UTC

   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.

3. identified Mar 01, 2026, 03:04 PM UTC

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

4. identified Mar 01, 2026, 03:14 PM UTC

   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.

5. identified Mar 01, 2026, 04:10 PM UTC

   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.

6. identified Mar 01, 2026, 05:11 PM UTC

   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.

7. identified Mar 01, 2026, 07:03 PM UTC

   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.

8. resolved Mar 01, 2026, 07:44 PM UTC

   Hi Team, The issue has been resolved and services are stable. However, one Availability Zone (AZ) on the AWS side remains down. We are actively monitoring the situation and will share updates if any impact is observed.

Read the full incident report →

Started Feb 26, 2026, 08:28 AM UTC· resolved Mar 02, 2026, 08:01 AM UTC

1. investigating Feb 26, 2026, 08:28 AM UTC

   This is to inform you that we are observing issues with Instagram Reel publishing, where posts are either failing to publish or experiencing significant delays of up to 30 minutes. Our engineering team is checking this the channel team and we shall keep you posted as soon as we have further updates. Below is the facebook community link about the issue: https://developers.facebook.com/community/threads/1970836260493737/

2. resolved Mar 02, 2026, 08:01 AM UTC

   Hi Team, We’re pleased to inform you that the issue affecting Instagram Reel publishing has now been resolved. Posts should publish as expected without delays. Thank you for your patience while we worked through this. Please let us know if you notice any further issues.

Read the full incident report →

Started Feb 23, 2026, 11:20 PM UTC· resolved Mar 12, 2026, 03:57 PM UTC

1. identified Feb 23, 2026, 11:20 PM UTC

   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.

2. identified Mar 12, 2026, 03:56 PM UTC

   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.

3. resolved Mar 12, 2026, 03:57 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 21, 2026, 06:47 AM UTC· resolved Feb 21, 2026, 08:30 AM UTC

1. investigating Feb 21, 2026, 06:47 AM UTC

   Hi Team, We are writing to proactively keep you informed that our monitoring system has identified a few alerts indicating a spike in IVR failures and Live Chat errors. We are diligently coordinating with our internal teams and will keep you informed as soon as we have further updates. Please rest assured that we are closely monitoring the situation. If you encounter any further issues related to this incident, please contact the Sprinklr Support Team. Thank you.

2. identified Feb 21, 2026, 06:58 AM UTC

   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

3. identified Feb 21, 2026, 07:36 AM UTC

   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.

4. resolved Feb 21, 2026, 08:30 AM UTC

   Hi Team, We would like to inform you that the previously reported brief disruption affecting Assignment, Live Chat, and Voice services has now been resolved. Our Engineering team has implemented corrective measures, and all services are currently operating normally. We are continuing to closely monitor the systems to ensure stability and prevent any recurrence. We sincerely apologize for any inconvenience this may have caused and appreciate your patience and understanding throughout this matter. Thank you

Read the full incident report →

Started Feb 18, 2026, 11:58 AM UTC· resolved Feb 18, 2026, 02:33 PM UTC

1. investigating Feb 18, 2026, 11:58 AM UTC

   We are currently observing failures impacting inbound and outbound calls. Our internal team is actively investigating the issue and working to identify the root cause. We will provide further updates as soon as more information becomes available. Thank you for your patience.

2. investigating Feb 18, 2026, 12:00 PM UTC

   We are continuing to investigate this issue.

3. monitoring Feb 18, 2026, 12:18 PM UTC

   Hi Team, This is an interim update regarding the previously reported voice operations issue. A fix has been applied, and services are expected to be restored shortly. We are continuing to monitor the situation closely and are coordinating with the voice vendor to ensure full service stability. We will share further updates as they become available. Please feel free to reach out to Sprinklr Support if you have any questions or need assistance.

4. investigating Feb 18, 2026, 12:18 PM UTC

   We are continuing to investigate this issue.

5. resolved Feb 18, 2026, 02:33 PM UTC

   The inbound / outbound call issue observed earlier has now been resolved, and services have stabilized. We will continue to monitor the situation closely to ensure ongoing stability. We apologize for any inconvenience caused and appreciate your patience while we addressed the matter. If you have any questions or need further assistance, please feel free to reach out to Sprinklr Support.

Read the full incident report →

Started Feb 12, 2026, 03:54 AM UTC· resolved Feb 12, 2026, 05:25 AM UTC

1. investigating Feb 12, 2026, 03:54 AM UTC

   Hi Team, We are currently experiencing a lag in listening data, which is affecting data retrieval across multiple sources. Our team is actively working to resolve the issue and restore normal operations as quickly as possible. We will provide updates as soon as the situation is resolved. In the meantime, please be assured that we are closely monitoring the situation to mitigate any potential impact. Thank you for your understanding.

2. resolved Feb 12, 2026, 05:25 AM UTC

   Hi team, The issue with the lag in listening data has now been resolved. Data retrieval across all sources is functioning normally. We apologize for any inconvenience caused and appreciate your patience while we addressed the matter. However, we will continue to closely monitor the situation to ensure continued stability. If you have any questions or need further assistance, please feel free to reach out to Sprinklr Support. Thank you for your understanding.

Read the full incident report →

Started Feb 09, 2026, 09:56 AM UTC· resolved Feb 09, 2026, 11:08 AM UTC

1. identified Feb 09, 2026, 09:56 AM UTC

   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

2. identified Feb 09, 2026, 10:36 AM UTC

   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.

3. resolved Feb 09, 2026, 11:08 AM UTC

   Hi team, We are pleased to inform you that the issue with Prod15 Site has been resolved. After verification, we have confirmed that all voice and non voice services are working as expected. However, we will continue to closely monitor the situation to ensure continued stability. Thank you for your patience throughout this process. If you experience any further issues or have additional questions, please do not hesitate to reach out.

Read the full incident report →