A fix has been implemented and we are monitoring the results.
Posted Jun 10, 2025 - 23:00 BST
Update
From Salesforce: "We’ve restarted Heroku’s internal platform apps and are actively monitoring to confirm whether the issue is resolved. However, errors are resurfacing. We suspect a recent configuration change as the likely trigger and are working to revert it. In parallel, we’re developing an expedited rollout strategy and safeguards to prevent the recurrence of this config change."
Posted Jun 10, 2025 - 16:54 BST
Update
Salesforce have provided an update https://status.salesforce.com/generalmessages/10001540 "We have restarted a subset of our Heroku instances. This has shown positive results for the impacted services. We are working to restart the rest of the Heroku instances to fully restore the services. We are continuing to validate and closely monitor the services. Some customers are seeing improvements while accessing their services; however, the current impact still remains. Further investigations highlighted that an automated change on the Heroku environment was the potential trigger of this issue. The network configuration change, which was performed earlier, did not show any improvements."