Issue is here: <a href="https://github.com/yarnpkg/yarn/issues/5885" rel="nofollow">https://github.com/yarnpkg/yarn/issues/5885</a><p>The problem is that npm just migrated their registry to use CloudFlare. Yarn already used CloudFlare, and had <a href="https://registry.yarnpkg.com" rel="nofollow">https://registry.yarnpkg.com</a> CNAME'd to <a href="https://registry.npmjs.org" rel="nofollow">https://registry.npmjs.org</a>. CloudFlare has a security restriction that one CloudFlare account cannot have DNS records pointing to another CloudFlare account, so npm moving to CloudFlare broke yarn's existing CNAME to npm's registry (thus breaking yarn).
"We (aka npm) are in contact with Cloudflare to get this third-party CNAME allowed. I'll update this thread when I hear back." (via [0])<p>More status on the Github issue [0] than yarn status page [1]<p>[0]: <a href="https://github.com/yarnpkg/yarn/issues/5885#issuecomment-392212653" rel="nofollow">https://github.com/yarnpkg/yarn/issues/5885#issuecomment-392...</a><p>[1]: <a href="https://status.yarnpkg.com/" rel="nofollow">https://status.yarnpkg.com/</a>
They had other issues earlier this week too. Doesn't help that their status page hasn't been updated in a year :D <a href="https://twitter.com/trentbillington/status/998822168036167680" rel="nofollow">https://twitter.com/trentbillington/status/99882216803616768...</a>.