Resolved -
Azure has resolved the issue on their side, and monitoring was successful overnight. If there are any reports of issues with Conversations during the issue that aren't resolved now, then please open a support ticket with Validic technical support with the specifics so we can assist further. We appreciate your patience on this matter.
Oct 30, 09:14 EDT
Monitoring -
Azure is reporting that they are observing recovery. Validic is monitoring
We have completed deployment of our ‘last known good’ configuration, and recovery is progressing steadily. We are currently recovering nodes and re-routing traffic through healthy nodes across the global fleet. As recovery continues, some requests may still land on unhealthy nodes, resulting in intermittent failures or reduced availability for a subset of customers.
This recovery effort involves reloading configurations and rebalancing traffic across a large number of nodes to restore full operational scale. The process is gradual by design, ensuring stability and preventing overload as dependent services recover.
The AFD service is now operating above 98% availability. While the majority of customers and services are mitigated or seeing strong improvement across affected regions, we are continuing to work on tail-end recovery for remaining impacted customers and services. We have revised our mitigation time and are currently tracking toward full mitigation by 00:40 UTC on 30 October 2025, though we will communicate if mitigation is achieved sooner.
Customer configuration changes remain temporarily blocked to prevent new deployments that could interfere with recovery. We will notify customers once this block has been lifted.
We will provide another update on our progress within the next 60 minutes, or sooner if warranted.
This message was last updated at 23:40 UTC on 29 October 2025"
Oct 29, 19:49 EDT
Identified -
Azure updated its status page with this. That translates to 7:20 PM EST on their target for full recovery. Text from their status page below https://azure.status.microsoft/en-us/status
"Azure Front Door - Connectivity issues - Observing recovery
Starting at approximately 16:00 UTC on 29 October, 2025, customers and Microsoft services leveraging Azure Front Door (AFD) may have experienced latencies, timeouts, and errors. We have confirmed that an inadvertent configuration change was the trigger event for this issue.
Current status:
We initiated the deployment of our ‘last known good’ configuration, which has now successfully been completed. Customers may have begun to see initial signs of recovery. We are currently recovering nodes and routing traffic through healthy nodes, and as we make progress in this workstream, customers will continue to see improvement.
Customer configuration changes will remain temporarily blocked while we continue mitigation efforts. We will notify customers once this block has been lifted.
Some customers may also have experienced issues accessing the Azure management portal. We have failed the portal away from AFD to mitigate these access issues. Customers should now be able to access the Azure portal directly, and while most portal extensions are functioning as expected, a small number of endpoints (e.g., Marketplace) may still experience intermittent loading problems.
At this stage, we anticipate full mitigation within the next four hours as we continue to recover nodes. This means we expect recovery to happen by 23:20 UTC on 29 October 2025. We will provide another update on our progress within two hours, or sooner if warranted.
Although we are seeing signs of recovery and have an estimated timeline, customers may also consider implementing existing failover strategies using Azure Traffic Manager to redirect traffic from Azure Front Door to their origin servers as an interim measure.
That is used to power the Impact Conversations. There will be performance issues with Conversations until the issue on the Azure side is resolved. This status page will be updated as recovery progresses for Azure.
Oct 29, 13:44 EDT
Resolved -
AWS has resolved its issues. We appreciate your patience if your experience with Impact was affected by the AWS issues yesterday
Oct 21, 10:16 EDT
Monitoring -
AWS had an issue overnight and they are still in the process of recoveriing. The affected region does appear to be where KP's prod Impact is housed. This could generate performance issues with our product. We're monitoring. AWS status page: https://health.aws.amazon.com/health/status
Oct 20, 09:34 EDT
