📣 Service notice – 12 June 2025

announcements
1

At 14:54 EDT we rolled the forums back to our last snapshot.

The reason:

Today’s Discourse upgrade stalled when pnpm couldn’t pull packages from the public npm registry. The registry is front-ended by Cloudflare, and Cloudflare is having issues right now—which means the mirror we rely on is returning 503 Service Unavailable for many tarballs.

  • npm status page is tracking the incident – “Issues with package install, package publish, and login” (opened 18:14 UTC). status.npmjs.org
  • Cloudflare is simultaneously doing maintenance and reporting sporadic outages. cloudflarestatus.com

Because the package fetch failed mid-upgrade, Discourse couldn’t finish boot-strapping. Rather than leave the forums offline, I restored a VM backup. The forum is fully operational again; you might notice that **one or two posts or reactions made between have disappeared—that’s all we lost.

Later…

  1. I’ll wait until npm shows “All systems operational” or Cloudflare’s edges calm down.
  2. I’ll rerun the upgrade.
  3. If you’re curious (or just like outage-watching) you can refer to general internet news. This is a big one!

No action needed on your side. Thanks!

2 Likes
2

I have to mark this red in the calendar, the “half” Internet is out but the Microsoft services have worked :rofl:

3 Likes
3

Back online:

1 Like
4

Cloudflare is simultaneously doing maintenance and reporting sporadic outages.cloudflarestatus.com

You accidentally forgot a space between “outages.” and the url itself. Meaning it links to a subdomain, so clicking it will lead to a nonexistant url. Just thought I wanted to let you know. :smiley:

1 Like
5

Glad you are successful in getting things back.

Thank you for the work behind the scenes! :slightly_smiling_face:

3 Likes
6

GET GUINNESS!!! This is one for the record books. :rofl: :rofl: :rofl: :rofl:

1 Like
7

Today MS has delivered. For some customers, MFA was not possible for anyone…