Thanks for letting us know!

We have been seeing this issue internally as well, and we believe it stems from one of our back-end dependencies. It has been under investigation, and we'll update you as soon as we have more information available.