Sprinklr Outage History

Started Oct 29, 2025, 04:00 PM UTC· resolved Oct 30, 2025, 12:53 AM UTC

1. investigating Oct 29, 2025, 04:00 PM UTC

   Hi Team, We’ve received several alerts indicating errors when loading URLs across our services. Upon investigation, we’ve identified that the issue originates from our service provider, Microsoft Azure. Our monitoring confirms that this is an external incident affecting connectivity, and we’re actively tracking updates from Azure’s status page. We’ll provide additional information and expected resolution timelines as soon as they’re available. Thank you for your patience and understanding.

2. identified Oct 29, 2025, 04:47 PM UTC

   Hi Team, As per the latest update from Azure, starting around 16:00 UTC, Azure identified DNS-related issues that have caused degraded availability for some Azure services. As a result, some customers may experience intermittent difficulties accessing the Azure Portal. Azure has taken mitigation steps expected to restore portal access shortly. Their engineering teams are actively investigating the underlying cause and evaluating additional actions to ensure full recovery. We will continue to monitor the situation closely and provide an update within 60 minutes or sooner as more information becomes available. Thank you for your patience and understanding.

3. identified Oct 29, 2025, 04:54 PM UTC

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

4. identified Oct 29, 2025, 05:24 PM UTC

   As per the latest update from Azure, Starting around 16:00 UTC, Azure identified an issue with Azure Front Door (AFD) that is causing service availability problems. Some customers may also have trouble accessing the Azure Portal. The investigation and recovery efforts are ongoing, and Azure will provide another update within 60 minutes or sooner. We will continue to monitor the situation closely. Thank you for your patience and understanding.

5. identified Oct 29, 2025, 05:37 PM UTC

   According to the latest update from Azure, starting around 16:00 UTC, Azure identified an issue with Azure Front Door (AFD) that has caused service availability disruptions. The issue is believed to have been triggered by an unintentional configuration change. To reduce impact, Azure has paused all configuration changes to AFD services and is rolling back to the last known stable state. At this time, there is no estimated time for completion of the rollback. Azure will share another update within 30 minutes or as soon as more details become available. We are closely monitoring the situation and will continue to provide updates as Azure releases new information.

6. identified Oct 29, 2025, 06:06 PM UTC

   According to the latest update from Azure, beginning around 16:00 UTC, some customers and Microsoft services using Azure Front Door (AFD) have experienced latency, timeouts, and errors. Azure identified an issue with Azure Front Door (AFD) that has caused service availability disruptions. The issue is believed to have been triggered by an unintentional configuration change. Azure is actively working on a rollback to restore normal service. While there is no current ETA for completion, another update is expected within 30 minutes or as soon as new information becomes available. We are continuing to monitor the situation closely and will provide further updates as Azure shares more details.

7. identified Oct 29, 2025, 06:24 PM UTC

   As per the latest update from Azure, starting around 16:00 UTC, customers and Microsoft services using Azure Front Door (AFD) may have experienced latency, timeouts, and errors due to an unintentional configuration change. Azure has initiated deployment of the last known good configuration, expected to complete in about 30 minutes, after which initial recovery signs should be visible. There is no confirmed ETA for full mitigation, and Azure will share the next update once the rollback deployment is complete. We continue to monitor the situation closely and will share further updates as received.

8. identified Oct 29, 2025, 07:07 PM UTC

   According to the latest update from Azure, customers should now be able to access the Azure Portal directly. Most portal extensions are functioning as expected, indicating that the system is showing signs of recovery.

9. identified Oct 29, 2025, 07:44 PM UTC

   As per the latest update from Azure, customers should now be able to access the Azure Portal directly, and most portal extensions are functioning as expected, indicating continued signs of recovery. However, Azure reports a long-tailed recovery flow and anticipates that it may take up to 4 hours for complete mitigation.

10. identified Oct 29, 2025, 08:46 PM UTC

    As per the latest update from Azure, the deployment of the last known good configuration has been completed, and customers are beginning to see signs of recovery. The Azure Portal is accessible, and most extensions are functioning as expected, though a few endpoints may still face intermittent issues. Azure continues to recover nodes and route traffic through healthy ones and anticipates full mitigation within the next 4 hours. We are monitoring the situation closely and will share further updates as received.

11. identified Oct 29, 2025, 09:52 PM UTC

    As per the latest update from Azure, the deployment of the last known good configuration has been completed, and recovery is progressing. The Azure Portal is accessible, and most extensions are functioning normally, though some endpoints may still show intermittent issues. Azure continues to recover and rebalance nodes and anticipates full mitigation within the next couple of hours We are closely monitoring the situation and will share further updates as they become available.

12. identified Oct 29, 2025, 10:46 PM UTC

    As per the latest update from Azure, the deployment of the last known good configuration has been completed, and recovery is progressing. Azure is currently recovering and re-routing traffic through healthy nodes, with strong signs of improvement observed across affected regions. Some requests may still experience intermittent failures as nodes continue to recover. The Azure Portal is accessible, and most extensions are functioning normally, though a few (e.g., Marketplace) may still show intermittent issues. Azure anticipates full mitigation by 23:20 UTC on 29 October 2025, We continue to monitor the situation closely and will share further updates as received.

13. identified Oct 29, 2025, 11:20 PM UTC

    Azure has confirmed that deployment of the ‘last known good’ configuration has been completed, and recovery efforts are well underway. The platform is actively recovering nodes and routing traffic through healthy ones, which is resulting in gradual service stabilization. While many customers are already seeing improvements, some intermittent issues may continue as recovery progresses and configurations are rebalanced across the global infrastructure. The Azure Portal is accessible, and most extensions are operating as expected. However, a small number of endpoints, such as Marketplace, may still experience occasional loading problems. We continue to monitor the situation closely and will share further updates as received.

14. resolved Oct 30, 2025, 12:53 AM UTC

    We are pleased to inform you that the earlier issue with Azure Front Door (AFD), which caused service availability disruptions due to an unintentional configuration change, has now been resolved. Azure has confirmed that services have stabilized and normal operations have been restored across all affected regions. We are continuing to monitor the situation closely to ensure sustained stability. If you have any questions or need further assistance, please don’t hesitate to reach out to Sprinklr Support.

Read the full incident report →

Started Oct 20, 2025, 12:37 PM UTC· resolved Oct 20, 2025, 01:50 PM UTC

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 →

Started Oct 20, 2025, 09:22 AM UTC· resolved Oct 20, 2025, 11:36 PM UTC

1. investigating Oct 20, 2025, 09:22 AM UTC

   We are currently experiencing service disruptions across multiple product lines due to an ongoing incident with AWS in their us1 Region. Our incident response team has been activated and is actively working on mitigation while coordinating closely with AWS. The issue has been escalated to AWS leadership for expedited resolution. At this stage, no failover actions to alternative regions are recommended. Should this guidance change, we will immediately communicate the updated instructions. We appreciate your patience and understanding. Further updates will be shared as soon as additional information becomes available.

2. investigating Oct 20, 2025, 09:34 AM UTC

   Hi Team, AWS has applied initial mitigations to the ongoing issue in their us1 Region, and we are now observing significant signs of recovery across our affected services. Most requests are currently succeeding, and performance is steadily improving. Our incident response team continues to monitor the situation closely in collaboration with AWS. We will maintain heightened oversight until full resolution is confirmed. Thank you for your continued patience. We will share additional updates as new information becomes available.

3. identified Oct 20, 2025, 09:36 AM UTC

   Hi Team, AWS has applied initial mitigations to the ongoing issue in their us1 Region, and we are now observing significant signs of recovery across our affected services. Most requests are currently succeeding, and performance is steadily improving. Our incident response team continues to monitor the situation closely in collaboration with AWS. We will maintain heightened oversight until full resolution is confirmed. Thank you for your continued patience. We will share additional updates as new information becomes available.

4. identified Oct 20, 2025, 12:28 PM UTC

   Hi Team, We are monitoring the ongoing AWS US-EAST-1 incident, which is affecting multiple services. AWS has started recovery, and operations are gradually stabilizing. Some delays may still occur as they work through the backlog and restore full functionality. Our teams are actively tracking the situation and coordinating closely with AWS. We will provide another update as soon as more information is available.

5. identified Oct 20, 2025, 02:22 PM UTC

   We are currently observing significant API errors and connectivity issues impacting multiple services. These issues are related to AWS operations in the US-EAST-1 Region. Our engineering teams are actively monitoring the situation and coordinating with AWS to restore full functionality. We will keep you informed as soon as further updates are available. Thank you for your patience and understanding.

6. identified Oct 20, 2025, 03:29 PM UTC

   Hi Team, We’d like to inform you that AWS is continuing to investigate the root cause of the ongoing network connectivity issues impacting services such as DynamoDB, SQS, and Amazon Connect in the US-EAST-1 Region. According to AWS, the issue originated within the EC2 internal network, and their engineering teams are actively working on identifying mitigations and restoring full service functionality. We are closely monitoring the situation and will share further updates as more information becomes available. Thank you for your patience and understanding.

7. identified Oct 20, 2025, 05:42 PM UTC

   Hi team, We’d like to inform you that AWS has reported that their mitigations to resolve launch failures for new EC2 instances are progressing, with internal EC2 subsystems showing early signs of recovery in several Availability Zones (AZs) within the US-EAST-1 Region. Mitigations are now being applied to the remaining AZs, and AWS expects launch errors and network connectivity issues affecting services such as DynamoDB, SQS, and Amazon Connect to gradually subside as recovery continues. We will continue to monitor AWS’s progress and provide further updates as more information becomes available. Thank you for your patience and understanding.

8. identified Oct 20, 2025, 07:44 PM UTC

   Hi Team, AWS has reported ongoing recovery across multiple Availability Zones in the US-EAST-1 Region. EC2 instance launches are now succeeding in most zones, and network connectivity issues affecting services such as DynamoDB, SQS, and Amazon Connect are gradually subsiding. For Lambda, customers may still experience intermittent function errors when functions make network requests to other services, as AWS continues to address residual connectivity issues. Steps such as adjusting SQS polling rates via Lambda Event Source Mappings are helping improve invocation success. We will continue to closely monitor the situation and share further updates as more information becomes available. Thank you for your patience and understanding.

9. identified Oct 20, 2025, 09:37 PM UTC

   Hi Team, We’d like to inform you that AWS has reported ongoing recovery across multiple Availability Zones (AZs) in the US-EAST-1 Region. EC2 instance launches are now succeeding in most zones, and network connectivity issues affecting DynamoDB, SQS, and Amazon Connect are gradually subsiding. For Lambda, intermittent function errors may still occur when making network requests, but queued events are being processed and full recovery is expected within the next two hours. Services dependent on EC2, such as ECS and Glue, will recover as instance launch rates improve. We are closely monitoring the situation and will share further updates as more information becomes available. Thank you for your patience and understanding.

10. resolved Oct 20, 2025, 11:36 PM UTC

    Hi Team, We’d like to inform you that the AWS network connectivity issues in the US-EAST-1 Region have now been resolved. Between 11:49 PM PDT on October 19 (Oct 20, 12:19 PM IST) and 2:24 AM PDT on October 20 (Oct 20, 2:54 PM IST), AWS experienced increased error rates and latencies across multiple services due to DNS resolution issues affecting regional DynamoDB endpoints, which subsequently impacted EC2, Lambda, and other dependent services. All affected AWS services have now returned to normal operations as of 3:01 PM PDT (Oct 21, 3:31 AM IST), and connectivity has been fully restored. Some services may continue processing residual backlogs, which AWS expects to clear shortly. However rest assured We will continue to monitor for continued stability. Please feel free to reach out to Sprinklr Support if you have any questions or need further assistance

Read the full incident report →

Started Oct 17, 2025, 02:45 PM UTC· resolved Oct 17, 2025, 02:59 PM UTC

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 →

Started Oct 14, 2025, 07:20 AM UTC· resolved Oct 14, 2025, 08:23 AM UTC

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 →

Started Oct 10, 2025, 06:57 AM UTC· resolved Oct 10, 2025, 08:46 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →