Issue with platform URLs

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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

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.

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.