Update: 8:24 AM UTC - We have resolved the issue, thank you for being patient!
Update: 8:06 AM UTC - We have identified the issue and are attempting to fix it.
We are investigating an issue with one of our cache servers and our team is working to resolve it as soon as possible.