Invoke-PnPSiteTemplate AND Set-PnPDefaultColumnValues error since this morning

Since this morning we experience a blocking issue with Invoke-PnPSiteTemplate cmdlet which is failing as soon as there are lists included in a pnp site template (which is pretty much every template in our case). We see this behaviour on all of our own tenants and all customer tenants.

This is a very important part of our provioning engine so it's blocking all new sites & teams in all tenants.

Context
We have a provisioning engine that runs in Azure. It automatically creates SharePoint-sites and applies a configured PnP site template (either .pnp or .xml)

Expected behavior
Normally, the template gets applied correctly without any error

Actual behavior
An error occurs in our logging, also visible when reproducing this locally:

Error applying default column values
Microsoft.SharePoint.Client.ServerException: Exception of type 'Microsoft.SharePoint.Client.ServiceUnavailableException' was thrown.
Microsoft.SharePoint.Client.ClientRequest.ProcessResponseStream(Stream responseStream)

StackTrace: at Microsoft.SharePoint.Client.ListExtensions.SetDefaultColumnValuesImplementation(List list, IEnumerable1 columnValues) at Microsoft.SharePoint.Client.ListExtensions.SetDefaultColumnValues(List list, IEnumerable1 columnValues, Boolean overwriteExistingDefaultColumnValues) at PnP.Framework.Provisioning.ObjectHandlers.ObjectListInstance.ProvisionObjects(Web web, ProvisioningTemplate template, TokenParser parser, ProvisioningTemplateApplyingInformation applyingInformation) at PnP.Framework.Provisioning.ObjectHandlers.SiteToTemplateConversion.ApplyRemoteTemplate(Web web, ProvisioningTemplate template, ProvisioningTemplateApplyingInformation provisioningInfo, Boolean calledFromHierarchy, TokenParser tokenParser) at CallSite.Target(Closure , CallSite , Object , Object , Object , Object )

Steps to reproduce behavior
Create a PnP template
Apply the template, using invoke-pnpsitetemplate -Path "..."

We also see the same error happening when executing this cmdlet:
Set-PnPDefaultColumnValues -List "Documents" -Field Status -Value "MyDefaultValue" -Connection $pnpConnTargetSite

So it seems related...

anyone getting the same issues?