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

[georgesequeira]

At 2018-06-05 17:19 UTC

Running

while curl -I https://registry.yarnpkg.com/ ; do :; done

Shows intermittent 503s:

HTTP/2 200
date: Tue, 05 Jun 2018 17:13:51 GMT
content-type: text/plain
content-length: 4
set-cookie: __cfduid=dc18ec800fc64ed09ef1d844d6946fee61528218830; expires=Wed, 05-Jun-19 17:13:50 GMT; path=/; domain=.registry.yarnpkg.com; HttpOnly
cache-control: must-revalidate
cf-ray: 426445abfe7c2180-EWR
expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
server: cloudflare


HTTP/2 503
date: Tue, 05 Jun 2018 17:14:04 GMT
content-type: text/plain;charset=UTF-8
content-length: 28
set-cookie: __cfduid=d1ef1d891ac86c43ea1d759b1891cf9801528218831; expires=Wed, 05-Jun-19 17:13:51 GMT; path=/; domain=.registry.yarnpkg.com; HttpOnly
expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
server: cloudflare
cf-ray: 426445b129e421ce-EWR
...
....

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

Currently https://status.npmjs.org/ shows a healthy status.

[stringbeans]

i am also running into 503 errors occassionally when installing packages... for example:

[2/4] Fetching packages...
info If you think this is a bug, please open a bug report with the information provided in "/usr/src/app/yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
error An unexpected error occurred: "https://registry.yarnpkg.com/node-pre-gyp/-/node-pre-gyp-0.6.36.tgz: Request failed \"503 Service Unavailable\"".

[BYK]

Works for me here from London. CloudFlare shows some reroutes but says things are fine in general: https://www.cloudflarestatus.com/

Don't really know what might be happening.

[stringbeans]

strangely enough we are not experiencing the issues locally (we're in Vancouver Canada) but in our circleCI builds we're run into the 503 errors about 50% of the time

[Dog]

I'm having the same experience in Seattle.

[brianleach]

Getting 503 service unavailable on CircleCI.

#!/bin/bash -eo pipefail
cd www && yarn install
yarn install v0.24.4
[1/4] Resolving packages...
[2/4] Fetching packages...
error An unexpected error occurred: "https://registry.yarnpkg.com/spdy/-/spdy-3.4.7.tgz: Request failed \"503 Service Unavailable\"".

[anthonyroach]

I'm seeing the same problem on a Jenkins slave running in us-east-1 of AWS (Virginia). Interestingly, I do not see it when running locally from Indianapolis, IN:

yarn install v1.5.1
[1/4] Resolving packages...
[2/4] Fetching packages...
error An unexpected error occurred: "https://registry.yarnpkg.com/regl-error2d/-/regl-error2d-2.0.4.tgz: Request failed \"503 Service

[arist0tl3]

Confirmed on our CircleCI. Seems random, though I haven't seen the same package fail twice. Here are the latest three:

yarn install v0.24.4
[1/4] Resolving packages...
[2/4] Fetching packages...
error An unexpected error occurred: "https://registry.yarnpkg.com/babel-plugin-syntax-exponentiation-operator/-/babel-plugin-syntax-exponentiation-operator-6.13.0.tgz: Request failed \"503 Service Unavailable\"".
info If you think this is a bug, please open a bug report with the information provided in "/home/circleci/repo/yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
Exited with code 1

yarn install v0.24.4
[1/4] Resolving packages...
[2/4] Fetching packages...
error An unexpected error occurred: "https://registry.yarnpkg.com/pinkie-promise/-/pinkie-promise-2.0.1.tgz: Request failed \"503 Service Unavailable\"".
info If you think this is a bug, please open a bug report with the information provided in "/home/circleci/repo/yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
Exited with code 1

yarn install v0.24.4
[1/4] Resolving packages...
[2/4] Fetching packages...
error An unexpected error occurred: "https://registry.yarnpkg.com/map-keys-deep-lodash/-/map-keys-deep-lodash-1.2.0.tgz: Request failed \"503 Service Unavailable\"".
info If you think this is a bug, please open a bug report with the information provided in "/home/circleci/repo/server/yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
error Command failed with exit code 1.
Exited with code 1

[ahunter-tehama]

Same issue here:

yarn install v1.5.1
[1/4] Resolving packages...
[2/4] Fetching packages...
error An unexpected error occurred: "https://registry.yarnpkg.com/debug/-/debug-2.6.1.tgz: Request failed \"503 Service Unavailable\"".

yarn install v1.5.1
[1/4] Resolving packages...
[2/4] Fetching packages...
merror An unexpected error occurred: "https://registry.yarnpkg.com/raw-body/-/raw-body-2.2.0.tgz: Request failed \"503 Service Unavailable\"".

and so on intermittently

[BYK]

Reached out to CloudFlare, awaiting a response.

[bluepichu]

I've been having a similar issue in a BitBucket Pipeline, but interestingly, with the --verbose flag set yarn install _always_ succeeds. It seems like the added delay from all of the printing is preventing whatever the issue is from occurring.

[anthonyroach]

I was able to work around the problem and get rid of the 503s by changing https://registry.yarnpkg.com to https://registry.npmjs.org/ in yarn.lock. This suggests that the problem is not the npmjs registry, but rather the yarnpkg registry.

[BYK]

I was able to work around the problem and get rid of the 503s by changing https://registry.yarnpkg.com to https://registry.npmjs.org/ in yarn.lock. This suggests that the problem is not the npmjs registry, but rather the yarnpkg registry.

@anthonyroach that is very unlikely since they are both behind CloudFlare and point to the same servers. I'd say this is just coincidence.

[Dog]

I'm starting to see the failed builds resolving.

[DanielJoyce]

We currently have codeship builds failing due to this

2018-06-05 21:06:23
yarn install v1.5.1
2018-06-05 21:06:23
[1/4] Resolving packages...
2018-06-05 21:06:23
[2/4] Fetching packages...
2018-06-05 21:06:38
error An unexpected error occurred: "https://registry.yarnpkg.com/balanced-match/-/balanced-match-1.0.0.tgz: Request failed \"503 Service Unavailable\"".

[Dog]

FWIW I am no longer experiencing this.

All failed builds have passed, and no new failed builds yet.

[Gianfranco97]

I also have the same problem in my CircleCI integration, everything worked yesterday but today I let it work.

[1/4] Resolving packages...
[2/4] Fetching packages...
error An unexpected error occurred: "https://registry.yarnpkg.com/@sonarwhal/rule-http-compression/-/rule-http-compression-4.0.2.tgz: Request failed \"503 Service Unavailable\"".
info If you think this is a bug, please open a bug report with the information provided in "/root/repo/yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
Exited with code 1

[benjyblack]

We are experiencing this still from our CircleCI builds. --verbose does not help. It's happening 95% of the time.

error An unexpected error occurred: "https://registry.yarnpkg.com/pug-lexer/-/pug-lexer-4.0.0.tgz: Request failed \"503 Service Unavailable\"".

[luislezcair]

I'm experiencing the same problem when deploying to Heroku. It fails with random packages. It works fine locally.

Also, the registry status says it was last updated on May 25th: https://status.yarnpkg.com/

[geropl]

We experience the same issue every other day, always around 3-5pm CET, in our own Jenkins-on-Docker build pipeline.
Any robust work around?

[wichert]

We're seeing this happen 100% of the time as of today with requests coming from CircleCI.

[zwade]

Following up on this, we've been having the same issue running both locally (under Docker) and on Bitbucket's pipelines. Solving the local issue, we found that the error only occurred when performing multiple parallel installs and that building them in sequence was sufficient to prevent 503's. I'm not sure this helps, but it backs up what @bluepichu was saying about needing to slow the install down.

[Ponjimon]

Same issue, our GitLab runner runs on AWS.

[ganglio]

I'm experiencing the same issue in London. Building from the Docker container fails while building locally works.

[WebMex]

The same issue for our Gitlab runner in Frankfurt. Verbose didn't help

[yv3s]

Having the same issue in Paris

[2/4] Fetching packages... remote: error An unexpected error occurred: "https://registry.yarnpkg.com/uglifyjs-webpack-plugin/-/uglifyjs-webpack-plugin-1.2.3.tgz: Request failed \"503 Service Unavailable\"". remote: info If you think this is a bug, please open a bug report with the information provided in "/tmp/build_3466b5d056c6bb38c5e354a0a5942555/yarn-error.log". remote: info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

[tjbrez]

Seeing the same issue in Cleveland. Works locally, but CircleCI fails 90% of the time.

[HoughIO]

An unexpected error occurred: \"https://registry.yarnpkg.com/css-select/-/css-select-1.2.0.tgz: Request failed \\\"503 Service Unavailable

As of 11:00AM EST 6/6/2018

Various packages fail in no particular order.

[rvirani1]

We're getting this same error most of the time running in Amazon CodeBuild in us-east-1

[DanielJoyce]

Outage resolved for us for now.

[jayschwa]

We're still getting this error in Amazon's us-west-2.

[yv3s]

Resolved in France too

Yves

Le 6 juin 2018 à 17:13, Jay Weisskopf [e-mail] a écrit :

We're still getting this error in Amazon's us-west-2.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

[StasDachinsky]

The same with circleCi :(

[efournival]

Still not resolved under CircleCI:

yarn install v1.5.1
[1/4] Resolving packages...
[2/4] Fetching packages...
error An unexpected error occurred: "https://registry.yarnpkg.com/chalk/-/chalk-2.4.1.tgz: Request failed \"503 Service Unavailable\"".
info If you think this is a bug, please open a bug report with the information provided in "/root/moonapp/yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
Exited with code 1

[rufushonour]

npm are now publicly acknowledging the issue: https://status.npmjs.org/incidents/qxj3kdzw4jrg

[draconteus]

Temporarily changing to NPM and https://registry.npmjs.org/ can solve the problem.

[wcmonty]

We added some retry logic in our build processes:

for i in {1..4}; do yarn install && break; done && yarn install

We try to install up to 4 times, then install a final time to make sure that we return the right status code.

[leff]

NPM says they fixed it but we're still seeing 503 errors from registry.yarnpkg.com

[rvirani1]

We're still seeing issues as well.

[leff]

I tried replacing registry.yarnpkg.com with registry.npmjs.org in my yarn.lock file. The build has gotten past the yarn install step. I suspect registry.yarnpkg.com is caching the error responses.

[hemp]

npmjs incident has been updated to resolved: https://status.npmjs.org/incidents/qxj3kdzw4jrg

[edarblanco]

Oh why does this happen? again this is happening, error 503, don't install packages

[synalysis]

I was able to resolve the issue locally by leaving the VPN connection (IPVanish).

But when deploying to zeit.co I had it again. Annoying.

[johnnyreilly]

I'm completely out of action due to this. So frustrating.

[andrjuha01]

Same in Ukraine right now.

[jimitpatel]

I was able to work around the problem and get rid of the 503s by changing https://registry.yarnpkg.com to https://registry.npmjs.org/ in yarn.lock. This suggests that the problem is not the npmjs registry, but rather the yarnpkg registry.

Worked for me like a charm... I am behind proxy. I replaced those link with proxy links... I had to change it eventhough I have changed it via npm config set registry