Sprinklr Outage History

Started Jan 29, 2026, 10:38 AM UTC· resolved Jan 29, 2026, 10:57 AM UTC

1. identified Jan 29, 2026, 10:38 AM UTC

   Hi Team, We are reaching out to inform you that Prod3 environment is inaccessible due to an outage identified. We are checking this with our team on highest priority and shall keep you posted as soon as more information becomes available.

2. resolved Jan 29, 2026, 10:57 AM UTC

   Hi Team, We are pleased to inform you that the issue impacting the Prod3 environment has now been resolved. The site is up and functioning as expected. Our teams will continue to monitor the environment to ensure stability. Please let us know if you observe any further issues or need additional assistance. Thank you for your patience and cooperation.

Read the full incident report →

Started Jan 28, 2026, 02:02 PM UTC· resolved Jan 28, 2026, 05:48 PM UTC

1. identified Jan 28, 2026, 02:02 PM UTC

   Hi Team, We wanted to inform you that the Prod19 community site is currently experiencing a temporary service disruption, resulting intermittent page unavailability.Our engineering teams are actively investigating the issue and working to restore full access as quickly as possible. At this time, there is no action required from your side. We appreciate your patience and will keep you informed with timely updates as progress is made. Please feel free to reach out if you have any questions or notice additional issues.

2. identified Jan 28, 2026, 04:00 PM UTC

   Hi team, We are pleased to inform you that the issue with Prod19 Community Site has been resolved. After verification, we have confirmed that 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.

3. resolved Jan 28, 2026, 05:48 PM UTC

   Hi team, We are pleased to inform you that the issue with Prod19 Community Site has been resolved. After verification, we have confirmed that 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 →

Started Jan 27, 2026, 11:37 AM UTC· resolved Jan 28, 2026, 09:12 AM UTC

1. investigating Jan 27, 2026, 11:37 AM UTC

   Hi Team, We would like to inform you that Azure has reported an issue impacting the Azure OpenAI Service in the Sweden Central region. Impact: Starting at 09:00 UTC on 27 January 2026, customers may experience intermittent availability issues. Current Status: Azure is actively investigating the issue. Our team is closely monitoring the situation and coordinating with Azure to track progress and restoration. You can also follow updates directly on the Azure status page: https://azure.status.microsoft/en-gb/status Note : This update is only applicable if you are using Azure OpenAI services. You may ignore this message if Azure services are not in use on your account. We will share further updates as soon as more information becomes available. Thank you for your patience and understanding.

2. investigating Jan 27, 2026, 11:49 AM UTC

   We are continuing to investigate this issue.

3. resolved Jan 28, 2026, 09:12 AM UTC

   Hi team, We are pleased to inform you that the issue with Azure OpenAI Service has been resolved. After verification, we have confirmed that services are working as expected. However, we will continue to closely monitor the situation to ensure continued stability. You can also follow updates directly on the Azure status page: https://azure.status.microsoft/en-gb/status Note : This update is only applicable if you are using Azure OpenAI services. You may ignore this message if Azure services are not in use on your account. 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 →

Started Jan 20, 2026, 01:42 PM UTC· resolved Jan 27, 2026, 09:32 AM UTC

1. investigating Jan 20, 2026, 01:42 PM UTC

   We are reaching out to inform you that we are currently experiencing an issue where images uploaded by customers are not visible within Sprinklr. This may impact your chatbot workflows, depending on your usage of customer-uploaded images. Our teams are actively investigating the issue and are working closely with Meta to identify the root cause and restore full functionality at the earliest. We will keep you informed and share further updates as more information becomes available. Thank you for your patience.

2. investigating Jan 20, 2026, 01:53 PM UTC

   We are continuing to investigate this issue.

3. investigating Jan 20, 2026, 02:44 PM UTC

   This is a follow-up regarding the ongoing issue where all media files uploaded by customers are not currently visible within Sprinklr. The issue may continue to impact chatbot workflows and any use cases dependent on customer-uploaded media. Our teams remain actively engaged and are working closely with Meta to resolve this at the earliest. We will continue to keep you informed as progress is made. Thank you for your continued patience and cooperation.

4. resolved Jan 27, 2026, 09:32 AM UTC

   We want to inform you that, as per Meta, the issue affecting the visibility of customer-uploaded images within Sprinklr has now been resolved. Meta has confirmed that the underlying problem on their platform has been fixed, and customer-uploaded images are now displaying correctly across Sprinklr. If you encounter any further issues related to the incident, please feel free to reach out to Sprinklr support.

Read the full incident report →

Started Jan 20, 2026, 12:13 PM UTC· resolved Jan 24, 2026, 07:23 AM UTC

1. investigating Jan 20, 2026, 12:13 PM UTC

   This is to inform you that we have observed an issue on the platform where Twitter videos are not playing within Sprinklr. Our teams are actively monitoring the situation and coordinating efforts to resolve the issue. We will keep you informed as soon as we have further updates.

2. investigating Jan 23, 2026, 08:05 AM UTC

   Hi Team, We are actively exploring workarounds and solutions in collaboration with X. A potential workaround has been identified and is currently under validation. Once validated, we will proceed with implementation at the earliest. We regret any inconvenience caused and assure you that we are working diligently to resolve this issue as soon as possible. Thank you for your patience and understanding.

3. resolved Jan 24, 2026, 07:23 AM UTC

   Hi team, We are pleased to inform you that the issue with Twitter Video playback within Sprinklr has been resolved. After verification, we have confirmed that videos should now be playing 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. Thank you,

Read the full incident report →

Started Jan 16, 2026, 03:52 PM UTC· resolved Jan 18, 2026, 05:30 AM UTC

1. investigating Jan 16, 2026, 03:52 PM UTC

   Hi Team, We would like to inform you that we are currently observing a spike in errors from X (formerly Twitter) APIs, which may impact publishing, message grabbing, reporting and other parts of platform . Our team is actively monitoring the situation and tracking updates from X. We will keep you informed as soon as we have further information or a resolution. Thank you for your patience and understanding. Please feel free to reach out to Sprinklr Support if you have any questions.

2. resolved Jan 18, 2026, 05:30 AM UTC

   Hi Team, We’re pleased to inform that the issue related to elevated error rates from X (formerly Twitter) APIs has been resolved. All services have stabilized, and customers should no longer experience disruptions to publishing, message ingestion, reporting, or other platform capabilities. Our teams have been closely monitoring performance to ensure everything is functioning smoothly. We appreciate your patience while this was being addressed and remain committed to providing a reliable experience. If you have any questions or continue to experience any issues, please feel free to reach out to Sprinklr Support. Thank you

Read the full incident report →

Started Jan 14, 2026, 08:41 AM UTC· resolved Jan 15, 2026, 04:11 AM UTC

1. identified Jan 14, 2026, 08:41 AM UTC

   Hi Team, We are currently observing an impact on Engagement, Compliance, and Web Share metrics across all partners. Metrics availability and processing may be delayed at this time. The issue is due to an ongoing Hardware Issue, and we are closely monitoring the progress. We will provide an update as soon as the recovery is completed or if there is any change in the situation. Thank you for your patience.

2. identified Jan 14, 2026, 08:42 AM UTC

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

3. resolved Jan 15, 2026, 04:11 AM UTC

   Hi Team, The issue impacting Engagement, Compliance, and Web Share metrics across all partners has been resolved. Metrics are now processing normally. Thank you for your patience.

Read the full incident report →

Started Jan 12, 2026, 09:47 AM UTC· resolved Jan 12, 2026, 10:53 AM UTC

1. investigating Jan 12, 2026, 09:47 AM UTC

   Hi Team, This is to inform you that our monitoring system has identified some sporadic disruptions in Voice operations (drop in incoming call count), which may or may not impact you. We are checking with our Voice Provider on utmost priority and shall keep posted as soon as we have further update on this.

2. investigating Jan 12, 2026, 09:57 AM UTC

   Hi Team, We would like to inform you that our team has observed a decrease in the volume of incoming calls. Please be assured that we are actively investigating this internally. Our initial findings indicate that the issue is on the voice provider’s end (SignalWire). We are currently in touch with their team to review this further and will keep you informed as soon as we have any updates. Please feel free to reach out if you have any questions in the meantime.

3. resolved Jan 12, 2026, 10:53 AM UTC

   Hi Team, This is to inform you that the earlier sporadic disruption observed in voice operations, including a brief drop in incoming call count, has now been resolved. Our teams have completed the necessary checks and are continuing to monitor the platform closely to ensure stable operations. If you notice any further irregularities or need assistance, please feel free to reach out to Sprinklr Support. Thank you for your patience and cooperation.

Read the full incident report →

Started Dec 22, 2025, 10:08 AM UTC· resolved Dec 24, 2025, 11:15 AM UTC

1. investigating Dec 22, 2025, 10:08 AM UTC

   Hi Team, The intermittent errors with the AI Chatbot have resurfaced, and we are currently investigating the issue again. Initial findings indicate it may be related to an OpenAI dependency, and our team is actively checking this with Azure for further validation. We will share updates as soon as we have more information. Please feel free to reach out if you have any questions in the meantime. Thank you for your patience.

2. monitoring Dec 23, 2025, 07:18 AM UTC

   The issue has subsided in the short term, and the service is currently operating as expected. That said, there may still be occasional intermittent behavior while we continue to monitor the system closely. As a next step, we are actively working with Azure to secure higher capacity to completely stabilize the service and prevent similar issues moving forward in this busy period. We appreciate your continued patience and will provide additional updates as progress is made. Please feel free to reach out if you have any questions or notice any ongoing issues.

3. monitoring Dec 24, 2025, 08:02 AM UTC

   The service is currently operating as expected; however, intermittent behavior may still occur while we continue to monitor the system closely. Our team is actively working with Azure to fully stabilize the service and prevent further disruptions. We appreciate your patience and will provide additional updates as progress is made. Please reach out if you experience any ongoing issues.

4. resolved Dec 24, 2025, 11:15 AM UTC

   Hi Team, We would like to confirm that the AI Chatbot service is now operating as expected and the reported issue has been resolved. At this time, no further disruptions are observed. We are continuing to closely monitor the system to ensure a seamless experience. In parallel, our team is actively working with our cloud provider (Azure) to complete a detailed Root Cause Analysis (RCA) related to the intermittent behavior observed earlier. However, rest assured we will continue to monitor the situation. Please feel free to reach out if you have any questions. Thank you for your continued patience and support.

Read the full incident report →

Started Dec 18, 2025, 10:34 AM UTC· resolved Dec 18, 2025, 11:31 AM UTC

1. investigating Dec 18, 2025, 10:34 AM UTC

   Hi Team, We are currently observing intermittent errors with the AI related services due to an Azure OpenAI-related dependency . Our team is actively investigating the issue and is checking this with Azure for further validation. We will keep you updated as we have more information. Please feel free to reach out if you have any questions in the meantime. Thank you for your patience.

2. investigating Dec 18, 2025, 10:55 AM UTC

   We are continuing to investigate this issue.

3. investigating Dec 18, 2025, 10:56 AM UTC

   We are continuing to investigate this issue.

4. resolved Dec 18, 2025, 11:31 AM UTC

   The intermittent errors impacting the AI-related services due to an Azure OpenAI–related dependency have now been resolved. We will continue to monitor the systems to ensure stability. Please feel free to reach out if you observe any further issues or have questions. If you have any questions or need further assistance, please don’t hesitate to reach out to Sprinklr Support. Thank you for your patience and cooperation.

Read the full incident report →

Started Dec 17, 2025, 04:29 PM UTC· resolved Dec 21, 2025, 04:24 AM UTC

1. investigating Dec 17, 2025, 04:29 PM UTC

   We want to inform you that our team has identified an issue where users may experience disruptions with Benchmarking, as some posts might not be ingested into the platform, which can affect reporting and dashboard accuracy.. Our engineering team is actively investigating this at the highest priority and working toward a resolution. We will keep you updated as soon as we have further progress. We sincerely apologize for the inconvenience caused and appreciate your patience. If you continue to face issues related to Benchmarking posts, please report them to Sprinklr Support for assistance. Thank you!

2. resolved Dec 21, 2025, 04:24 AM UTC

   Hi Team, We are pleased to inform you that the issue affecting the Benchmarking functionality, where some posts were not being ingested into the platform, was fully resolved on 19th Dec 2025, 14:20 PM IST. Our engineering team has successfully addressed the underlying cause, and we have confirmed that reporting and dashboard accuracy is back to normal. Thank you for your patience and understanding as we worked to resolve this matter. If you continue to experience any issues, or if you have further questions, please don’t hesitate to reach out to Sprinklr Support for assistance. We appreciate your continued support.

Read the full incident report →

Started Dec 11, 2025, 04:37 AM UTC· resolved Dec 12, 2025, 10:53 AM UTC

1. investigating Dec 11, 2025, 04:37 AM UTC

   This is to inform you that we have identified an issue where the Threads Message Insights API is currently failing across multiple environments. This is resulting delay in message when fetching message-level insights for Threads. The issue has been raised with the Threads (Meta) channel team and is now under active investigation. We are closely monitoring the situation and will provide updates as more information becomes available. In the meantime, if you observe any issues related to Threads insights or reporting, please report them to Sprinklr Support so we can assist and track the impact

2. resolved Dec 12, 2025, 10:53 AM UTC

   Hi Team, We are pleased to inform you that the issue impacting the Threads Message Insights API has been successfully resolved. The delays in fetching message-level insights for Threads have now been addressed, and the API is operating as expected across all environments. We would like to thank you for your patience and understanding while the Threads (Meta) channel team worked to resolve the issue. If you continue to experience any related issues or have any further questions, please don't hesitate to reach out to Sprinklr Support. Thank you for your cooperation.

Read the full incident report →

Started Dec 04, 2025, 11:11 AM UTC· resolved Dec 04, 2025, 12:41 PM UTC

1. investigating Dec 04, 2025, 11:11 AM UTC

   We are currently experiencing a downtime affecting the Frequently Asked Questions (FAQ) bot services. These bots, which help automate responses to common customer queries, may not function as expected during this period. Our engineering team is actively investigating the issue and working to restore full functionality as soon as possible. We will share further updates as we make progress. Thank you for your patience.

2. resolved Dec 04, 2025, 12:41 PM UTC

   The earlier downtime affecting the Frequently Asked Questions (FAQ) bot services has now been resolved. All FAQ bots are functioning as expected. Our engineering team has implemented the necessary fix, and services have been restored to normal operation. We will continue to monitor to ensure stability. Thank you for your patience.

Read the full incident report →

Started Dec 02, 2025, 09:25 PM UTC· resolved Dec 02, 2025, 10:08 PM UTC

1. investigating Dec 02, 2025, 09:25 PM UTC

   This is to inform you that we are observing intermittent issues in the platform especially with X media publishing, This seems to be occurring due to X API issues. We shall keep you posted as soon as we have further updates on this.

2. resolved Dec 02, 2025, 10:08 PM UTC

   The earlier intermittent issues affecting X media publishing have now been fully resolved. All platform functionalities are operating as expected. If you encounter any further issues, please contact the Sprinklr Support Team.

Read the full incident report →

Started Nov 28, 2025, 03:25 AM UTC· resolved Nov 29, 2025, 06:07 AM UTC

1. investigating Nov 28, 2025, 03:25 AM UTC

   Hi Team, We are currently experiencing issues with Instagram Message Breakdown Insights reporting due to continuous failures from the Instagram API since approximately 07:00 AM IST . Our engineering teams are actively investigating and working to restore normal functionality. We will provide further updates as more information becomes available. Please feel free to reach out to Sprinklr Support if you have any questions.

2. resolved Nov 29, 2025, 06:07 AM UTC

   Hi Team The issue impacting Instagram Message Breakdown Insights reporting, caused by continuous failures from the Instagram API since approximately 07:00 AM IST, has now been fully resolved. Data processing has stabilized, and all functionalities are operating as expected. Our engineering teams have confirmed recovery from Instagram’s side and normal service has been restored. If you have any questions or notice any anomalies, please feel free to reach out to Sprinklr Support.

Read the full incident report →

Started Nov 19, 2025, 11:44 AM UTC· resolved Nov 21, 2025, 12:36 PM UTC

1. investigating Nov 19, 2025, 11:44 AM UTC

   Hi Team, We would like to inform you that we have identified an issue with X (formerly Twitter) currently impacting the grabbing of Direct Messages (DMs). Our team is actively investigating this, working closely with the X channel team, and we are treating the matter with utmost priority. In the meantime, X recommends that users avoid following back anyone who starts a new DM conversation. This ensures the message remains in the standard unencrypted flow. Please note that this applies only to new DM conversations, unfollowing users who have already messaged you will not resolve the issue.

2. resolved Nov 21, 2025, 12:36 PM UTC

   Hi Team, We’re pleased to inform you that the issue on the X platform (formerly Twitter) that was affecting the grabbing of Direct Messages (DMs) has now been fully resolved. The DM grabbing functionality is working as expected, and all operations have returned to normal. Our team will continue to monitor the platform closely to ensure stability. If you notice anything unusual or need any further assistance, please feel free to reach out to Sprinklr Support. Thank you for your patience and cooperation.

Read the full incident report →

Started Nov 18, 2025, 12:29 PM UTC· resolved Nov 19, 2025, 04:50 AM UTC

1. investigating Nov 18, 2025, 12:29 PM UTC

   This is to inform you that we have observed issues in the platform especially with twitter publishing, grabbing and reporting. This seems to be occurring due to Twitter API issues. We shall keep you posted as soon as we have further updates on this.

2. investigating Nov 18, 2025, 03:41 PM UTC

   would like to inform you about an ongoing issue related to Twitter publishing across the platform. We suspect that this could be related to the current Cloudflare outage, and we are actively working with twitter team to resolve the issue as a priority. We will continue to keep you posted on any further developments. In the meantime, if you have any urgent concerns, please reach out to Sprinklr support.

3. resolved Nov 19, 2025, 04:50 AM UTC

   Twitter publishing, grabbing and reporting has been restored. All systems are operating as expected. Thank you for your patience.

Read the full incident report →

Started Nov 15, 2025, 01:18 PM UTC· resolved Nov 18, 2025, 06:52 AM UTC

1. investigating Nov 15, 2025, 01:18 PM UTC

   Hi Team, We would like to inform you that we have identified an issue with X (formerly Twitter). Their recent release of an encrypted chat feature is currently impacting the grabbing of Direct Messages (DMs). Our team is actively investigating this, working closely with the X channel team, and we are treating the matter with utmost priority. We will keep you updated as soon as we have more information. Thank you for your patience and understanding.

2. resolved Nov 18, 2025, 06:52 AM UTC

   Hi Team, We’d like to inform you that the earlier issue affecting Direct Message (DM) grabbing on X (formerly Twitter) has now been resolved. Our engineering team, in collaboration with the X channel team, has implemented the necessary fixes, and the service is now functioning as expected. We are continuing to monitor the platform to ensure stability and consistent performance. Thank you for your patience and understanding

Read the full incident report →

Started Nov 15, 2025, 01:55 AM UTC· resolved Dec 04, 2025, 03:47 AM UTC

1. investigating Nov 15, 2025, 01:55 AM UTC

   Hi team This is to inform you that our team has identified an issue with Twitter message ingestion. Our engineering team is actively investigating the root cause and working to restore full functionality as quickly as possible.We will provide updates as more information becomes available. Thank you.

2. investigating Nov 15, 2025, 09:47 AM UTC

   We are continuing to investigate this issue.

3. investigating Nov 15, 2025, 09:55 AM UTC

   We are continuing to investigate this issue.

4. investigating Nov 15, 2025, 10:03 AM UTC

   We are continuing to investigate this issue.

5. identified Nov 15, 2025, 10:39 AM UTC

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

6. identified Nov 15, 2025, 11:23 AM UTC

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

7. monitoring Nov 16, 2025, 02:17 AM UTC

   Hi Team, We’d like to inform you that the earlier disruptions in Twitter Data Ingestion have now been resolved. Our engineering teams have confirmed that services are stable and functioning as expected. We will continue to monitor the system closely to ensure consistent performance. Please note that the fix has not yet been implemented for Prod 19, and we will provide an update as soon as it becomes available. Thank you for your patience and understanding during this time.

8. resolved Dec 04, 2025, 03:47 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 13, 2025, 11:50 AM UTC· resolved Nov 13, 2025, 02:53 PM UTC

1. identified Nov 13, 2025, 11:50 AM UTC

   We are currently observing latency issues in bot replies within AIMEE. The responses from the bot are delayed, and upon investigation, it appears that the latency is related to Azure API performance. The issue occurs inconsistently but is impacting the overall user experience. We will continue to monitor the situation from our side. If you have any questions or need further assistance, please don’t hesitate to reach out to Sprinklr Support.

2. identified Nov 13, 2025, 12:53 PM UTC

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

3. identified Nov 13, 2025, 12:57 PM UTC

   This is to inform that Microsoft has acknowledged an ongoing issue with the Azure OpenAI GPT-4 Mini service in the Sweden Central region, which may be contributing to the latency we are experiencing. They have also update the status site- Link - https://azure.status.microsoft/en-gb/status We will continue to monitor the situation from our side and provide updates as more information becomes available. If you have any questions or need further assistance, please don’t hesitate to reach out to Sprinklr

4. resolved Nov 13, 2025, 02:53 PM UTC

   Microsoft Azure has confirmed the issue is resolved. All impacted instances are restored, and services are operating normally. We will continue to monitor to ensure stable performance.

Read the full incident report →

Started Nov 12, 2025, 04:43 PM UTC· resolved Nov 19, 2025, 05:17 AM UTC

1. identified Nov 12, 2025, 04:43 PM UTC

   We are currently experiencing a disruption with the Facebook Reels API. Users attempting to publish Reels may encounter errors such as: “We are currently experiencing a disruption with Facebook Reel API. Please re-try in a few minutes.” This issue appears to originate from Facebook’s end and is impacting all API-based publishing attempts. Current Action: Our engineering team is monitoring the situation and is in contact with Meta for updates. We recommend retrying affected posts after some time. Next Update: We will provide the next update as soon as more information becomes available. Thank you for your patience.

2. resolved Nov 19, 2025, 05:17 AM UTC

   Temporary disruption affecting Reels publishing via API has been resolved. Reels publishing is now functioning normally.

Read the full incident report →

Started Nov 10, 2025, 03:56 PM UTC· resolved Nov 10, 2025, 03:56 PM UTC

1. resolved Nov 10, 2025, 03:56 PM UTC

   Hi Team, This is to inform you that our team identified an issue where reporting data was not loading and dashboard widgets were failing to load, resulting in errors. We prioritized resolving this with our team internally and are happy to confirm that the issue has now been fixed, and dashboards are now functioning normally. We will continue to monitor the system closely to ensure everything is functioning as expected. If you experience any further issues, please don't hesitate to reach out to Sprinklr Support.

Read the full incident report →

Started Nov 10, 2025, 05:23 AM UTC· resolved Nov 10, 2025, 05:59 AM UTC

1. investigating Nov 10, 2025, 05:23 AM UTC

   This is to inform you that our team has identified an issue where Twitter message ingestion and enrichment processes may be delayed. Our engineering team is actively investigating the root cause and working to restore full functionality as quickly as possible. We will provide updates as more information becomes available.

2. resolved Nov 10, 2025, 05:59 AM UTC

   We are pleased to inform you that the issue regarding delays in Twitter message ingestion and enrichment has been successfully resolved. Our engineering team has identified and addressed the root cause, and the affected processes have been fully restored to normal operation. Thank you for your patience while we worked to resolve this matter. Should you have any further questions or experience any issues, please don't hesitate to reach out.

Read the full incident report →

Started Nov 01, 2025, 03:16 PM UTC· resolved Nov 01, 2025, 06:12 PM UTC

1. identified Nov 01, 2025, 03:16 PM UTC

   We are currently experiencing an outage in our benchmarking cluster, which may result in slower response times or temporary delays in benchmarking-related services. Our engineering team is actively working to restore full performance. All other systems remain operational. We’ll provide updates as soon as more information becomes available.

2. resolved Nov 01, 2025, 06:12 PM UTC

   The benchmarking cluster issue has been resolved, and normal service has been fully restored. Users should no longer experience delays or performance issues. We’ll continue to monitor system performance to ensure stability. Thank you for your patience while we addressed this incident.

Read the full incident report →

Started Oct 30, 2025, 07:51 AM UTC· resolved Nov 03, 2025, 01:08 PM UTC

1. investigating Oct 30, 2025, 07:51 AM UTC

   Hi team We are currently experiencing an issue affecting TikTok platform services. This disruption is impacting the ability to fetch TikTok data, publish posts and replies due to a permission error: "No permission to operate tiktok creator id". This may result in delayed or failed grabbing of TikTok comments and replies and failure in publishing posts and replies. Please note that account addition is resulting in a duplicate account creation on Sprinklr because TikTok API is returning a different Business ID for the same account. Therefore, account re-addition is not recommended at this point to avoid duplication of accounts. Thank you.

2. identified Oct 31, 2025, 10:27 AM UTC

   Hi Team, We wanted to share the updates with you that TikTok has acknowledged the concern and have rolled back the service that seemed to be causing the issue. We are monitoring the situation on our side. We will keep you updated with the latest. Thank you for your patience.

3. identified Nov 03, 2025, 10:01 AM UTC

   Hi team, Based on the latest error logs and the trend of it over the last 2 days since TikTok fixed the root cause of this issue, we have observed a decline close to zero for such errors. You will only observe these errors in case a duplicate account was created if you tried re-adding the affected account and you are trying to publish or reply through the duplicate account. We recommend that you continue your operations with the original account and manually deactivate the duplicate account to avoid confusion. Help article to deactivate the account: https://www.sprinklr.com/help/articles/manage-accounts/deactivate-an-account/63ef5821ef1b447d6c631c7f With the above said, we are now working with TikTok to identify the RCA and will get back to you as soon as we have an update on the same.

4. resolved Nov 03, 2025, 01:08 PM UTC

   Hi team, We have received an update from TikTok with regards to the RCA. TikTok has acknowledged that this was due to an internal issue that was affecting their APIs and they rolled back a service which resolved the problem. Other details revolving the RCA are sensitive and cannot be shared by TikTok. As noted in our previous communication, your original account should work as expected and should not be facing any errors. If a duplicate account was created, you can deactivate the same. Help article: https://www.sprinklr.com/help/articles/manage-accounts/deactivate-an-account/63ef5821ef1b447d6c631c7f

Read the full incident report →