Yarn registry was down

Issue is here: <a href="https:&#x2F;&#x2F;github.com&#x2F;yarnpkg&#x2F;yarn&#x2F;issues&#x2F;5885" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;yarnpkg&#x2F;yarn&#x2F;issues&#x2F;5885</a><p>The problem is that npm just migrated their registry to use CloudFlare. Yarn already used CloudFlare, and had <a href="https:&#x2F;&#x2F;registry.yarnpkg.com" rel="nofollow">https:&#x2F;&#x2F;registry.yarnpkg.com</a> CNAME&#x27;d to <a href="https:&#x2F;&#x2F;registry.npmjs.org" rel="nofollow">https:&#x2F;&#x2F;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&#x27;s existing CNAME to npm&#x27;s registry (thus breaking yarn).

And that’s why you never do an infrastructure change EOD Friday before Memorial Day weekend.

&quot;We (aka npm) are in contact with Cloudflare to get this third-party CNAME allowed. I&#x27;ll update this thread when I hear back.&quot; (via [0])<p>More status on the Github issue [0] than yarn status page [1]<p>[0]: <a href="https:&#x2F;&#x2F;github.com&#x2F;yarnpkg&#x2F;yarn&#x2F;issues&#x2F;5885#issuecomment-392212653" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;yarnpkg&#x2F;yarn&#x2F;issues&#x2F;5885#issuecomment-392...</a><p>[1]: <a href="https:&#x2F;&#x2F;status.yarnpkg.com&#x2F;" rel="nofollow">https:&#x2F;&#x2F;status.yarnpkg.com&#x2F;</a>

They had other issues earlier this week too. Doesn&#x27;t help that their status page hasn&#x27;t been updated in a year :D <a href="https:&#x2F;&#x2F;twitter.com&#x2F;trentbillington&#x2F;status&#x2F;998822168036167680" rel="nofollow">https:&#x2F;&#x2F;twitter.com&#x2F;trentbillington&#x2F;status&#x2F;99882216803616768...</a>.

The official NPM registry isn&#x27;t fairing well, either: <a href="https:&#x2F;&#x2F;github.com&#x2F;npm&#x2F;npm&#x2F;issues&#x2F;20766" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;npm&#x2F;npm&#x2F;issues&#x2F;20766</a>

depending on npm is scary &gt;.&lt;