registry.yarnpg.com is down, but status.yarnpkg.com is green

[OlafMerkert]

At 2018-05-22 09:22:01+02:00,

registry.yarnpg.com returns the following error message:

Error 503 No healthy backends
No healthy backends

Guru Mediation:
Details: cache-fra19124-FRA 1526973594 170258232

Varnish cache server

But status.yarnpkg.com lists the registry as operational.

[CzarScar]

I also struggled with this error. Please help us?

[neilstudd]

Looks to be due to degraded performance on NPM's side: https://status.npmjs.org/

Edit: NPM fix implemented and Yarn has returned to normal for me

[OlafMerkert]

But there also seems to be an issue with the status page? It should show the correct status of the registry when it is not reachable?

[neilstudd]

Agreed - although this particular incident is resolved, it should have been showing problems on the Yarn status page even if the problem originated upstream.

[hielfx]

I still got this problem; yarn add fails but npm install works fine. The yarn registry site still shows a 503 with guru meditation

[zacblazic]

Looks down again, possibly due to NPM:

[pariola]

Seems down!

[arcanis]

https://twitter.com/yarnpkg/status/1035896058616991744

We're aware of connectivity issues when accessing the registry. We believe they are caused by a dns resolution problem that affected npm - it should resolve once the various dns caches get cleared. More info at https://status.npmjs.org/

More generally speaking, if you see the registry going down, it's highly unlikely the problem comes from us, and even more unlikely we can do anything about it, since we don't maintain an full mirror.

[pariola]

Oh, thanks!

[zhuangya]

sorry to bring this up, but:

error An unexpected error occurred: "https://registry.yarnpkg.com/@fortawesome/free-solid-svg-icons/-/free-solid-svg-icons-5.6.0.tgz: Request failed \"500 Internal Server Error\"".

anything wrong with yarnpkg now?

[arcanis]

More generally speaking, if you see the registry going down, it's highly unlikely the problem comes from us, and even more unlikely we can do anything about it, since we don't maintain an full mirror.

[OlafMerkert]

To clarify: this issue is not about the yarn registry being down because the npm registry is down. Obviously, if the yarn registry is just a mirror, then not much can be done about this.

My suggestion is however to make this more transparent on http://status.yarnpkg.com. The fact that the yarn registry is a mirror may not be obvious to every user. I noticed that there is currently a tooltip on the status page, but perhaps something even more prominent would be helpful?

Or even better, the status page could link to npmjs status page?

[GuiSim]

I guess this could be closed now, http://status.yarnpkg.com doesn't seem to exist anymore.

[merceyz]

#8231 (comment)