ETIMEDOUT error when building NodeJS project

I’ve tried a deploy locally and using the remote builder and I get the same issue. I am not entirely sure if this is a fly.io-specific problem, but wanted to post here to be sure. Attached are the deploy logs that I’m getting. I am able to get the URL https://registry.npmjs.org/xpath.js/-/xpath.js-1.1.0.tgz manually through my browser even though NPM is not able to get it.

Run "fly version update" to upgrade.
==> Verifying app config
Remote builder fly-builder-autumn-bird-1737 ready
==> Building image with BuildpacksWWWWWWWWWWWWWWWWWWWWWWWWWWW 
--> docker host: 20.10.12 linux x86_64WWWWWWWWWWWWWWWWWWWWWWW 
20: Pulling from heroku/buildpacksWWWWWWWWWWWWWWWWWWWWWWWWWWW 
Digest: sha256:e2235fe9ce4e834c8294abfb9d44546a55c68dacd0f64d5ad990a69ce75d732f
Status: Image is up to date for heroku/buildpacks:20WWWWWWWWW 
20-cnb: Pulling from heroku/herokuWWWWWWWWWWWWWWWWWWWWWWWWWWW 
Digest: sha256:b323808b41c13adafdeb0b546fe7fddeafe5695f573c1a3bd1e3aa5c3586b462
Status: Image is up to date for heroku/heroku:20-cnbWWWWWWWWW 
===> DETECTINGWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW 
2 of 3 buildpacks participatingWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW 
heroku/nodejs-engine 0.8.7WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW 
heroku/nodejs-npm    0.5.2
===> ANALYZING
Previous image with name "registry.fly.io/...:cache" not found
===> RESTORING
===> BUILDING

[Heroku Node.js Engine Buildpack]

[Checking Node.js version]
Detected Node.js version range: >=12.0.0
Resolved Node.js version: 18.5.0

[Installing Node.js distribution]
Downloading Node.js 18.5.0
Extracting Node.js 18.5.0
Installing Node.js 18.5.0
[INFO] Installing toolbox
[INFO] - yj
[INFO] Using npm v8.12.1 from Node
[INFO] Installing node modules from ./package-lock.json
npm WARN config production Use `--omit=dev` instead.
npm ERR! code ETIMEDOUT
npm ERR! syscall connect
npm ERR! errno ETIMEDOUT
npm ERR! network request to https://registry.npmjs.org/xpath.js/-/xpath.js-1.1.0.tgz failed, reason: connect ETIMEDOUT 2606:4700::6810:1123:443
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 ERR! A complete log of this run can be found in:
npm ERR!     /home/heroku/.npm/_logs/2022-08-30T20_00_32_654Z-debug-0.log