This incident has been resolved.
The issue was a bug in latest release affecting about 20% of pro-customers and caused the client API to return 401 also for valid client tokens.
In most cases this will not affect the SDK as it remains a cached version of the configuration.