Sprinklr Outage History

Sprinklr degraded · 3 active incidents View live status →

Sprinklr had 62 outages in the last 2 years totaling 291h 53m of downtime — averaging 2.5 incidents per month.

There were 62 Sprinklr outages since October 10, 2025 totaling 291h 53m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.sprinklr.com

Minor November 13, 2025

Azure API latency issues observed

Detected by Pingoru
Nov 13, 2025, 11:50 AM UTC
Resolved
Nov 13, 2025, 02:53 PM UTC
Duration
3h 3m
Affected: EMEA (Prod5)
Timeline · 4 updates
  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 →

Major November 12, 2025

Facebook Reels Publishing – Disruption

Detected by Pingoru
Nov 12, 2025, 04:43 PM UTC
Resolved
Nov 19, 2025, 05:17 AM UTC
Duration
6d 12h
Affected: APAC (Prod4)APAC (Prod11)EMEA (Prod3)EMEA (Prod5)EMEA (Prod15)America (Prod)America (Prod6)America (Prod2)America (Prod8)EMEA (Prod16)EMEA (Prod17)EMEA (Prod18)EMEA (Prod19)America (Prod12)EMEA (Prod21)
Timeline · 2 updates
  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 →

Notice November 10, 2025

Issue with Reporting Data – Resolved

Detected by Pingoru
Nov 10, 2025, 03:56 PM UTC
Resolved
Nov 10, 2025, 03:56 PM UTC
Duration
—
Affected: America (Prod2)
Timeline · 1 update
  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 →

Major November 10, 2025

Twitter message ingestion and enrichment may be delayed

Detected by Pingoru
Nov 10, 2025, 05:23 AM UTC
Resolved
Nov 10, 2025, 05:59 AM UTC
Duration
36m
Affected: America (Prod)
Timeline · 2 updates
  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 →

Major November 1, 2025

Benchmarking Cluster Outage

Detected by Pingoru
Nov 01, 2025, 03:16 PM UTC
Resolved
Nov 01, 2025, 06:12 PM UTC
Duration
2h 55m
Affected: America (Prod2)America (Prod6)America (Prod8)EMEA (Prod3)EMEA (Prod5)EMEA (Prod15)EMEA (Prod16)EMEA (Prod17)EMEA (Prod18)APAC (Prod4)APAC (Prod11)EMEA (Prod19)America (Prod12)EMEA (Prod21)
Timeline · 2 updates
  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 →

Minor October 30, 2025

Issue with TikTok Comment/ Reply Grabbing

Detected by Pingoru
Oct 30, 2025, 07:51 AM UTC
Resolved
Nov 03, 2025, 01:08 PM UTC
Duration
4d 5h
Affected: America (Prod)America (Prod2)America (Prod6)America (Prod8)EMEA (Prod3)EMEA (Prod5)EMEA (Prod15)EMEA (Prod16)EMEA (Prod17)EMEA (Prod18)APAC (Prod4)APAC (Prod11)EMEA (Prod19)America (Prod12)EMEA (Prod21)
Timeline · 4 updates
  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 →

Minor October 20, 2025

Intermittent 503 Errors Across Services

Detected by Pingoru
Oct 20, 2025, 12:37 PM UTC
Resolved
Oct 20, 2025, 01:50 PM UTC
Duration
1h 12m
Affected: America (Prod)
Timeline · 3 updates
  1. investigating Oct 20, 2025, 12:37 PM UTC

    We are currently experiencing intermittent 503 error responses across our services. Our engineering team is actively investigating the root cause and working to restore full functionality. We will provide updates here as more information becomes available. We appreciate your patience and apologize for any inconvenience.

  2. investigating Oct 20, 2025, 01:02 PM UTC

    We are currently experiencing a service disruption resulting in 503 errors across parts of our system. The issue has been identified as originating from our upstream service provider, AWS. Our team has raised the incident with AWS and is actively monitoring their updates while performing internal checks to minimize impact where possible. We will continue to provide timely updates here as we receive more information. Thank you for your patience and understanding.

  3. resolved Oct 20, 2025, 01:50 PM UTC

    Hello All, We are pleased to inform you that the service disruption causing intermittent 503 errors across our systems has been resolved. Our engineering team has verified that all affected services are operating normally, and we continue to monitor the system to ensure stability. We apologize for any inconvenience caused and thank you for your patience and understanding.

Read the full incident report →

Minor October 20, 2025

AWS Global Outage

Detected by Pingoru
Oct 20, 2025, 09:22 AM UTC
Resolved
Oct 20, 2025, 11:36 PM UTC
Duration
14h 14m
Affected: America (Prod)America (Prod2)America (Prod6)America (Prod8)EMEA (Prod3)EMEA (Prod5)EMEA (Prod15)EMEA (Prod16)EMEA (Prod17)EMEA (Prod18)APAC (Prod4)APAC (Prod11)EMEA (Prod19)America (Prod12)EMEA (Prod21)
Timeline · 10 updates

Read the full incident report →

Minor October 17, 2025

Platform Slowness

Detected by Pingoru
Oct 17, 2025, 02:45 PM UTC
Resolved
Oct 17, 2025, 02:59 PM UTC
Duration
14m
Affected: America (Prod2)
Timeline · 2 updates
  1. investigating Oct 17, 2025, 02:45 PM UTC

    Hi team, We are writing to proactively keep you informed that our monitoring system has identified few alerts related to slowness. 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.

  2. resolved Oct 17, 2025, 02:59 PM UTC

    Hi Team, We’d like to inform you that the earlier observed slowness issue has now been resolved. Our engineering teams have implemented necessary fixes, and the platform performance has stabilized. We will continue to monitor the system closely to ensure consistent performance. If you continue to experience any issues or need further assistance, please don’t hesitate to reach out to Sprinklr Support.

Read the full incident report →

Minor October 14, 2025

Delay in publishing comments

Detected by Pingoru
Oct 14, 2025, 07:20 AM UTC
Resolved
Oct 14, 2025, 08:23 AM UTC
Duration
1h 3m
Affected: EMEA (Prod19)
Timeline · 2 updates
  1. investigating Oct 14, 2025, 07:20 AM UTC

    Hi Team, We’re currently experiencing delays in the publishing of comments within Sprinklr. Our engineering team is actively investigating the issue as a top priority. We’ll keep you updated with any developments and share an estimated resolution time as soon as we have more information. Thank you for your patience and understanding.

  2. resolved Oct 14, 2025, 08:23 AM UTC

    Hi Team, This is to inform you that the issue causing delays while publishing of comments within Sprinklr and latency observed has been successfully resolved as of 1:15 PM IST. Comment publishing is now functioning normally. Thank you for your patience and understanding during this time. Please feel free to reach out if you notice any further issues.

Read the full incident report →