We've tracked down the issue and have identified the root cause as originating from our upstream infrastructure provider's APIs being down.
This is causing any provisioning of new nodes, both during new cluster provisioning and during configuration changes, to be affected.
Existing clusters that are already provisioned and running are unaffected.
We are closely monitoring the upstream issue and will post updates as a fix is being worked on.
