Frends Outage History
Frends degraded View live status →Pingoru has recorded 1 incident for Frends: 1 in the last 12 months and 1 in the last 90 days.
Incidents, newest first
Minor October 29, 2026 Remote Subprocess execution and Agent configuration updates failing due to Azure Service Bus issue 11h
Started Oct 29, 2026, 05:00 AM UTC· resolved Oct 29, 2026, 04:00 PM UTC
- investigating Oct 29, 2026, 05:00 AM UTC
We are investigating an issue affecting Remote Subprocess execution and configuration changes delivered to Frends Agents, such as environment variable updates, process deployments, process activations and deactivations, and API policy changes. The issue started at approximately 05:00 UTC (07:00 Finnish time). Processes already deployed on your Agents continue to run normally, and monitoring is unaffected. The cause is a change in Microsoft Azure Service Bus, which has started rejecting authentication tokens that Microsoft’s own documentation states are valid. There have been no changes to Frends or to customer configurations. We have opened a critical support case with Microsoft and are waiting for their response. A temporary workaround is available. Contact [email protected] for a replacement Agent access token and instructions for applying it. Next update at 15:00 Finnish time (13:00 UTC), or sooner if the issue is resolved.
- monitoring Oct 29, 2026, 10:31 AM UTC
We are now automatically applying a workaround to all Frends Cloud Agents (hosted by Frends). Each Agent will have a very short service break while it is updated. Full functionality is restored as soon as the update completes, and no action is needed from customers using these Agents. Customers running on-premise or self-hosted Agents need to apply the fix manually to restore full platform functionality. We will contact each of these customers separately with step-by-step guidance. If you need help sooner, please contact [email protected]. As before, processes already deployed continue to run normally and monitoring is unaffected. The root cause is a change in Microsoft Azure, and our critical support case with Microsoft remains open. Next update at 15:00 Finnish time (13:00 UTC), or sooner if the situation changes.
- monitoring Oct 29, 2026, 02:53 PM UTC
The workaround has been applied to all Frends Cloud Agents (hosted by Frends), and they are fully operational again. Customers using only Frends Cloud Agents need to take no action. For on-premise and self-hosted Agents, we are now sending each affected customer a fix package prepared for their organisation, together with instructions for updating their Agents. Until an Agent is updated, Remote Subprocess execution and configuration changes, such as deployments, will not reach it. Processes already deployed continue to run normally. If you have on-premise Agents and need help, please contact [email protected]. Microsoft has acknowledged the issue as a defect in Azure Service Bus and is investigating how to revert the change.
- monitoring Oct 29, 2026, 06:25 PM UTC
This incident is now resolved from Frends’ side. All Frends Cloud Agents (hosted by Frends) are fully operational with a temporary workaround in place. Every customer we have identified as running on-premise or self-hosted Agents has received a fix package for their tenant, with instructions for applying it. If you have on-premise Agents that are still affected, or you have not received your fix package, please contact [email protected]. Microsoft has partly acknowledged the issue as a defect in Azure Service Bus and is working on reverting the change or providing us with a path to normal operations. We will continue to monitor the situation and will let customers know when the workaround can be removed. A detailed incident report, including Microsoft’s explanation and our root cause analysis, will follow. We apologise for the disruption and thank you for your patience.