- Detected by Pingoru
- Feb 26, 2026, 08:28 AM UTC
- Resolved
- Mar 02, 2026, 08:01 AM UTC
- Duration
- 3d 23h
Affected: America (Prod)America (Prod6)America (Prod8)America (Prod2)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
-
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/
-
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 →
- Detected by Pingoru
- Feb 23, 2026, 11:20 PM UTC
- Resolved
- Mar 12, 2026, 03:57 PM UTC
- Duration
- 16d 16h
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 · 3 updates
-
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.
-
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.
-
resolved Mar 12, 2026, 03:57 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 21, 2026, 06:47 AM UTC
- Resolved
- Feb 21, 2026, 08:30 AM UTC
- Duration
- 1h 43m
Affected: America (Prod)
Timeline · 4 updates
-
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.
-
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
-
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.
-
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 →
- Detected by Pingoru
- Feb 18, 2026, 11:58 AM UTC
- Resolved
- Feb 18, 2026, 02:33 PM UTC
- Duration
- 2h 34m
Affected: EMEA (Prod3)EMEA (Prod18)EMEA (Prod19)
Timeline · 5 updates
-
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.
-
investigating Feb 18, 2026, 12:00 PM UTC
We are continuing to investigate this issue.
-
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.
-
investigating Feb 18, 2026, 12:18 PM UTC
We are continuing to investigate this issue.
-
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 →
- Detected by Pingoru
- Feb 12, 2026, 03:54 AM UTC
- Resolved
- Feb 12, 2026, 05:25 AM UTC
- Duration
- 1h 31m
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 · 2 updates
-
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.
-
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 →
- Detected by Pingoru
- Feb 09, 2026, 09:56 AM UTC
- Resolved
- Feb 09, 2026, 11:08 AM UTC
- Duration
- 1h 11m
Affected: EMEA (Prod15)EMEA (Prod15)EMEA (Prod15)
Timeline · 3 updates
-
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
-
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.
-
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 →
Critical January 29, 2026 - Detected by Pingoru
- Jan 29, 2026, 10:38 AM UTC
- Resolved
- Jan 29, 2026, 10:57 AM UTC
- Duration
- 19m
Affected: EMEA (Prod3)
Timeline · 2 updates
-
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.
-
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 →
- Detected by Pingoru
- Jan 28, 2026, 02:02 PM UTC
- Resolved
- Jan 28, 2026, 05:48 PM UTC
- Duration
- 3h 46m
Affected: EMEA (Prod19)
Timeline · 3 updates
-
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.
-
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.
-
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 →
- Detected by Pingoru
- Jan 27, 2026, 11:37 AM UTC
- Resolved
- Jan 28, 2026, 09:12 AM UTC
- Duration
- 21h 34m
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 · 3 updates
-
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.
-
investigating Jan 27, 2026, 11:49 AM UTC
We are continuing to investigate this issue.
-
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 →
- Detected by Pingoru
- Jan 20, 2026, 01:42 PM UTC
- Resolved
- Jan 27, 2026, 09:32 AM UTC
- Duration
- 6d 19h
Affected: America (Prod)America (Prod)America (Prod)America (Prod2)America (Prod2)America (Prod2)America (Prod6)America (Prod6)America (Prod6)America (Prod8)America (Prod8)America (Prod8)EMEA (Prod3)APAC (Prod4)APAC (Prod4)EMEA (Prod5)APAC (Prod11)APAC (Prod11)EMEA (Prod15)EMEA (Prod3)EMEA (Prod3)EMEA (Prod16)EMEA (Prod5)EMEA (Prod5)EMEA (Prod17)EMEA (Prod15)EMEA (Prod15)EMEA (Prod18)EMEA (Prod16)EMEA (Prod16)APAC (Prod4)EMEA (Prod17)EMEA (Prod17)APAC (Prod11)EMEA (Prod18)EMEA (Prod18)EMEA (Prod19)EMEA (Prod19)EMEA (Prod19)America (Prod12)America (Prod12)America (Prod12)EMEA (Prod21)EMEA (Prod21)EMEA (Prod21)EMEA (Prod21)
Timeline · 4 updates
-
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.
-
investigating Jan 20, 2026, 01:53 PM UTC
We are continuing to investigate this issue.
-
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.
-
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 →
- Detected by Pingoru
- Jan 20, 2026, 12:13 PM UTC
- Resolved
- Jan 24, 2026, 07:23 AM UTC
- Duration
- 3d 19h
Affected: America (Prod2)America (Prod)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 · 3 updates
-
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.
-
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.
-
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 →
- Detected by Pingoru
- Jan 16, 2026, 03:52 PM UTC
- Resolved
- Jan 18, 2026, 05:30 AM UTC
- Duration
- 1d 13h
Affected: America (Prod2)America (Prod)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
-
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.
-
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 →
- Detected by Pingoru
- Jan 14, 2026, 08:41 AM UTC
- Resolved
- Jan 15, 2026, 04:11 AM UTC
- Duration
- 19h 29m
Affected: America (Prod)America (Prod)America (Prod2)America (Prod2)America (Prod6)America (Prod6)America (Prod8)America (Prod8)EMEA (Prod3)EMEA (Prod3)EMEA (Prod5)EMEA (Prod5)EMEA (Prod15)EMEA (Prod15)EMEA (Prod16)EMEA (Prod16)EMEA (Prod17)EMEA (Prod17)EMEA (Prod18)EMEA (Prod18)APAC (Prod4)APAC (Prod4)APAC (Prod11)APAC (Prod11)EMEA (Prod19)EMEA (Prod19)America (Prod12)America (Prod12)EMEA (Prod21)EMEA (Prod21)
Timeline · 3 updates
-
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.
-
identified Jan 14, 2026, 08:42 AM UTC
We are continuing to work on a fix for this issue.
-
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 →
- Detected by Pingoru
- Jan 12, 2026, 09:47 AM UTC
- Resolved
- Jan 12, 2026, 10:53 AM UTC
- Duration
- 1h 5m
Affected: EMEA (Prod3)EMEA (Prod18)EMEA (Prod19)
Timeline · 3 updates
-
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.
-
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.
-
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 →
- Detected by Pingoru
- Dec 22, 2025, 10:08 AM UTC
- Resolved
- Dec 24, 2025, 11:15 AM UTC
- Duration
- 2d 1h
Affected: America (Prod)America (Prod)America (Prod2)America (Prod2)America (Prod8)America (Prod8)APAC (Prod4)APAC (Prod4)APAC (Prod11)APAC (Prod11)EMEA (Prod15)EMEA (Prod15)EMEA (Prod18)EMEA (Prod18)EMEA (Prod21)EMEA (Prod21)
Timeline · 4 updates
-
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.
-
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.
-
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.
-
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 →
- Detected by Pingoru
- Dec 18, 2025, 10:34 AM UTC
- Resolved
- Dec 18, 2025, 11:31 AM UTC
- Duration
- 57m
Affected: America (Prod)America (Prod2)America (Prod8)APAC (Prod4)APAC (Prod11)EMEA (Prod15)EMEA (Prod18)EMEA (Prod21)
Timeline · 4 updates
-
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.
-
investigating Dec 18, 2025, 10:55 AM UTC
We are continuing to investigate this issue.
-
investigating Dec 18, 2025, 10:56 AM UTC
We are continuing to investigate this issue.
-
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 →
- Detected by Pingoru
- Dec 17, 2025, 04:29 PM UTC
- Resolved
- Dec 21, 2025, 04:24 AM UTC
- Duration
- 3d 11h
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 · 2 updates
-
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!
-
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 →
- Detected by Pingoru
- Dec 11, 2025, 04:37 AM UTC
- Resolved
- Dec 12, 2025, 10:53 AM UTC
- Duration
- 1d 6h
Affected: America (Prod)America (Prod6)America (Prod8)America (Prod2)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
-
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
-
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 →
- Detected by Pingoru
- Dec 04, 2025, 11:11 AM UTC
- Resolved
- Dec 04, 2025, 12:41 PM UTC
- Duration
- 1h 30m
Affected: America (Prod)America (Prod8)EMEA (Prod5)EMEA (Prod15)APAC (Prod4)APAC (Prod11)
Timeline · 2 updates
-
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.
-
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 →
- Detected by Pingoru
- Dec 02, 2025, 09:25 PM UTC
- Resolved
- Dec 02, 2025, 10:08 PM UTC
- Duration
- 42m
Affected: America (Prod8)
Timeline · 2 updates
-
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.
-
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 →
- Detected by Pingoru
- Nov 28, 2025, 03:25 AM UTC
- Resolved
- Nov 29, 2025, 06:07 AM UTC
- Duration
- 1d 2h
Affected: America (Prod)America (Prod6)America (Prod8)America (Prod2)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
-
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.
-
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 →
- Detected by Pingoru
- Nov 19, 2025, 11:44 AM UTC
- Resolved
- Nov 21, 2025, 12:36 PM UTC
- Duration
- 2d
Affected: America (Prod2)America (Prod)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
-
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.
-
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 →
- Detected by Pingoru
- Nov 18, 2025, 12:29 PM UTC
- Resolved
- Nov 19, 2025, 04:50 AM UTC
- Duration
- 16h 21m
Affected: America (Prod2)America (Prod)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 · 3 updates
-
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.
-
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.
-
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 →
- Detected by Pingoru
- Nov 15, 2025, 01:18 PM UTC
- Resolved
- Nov 18, 2025, 06:52 AM UTC
- Duration
- 2d 17h
Affected: America (Prod2)America (Prod)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
-
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.
-
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 →
- Detected by Pingoru
- Nov 15, 2025, 01:55 AM UTC
- Resolved
- Dec 04, 2025, 03:47 AM UTC
- Duration
- 19d 1h
Affected: America (Prod2)America (Prod)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 · 8 updates
-
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.
-
investigating Nov 15, 2025, 09:47 AM UTC
We are continuing to investigate this issue.
-
investigating Nov 15, 2025, 09:55 AM UTC
We are continuing to investigate this issue.
-
investigating Nov 15, 2025, 10:03 AM UTC
We are continuing to investigate this issue.
-
identified Nov 15, 2025, 10:39 AM UTC
The issue has been identified and a fix is being implemented.
-
identified Nov 15, 2025, 11:23 AM UTC
We are continuing to work on a fix for this issue.
-
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.
-
resolved Dec 04, 2025, 03:47 AM UTC
This incident has been resolved.
Read the full incident report →