A configuration change led to errors noticed by some clients. The request headers were blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
We've investigated and found the root cause. This incident has been resolved.