MuleSoft service disruption

We have identified the trigger for this incident as a recent network-level change that was blocking external traffic, and we are proceeding with a staggered rollback to resolve it.

We’ll provide another update as additional information becomes available.

We’re investigating the cause of the issue. We will provide an update in 30 minutes or sooner if we have more information.

Investigations have highlighted that the impact radius is narrower than initially understood. We will now remove any instances that have not experienced an impact, and these will no longer receive communications about this incident going forward. Impacted instances will continue to be updated. We apologize for any inconvenience caused.