UPDATE: Cloudflare outage! - Discourse update to "3.5.0.beta6" failed

Edit: I tried testing with curl. This works:

curl -I https://registry.npmjs.org/
HTTP/2 200 
date: Thu, 12 Jun 2025 18:26:56 GMT
content-type: application/json
cache-control: public, immutable, max-age=31557600
set-cookie: _cfuvid=...-0.0.1.1-604800000; path=/; domain=.npmjs.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 94eb6640d930ac93-YYZ

But this and others fail with 503 error:

curl -I https://registry.npmjs.org/@swc/core/-/core-1.12.0.tgz
HTTP/2 503 
date: Thu, 12 Jun 2025 18:27:36 GMT
content-type: application/json
set-cookie: _cfuvid=...-0.0.1.1-604800000; path=/; domain=.npmjs.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 94eb664ced5cabe8-YYZ

Edit 2: Is the issue related to npmjs.org having issues with package install, package publish, and login?: also see: https://status.npmjs.org/

1 Like

ha! :smile: Talk about timing! Looks like, coincidentally, Cloudflare is having issues right now: https://www.cloudflarestatus.com/

My update request was about ~5 mins when this issue started. Argg.

Question, when this is resolved will ./launcher rebuild app be able to complete the upgrade? Anything additional I need to be aware of?

Update: This is a pretty big outage. AWS impacted, Google Cloud, Etsy, Google Drive, Mailchimp, etc. etc. etc. :popcorn:

I revert VM to a backup if this is extended.

Back online:

4 Likes

Oh my gosh Really CF?

Disabling reverse proxy helped me to rebuild… I guess.

@edit For some reason I not getting rebuild without put to skip mac address

./launcher rebuild app --skip-mac-address

1 Like

Nice. Well, actually everything was restored a while now:

**Update** - Cloudflare services are recovering quickly around the globe...
@Jun 12, 2025 - 20:32 UTC

In my case, the same curl test I ran earlier, started working again, so I just updated successfully also:

$ curl -I https://registry.npmjs.org/@swc/core/-/core-1.12.0.tgz
HTTP/2 200 
date: Thu, 12 Jun 2025 21:27:27 GMT
content-type: application/octet-stream
cf-ray: 94ec6eabdf84a21d-YYZ
cf-cache-status: HIT
...

Now I ended up on 3.5.0.beta7-dev :wink:

2 Likes

I guess not. That rebuild failed because registry.npmjs.org is fronted by CF. There was nothing you could do - except wait for it to recover.

4 Likes