ERR_SOCKET_TIMEOUT in Tokyo when installing @sls-next/serverless-component@3.7.0

[saadataz]

We have AWS EC2 build instances running in multiple regions using npm install.

Since 09/12/2023 at 12:46 UTC, we are seeing about 50% of the installs failing due to ERR_SOCKET_TIMEOUT error.

This is only happening in servers running in Tokyo, Japan when running npm install @sls-next/serverless-component@3.7.0.
What is strange is that it is only happening for this particular version of the package. npm install @sls-next/serverless-component@3.6.0 works fine.

NPM status page is not showing any issues https://status.npmjs.org/

Verbose logs:

npm http fetch GET 200 https://registry.npmjs.org/source-map/-/source-map-0.6.1.tgz 12145ms (cache miss)
npm http fetch GET 200 https://registry.npmjs.org/buffer/-/buffer-4.9.2.tgz 12039ms (cache miss)
npm http fetch GET 200 https://registry.npmjs.org/buffer/-/buffer-4.9.2.tgz 12033ms (cache miss)
npm http fetch GET 200 https://registry.npmjs.org/buffer/-/buffer-4.9.2.tgz 12030ms (cache miss)
npm http fetch GET 200 https://registry.npmjs.org/buffer/-/buffer-4.9.2.tgz 12016ms (cache miss)
npm http fetch GET 200 https://registry.npmjs.org/buffer/-/buffer-4.9.2.tgz 12030ms (cache miss)
npm http fetch GET 200 https://registry.npmjs.org/buffer/-/buffer-4.9.2.tgz 12023ms (cache miss)
npm http fetch GET 200 https://registry.npmjs.org/fs-extra/-/fs-extra-7.0.1.tgz 12012ms (cache miss)
npm http fetch GET 200 https://registry.npmjs.org/buffer/-/buffer-4.9.2.tgz 12018ms (cache miss)
npm http fetch GET 200 https://registry.npmjs.org/buffer/-/buffer-4.9.2.tgz 12025ms (cache miss)
npm http fetch GET 200 https://registry.npmjs.org/fs-extra/-/fs-extra-7.0.1.tgz 12013ms (cache miss)
npm http fetch GET 200 https://registry.npmjs.org/fs-extra/-/fs-extra-7.0.1.tgz 11984ms (cache miss)
npm http fetch GET 200 https://registry.npmjs.org/semver/-/semver-7.5.4.tgz 11968ms (cache miss)
npm http fetch GET 200 https://registry.npmjs.org/fast-glob/-/fast-glob-2.2.7.tgz 12095ms (cache miss)
npm http fetch GET 200 https://registry.npmjs.org/@aws-sdk/types/-/types-3.410.0.tgz 12119ms (cache miss)
npm http fetch GET 200 https://registry.npmjs.org/@babel/types/-/types-7.15.0.tgz 12446ms (cache miss)
npm http fetch GET 200 https://registry.npmjs.org/async/-/async-2.6.4.tgz 12209ms (cache miss)
npm http fetch GET 200 https://registry.npmjs.org/async/-/async-2.6.4.tgz 12177ms (cache miss)
npm http fetch GET 200 https://registry.npmjs.org/@serverless/aws-s3/-/aws-s3-1.0.1.tgz 12231ms (cache miss)
npm http fetch GET 200 https://registry.npmjs.org/ramda/-/ramda-0.27.1.tgz 12857ms (cache miss)
npm http fetch GET 200 https://registry.npmjs.org/ramda/-/ramda-0.27.1.tgz 12852ms (cache miss)
npm http fetch GET 200 https://registry.npmjs.org/ramda/-/ramda-0.27.1.tgz 12857ms (cache miss)
npm http fetch GET 200 https://registry.npmjs.org/@aws-sdk/client-s3/-/client-s3-3.54.0.tgz 13153ms (cache miss)
npm http fetch GET 200 https://registry.npmjs.org/@sls-next%2fcore 6099ms (cache miss)
npm http fetch GET 200 https://registry.npmjs.org/@sls-next%2flambda-at-edge 6274ms (cache miss)
npm http fetch GET 200 https://registry.npmjs.org/fast-glob 48ms (cache miss)
npm http fetch GET 200 https://registry.npmjs.org/@aws-sdk%2fclient-sts 122ms (cache miss)
npm http fetch GET 200 https://registry.npmjs.org/@aws-sdk%2fclient-s3 210ms (cache miss)
npm http fetch GET 200 https://registry.npmjs.org/@aws-sdk%2fclient-sqs 1410ms (cache miss)
npm http fetch GET 200 https://registry.npmjs.org/package-json 31ms (cache miss)
npm http fetch GET 200 https://registry.npmjs.org/styled-jsx 586ms (cache miss)
npm http fetch GET 200 https://registry.npmjs.org/@next%2freact-dev-overlay 1003ms (cache miss)
npm http fetch GET 200 https://registry.npmjs.org/terser-webpack-plugin 67ms (cache miss)
npm http fetch GET 200 https://registry.npmjs.org/aws-sdk/-/aws-sdk-2.1093.0.tgz 16771ms (cache miss)
npm http fetch GET 200 https://registry.npmjs.org/aws-sdk/-/aws-sdk-2.1093.0.tgz 16815ms (cache miss)
npm http fetch GET 200 https://registry.npmjs.org/aws-sdk/-/aws-sdk-2.1093.0.tgz 16827ms (cache miss)
npm http fetch GET 200 https://registry.npmjs.org/aws-sdk/-/aws-sdk-2.1093.0.tgz 16817ms (cache miss)
npm http fetch GET 200 https://registry.npmjs.org/@next%2freact-refresh-utils 1401ms (cache miss)
npm http fetch GET 200 https://registry.npmjs.org/aws-sdk 52ms (cache miss)
npm http fetch GET 200 https://registry.npmjs.org/@sls-next%2faws-common 1351ms (cache miss)
npm http fetch GET 200 https://registry.npmjs.org/globby 24ms (cache miss)
npm http fetch GET 200 https://registry.npmjs.org/@serverless%2fcore 1334ms (cache miss)
npm http fetch GET 200 https://registry.npmjs.org/@sls-next%2faws-cloudfront 855ms (cache miss)
npm http fetch GET 200 https://registry.npmjs.org/@sls-next%2fdomain 1239ms (cache miss)
npm http fetch GET 200 https://registry.npmjs.org/@serverless%2faws-lambda-layer 1429ms (cache miss)
npm http fetch GET 200 https://registry.npmjs.org/@sls-next%2faws-lambda 1452ms (cache miss)
npm http fetch GET 200 https://registry.npmjs.org/@sls-next%2faws-sqs 1464ms (cache miss)
npm http fetch GET 200 https://registry.npmjs.org/@sls-next%2faws-s3 1467ms (cache miss)
npm http fetch GET 200 https://registry.npmjs.org/@sls-next%2fcloudfront 1474ms (cache miss)
npm http fetch GET 200 https://registry.npmjs.org/@serverless%2faws-s3 1499ms (cache miss)
npm http fetch GET 200 https://registry.npmjs.org/@sls-next%2fs3-static-assets 1519ms (cache miss)
npm http fetch GET 200 https://registry.npmjs.org/@serverless%2faws-iam-role 1591ms (cache miss)
npm verb stack Error: Socket timeout
npm verb stack     at TLSSocket.onTimeout (/home/ec2-user/.nvm/versions/node/v18.17.1/lib/node_modules/npm/node_modules/agentkeepalive/lib/agent.js:346:23)
npm verb stack     at TLSSocket.emit (node:events:526:35)
npm verb stack     at Socket._onTimeout (node:net:571:8)
npm verb stack     at listOnTimeout (node:internal/timers:569:17)
npm verb stack     at process.processTimers (node:internal/timers:512:7)
npm verb cwd /home/ec2-user
npm verb Linux 6.1.49-69.116.amzn2023.x86_64
npm verb node v18.17.1
npm verb npm  v9.6.7
npm ERR! code ERR_SOCKET_TIMEOUT
npm ERR! network Socket timeout
npm ERR! network This is a problem related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network 
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly.  See: 'npm help config'
npm verb exit 1
npm verb unfinished npm timer command:install 1694543058084
npm verb unfinished npm timer reify 1694543058089
npm verb unfinished npm timer reify:unpack 1694543060389
npm verb unfinished npm timer reifyNode:node_modules/@sls-next/s3-static-assets/node_modules/aws-sdk 1694543060494
npm verb unfinished npm timer reifyNode:node_modules/@sls-next/aws-s3/node_modules/aws-sdk 1694543060497
npm verb unfinished npm timer reifyNode:node_modules/@sls-next/aws-lambda/node_modules/aws-sdk 1694543060497
npm verb code 1