- Detected by Pingoru
- Jun 15, 2026, 04:20 PM UTC
- Resolved
- Jun 15, 2026, 06:21 PM UTC
- Duration
- 2h
Affected: America (Prod)
Timeline · 2 updates
-
investigating Jun 15, 2026, 04:20 PM UTC
We are currently experiencing a disruption affecting voice services. Users may encounter issues placing or receiving calls. Our engineering team has identified the issue and is actively investigating. We are working to restore normal service as quickly as possible. We will provide updates as more information becomes available.
-
resolved Jun 15, 2026, 06:21 PM UTC
The issue affecting voice services has been resolved, and services are now operating normally. Our engineering team has completed remediation efforts and continues to monitor the platform to ensure ongoing stability and performance. We apologize for any inconvenience and thank you for your patience.
Read the full incident report →
- Detected by Pingoru
- Jun 13, 2026, 05:55 AM UTC
- Resolved
- Jun 13, 2026, 07:17 AM UTC
- Duration
- 1h 21m
Affected: America (Prod2)
Timeline · 2 updates
-
identified Jun 13, 2026, 05:55 AM UTC
Hi Team, We are currently investigating an issue that may cause intermittent failures or delays while loading media assets and attachments within the Sprinklr platform for a subset of customers. Our Engineering teams are actively working to identify the root cause and restore normal functionality. We will continue to provide updates as more information becomes available.
-
resolved Jun 13, 2026, 07:17 AM UTC
Hi Team, The issue impacting the loading of media assets and attachments within the Sprinklr platform has been resolved as of 12:25 PM IST / 06:55 AM UTC. Our Engineering teams implemented the necessary mitigation, and services have been restored successfully. We are no longer observing failures or delays, and monitoring confirms normal platform behaviour. We will continue to monitor the platform closely to ensure ongoing stability. Thank you for your patience and understanding.
Read the full incident report →
- Detected by Pingoru
- Jun 12, 2026, 02:02 PM UTC
- Resolved
- Jun 12, 2026, 05:27 PM UTC
- Duration
- 3h 25m
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 Jun 12, 2026, 02:02 PM UTC
Status: Investigating We are investigating reports of users encountering the following error while sending messages: "An unexpected error occurred, likely due to a temporary channel outage. Please re-try publishing after a short while." Based on our initial assessment, we suspect this may be related to an issue on the Meta side. Our engineering team is actively investigating and coordinating with the relevant parties to confirm the root cause and assess the impact. We will provide further updates as soon as more information becomes available.
-
identified Jun 12, 2026, 02:31 PM UTC
We are investigating reports of users encountering the following error while sending messages: "An unexpected error occurred, likely due to a temporary channel outage. Please re-try publishing after a short while." Based on our current findings, the issue appears to be originating from the Meta side. We are observing multiple API failures impacting Meta channels, including Facebook and Instagram, resulting in message publishing failures. Our engineering team has raised the issue with Meta, and it is currently being investigated by their team. We are actively coordinating with the relevant parties to confirm the root cause and assess the overall impact. We will continue to monitor the situation closely and provide further updates as soon as more information becomes available. Thank you for your patience and understanding.
-
resolved Jun 12, 2026, 05:27 PM UTC
Hi Team , We would like to inform you that the earlier Meta outage impacting Cloud API and related services has now been resolved. Services have been fully restored and are operating normally. Our team will continue to monitor the environment to ensure ongoing stability. Thank you for your patience and understanding
Read the full incident report →
- Detected by Pingoru
- Jun 06, 2026, 11:44 AM UTC
- Resolved
- Jun 06, 2026, 11:44 AM UTC
- Duration
- —
Affected: APAC (Prod4)
Timeline · 1 update
-
resolved Jun 06, 2026, 11:44 AM UTC
We would like to inform you that we received an alert related to the Co-browse service, which may have caused intermittent access issues for some users. Our team investigated the issue promptly and has now resolved it. The service is functioning normally, and no further impact is expected at this time. We will continue to monitor the service closely to ensure stability. Thank you for your patience and understanding.
Read the full incident report →
- Detected by Pingoru
- Jun 05, 2026, 10:46 PM UTC
- Resolved
- Jun 05, 2026, 11:04 PM UTC
- Duration
- 18m
Affected: APAC (Prod4)
Timeline · 2 updates
-
identified Jun 05, 2026, 10:46 PM UTC
Hi Team, We are currently observing that the Prod4 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.
-
resolved Jun 05, 2026, 11:04 PM UTC
Hi team, We are pleased to inform you that the issue with Prod4 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
- Jun 05, 2026, 07:43 AM UTC
- Resolved
- Jun 15, 2026, 10:52 AM UTC
- Duration
- 10d 3h
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 · 3 updates
-
investigating Jun 05, 2026, 07:43 AM UTC
Hi All, We are currently experiencing issues with Facebook workflows due to a recent Meta platform update. The impact includes fetching posts via comments (especially dark posts), Facebook profile creation and updates, and Facebook comment retrieval across all environments. Our Engineering team is actively working with Meta on a resolution and will provide further updates as they become available.
-
identified Jun 10, 2026, 01:57 PM UTC
Hi All, We have identified the required updates on the Sprinklr side and are currently working on implementing the fix. We will continue to share progress as deployment moves forward and confirm once all impacted workflows are restored." Thank you
-
resolved Jun 15, 2026, 10:52 AM UTC
The issue has been resolved, and workflows involving Facebook dark post comments will now work as expected going forward. If you have any questions or need further assistance, please reach out to Sprinklr Support. Thank you for your understanding and continued partnership.
Read the full incident report →
- Detected by Pingoru
- May 29, 2026, 04:06 PM UTC
- Resolved
- May 29, 2026, 06:09 PM UTC
- Duration
- 2h 3m
Affected: EMEA (Prod3)EMEA (Prod5)EMEA (Prod18)EMEA (Prod21)
Timeline · 2 updates
-
identified May 29, 2026, 04:06 PM UTC
We are currently observing issues with AI Agent bots failing due to GenAI service unavailability. Initial investigation indicates that the issue appears to be originating from the Azure side, impacting GenAI service availability. Our engineering team is actively monitoring the situation and coordinating further investigation. We will continue to provide updates as more information becomes available. We appreciate your patience and understanding.
-
resolved May 29, 2026, 06:09 PM UTC
Hi Team , We would like to inform you that the issue impacting AI Agent bots due to GenAI service unavailability has now been resolved. Services are currently stable and functioning normally. The service has since recovered. Our teams will continue to monitor the environment closely to ensure stability.
Read the full incident report →
- Detected by Pingoru
- May 19, 2026, 11:01 AM UTC
- Resolved
- May 19, 2026, 11:36 AM UTC
- Duration
- 34m
Affected: EMEA (Prod15)
Timeline · 2 updates
-
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.
-
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 →
- Detected by Pingoru
- May 19, 2026, 04:38 AM UTC
- Resolved
- May 19, 2026, 05:01 AM UTC
- Duration
- 22m
Affected: APAC (Prod4)
Timeline · 2 updates
-
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.
-
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 →
- Detected by Pingoru
- May 11, 2026, 10:57 AM UTC
- Resolved
- May 11, 2026, 12:00 PM UTC
- Duration
- 1h 2m
Affected: APAC (Prod4)
Timeline · 3 updates
-
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.
-
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.
-
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 →
- Detected by Pingoru
- May 08, 2026, 05:28 AM UTC
- Resolved
- May 11, 2026, 04:31 PM UTC
- Duration
- 3d 11h
Affected: America (Prod)America (Prod2)America (Prod6)America (Prod8)EMEA (Prod3)America (Prod12)
Timeline · 5 updates
Read the full incident report →
- Detected by Pingoru
- May 06, 2026, 10:49 AM UTC
- Resolved
- May 06, 2026, 11:29 AM UTC
- Duration
- 39m
Affected: EMEA (Prod19)
Timeline · 2 updates
-
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.
-
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 →
- Detected by Pingoru
- Apr 23, 2026, 12:18 PM UTC
- Resolved
- Apr 23, 2026, 02:50 PM UTC
- Duration
- 2h 32m
Affected: EMEA (Prod15)
Timeline · 3 updates
-
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.
-
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.
-
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 →
- Detected by Pingoru
- Apr 20, 2026, 06:03 PM UTC
- Resolved
- Apr 27, 2026, 02:37 PM UTC
- Duration
- 6d 20h
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
-
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.
-
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 →
- Detected by Pingoru
- Apr 13, 2026, 07:28 PM UTC
- Resolved
- Apr 13, 2026, 08:25 PM UTC
- Duration
- 56m
Affected: America (Prod)
Timeline · 2 updates
-
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.
-
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 →
- Detected by Pingoru
- Apr 09, 2026, 06:11 AM UTC
- Resolved
- Apr 20, 2026, 05:54 AM UTC
- Duration
- 10d 23h
Affected: America (Prod2)America (Prod)America (Prod8)EMEA (Prod3)EMEA (Prod17)EMEA (Prod19)EMEA (Prod21)
Timeline · 4 updates
-
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.
-
investigating Apr 09, 2026, 06:22 AM UTC
We are continuing to investigate this issue.
-
investigating Apr 09, 2026, 06:26 AM UTC
We are continuing to investigate this issue.
-
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 →
- Detected by Pingoru
- Apr 08, 2026, 03:01 AM UTC
- Resolved
- Apr 17, 2026, 06:44 AM UTC
- Duration
- 9d 3h
Affected: EMEA (Prod3)
Timeline · 3 updates
-
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.
-
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.
-
resolved Apr 17, 2026, 06:44 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 06, 2026, 11:23 AM UTC
- Resolved
- Apr 07, 2026, 03:02 AM UTC
- Duration
- 15h 38m
Affected: America (Prod8)EMEA (Prod3)
Timeline · 2 updates
-
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.
-
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 →
- Detected by Pingoru
- Apr 01, 2026, 07:32 AM UTC
- Resolved
- Apr 01, 2026, 08:07 AM UTC
- Duration
- 35m
Affected: EMEA (Prod3)
Timeline · 2 updates
-
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.
-
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 →
- Detected by Pingoru
- Mar 30, 2026, 10:25 AM UTC
- Resolved
- Mar 30, 2026, 10:36 AM UTC
- Duration
- 10m
Affected: EMEA (Prod21)
Timeline · 2 updates
-
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.
-
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 →
- Detected by Pingoru
- Mar 16, 2026, 06:18 PM UTC
- Resolved
- Mar 17, 2026, 08:28 AM UTC
- Duration
- 14h 10m
Affected: America (Prod)
Timeline · 2 updates
-
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.
-
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 →
- Detected by Pingoru
- Mar 15, 2026, 05:22 AM UTC
- Resolved
- Mar 15, 2026, 06:58 AM UTC
- Duration
- 1h 35m
Affected: America (Prod)
Timeline · 2 updates
-
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.
-
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 →
- Detected by Pingoru
- Mar 12, 2026, 03:35 PM UTC
- Resolved
- Mar 16, 2026, 11:54 AM UTC
- Duration
- 3d 20h
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
-
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.
-
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 →
- Detected by Pingoru
- Mar 02, 2026, 05:32 AM UTC
- Resolved
- Mar 02, 2026, 05:53 AM UTC
- Duration
- 20m
Affected: EMEA (Prod15)
Timeline · 3 updates
-
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.
-
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.
-
resolved Mar 02, 2026, 05:53 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 01, 2026, 01:17 PM UTC
- Resolved
- Mar 01, 2026, 07:44 PM UTC
- Duration
- 6h 27m
Affected: EMEA (Prod15)
Timeline · 8 updates
Read the full incident report →