Add incident report for April 1st

incidents/2026-04-01.md

@@ -0,0 +1,42 @@
+# 2025-04-01 Incident Report
+
+- Incident Commander: @MattIPv4
+- Severity Level: P2
+
+For a brief period of time, the downloads page was blank due to a false assumption on their always being a Current version of Node.
+
+## Timeline
+
+- **2025-04-01 00:00 AM UTC**: Start of impact. Node.js v25.x expected to move from Current to Active LTS.
+
+- **2025-04-01 00:14 AM UTC**: Impact identified by [@MattIPv4's monitoring action](https://github.com/MattIPv4/monitors/actions/runs/23825485542)
+
+- **2025-04-01 00:51 AM UTC**: Impact reported in [OpenJSF Slack](https://openjs-foundation.slack.com/archives/CVAMEJ4UV/p1775004674164609). Investigation began.
+
+- **2025-04-01 01:00 AM UTC**: Root casued identified.
+
+- **2025-04-01 01:20 AM UTC**: [nodejs/nodejs.org#8786](https://github.com/nodejs/nodejs.org/issues/8787) opened to resolve issue.
+
+- **2025-04-01 01:33 AM UTC**: [nodejs/nodejs.org#8786](https://github.com/nodejs/nodejs.org/issues/8787) merged. Impact resolved shortly after.
+
+## Impact
+
+Users navigating to `https://nodejs.org/en/download/current` would see a blank page instead of the proper download instructions.
+
+`https://nodejs.org/en/download` was unaffected by this issue.
+
+## Root Cause
+
+According to a static schedule, on April 1st, 2026, Node.js 25.x was expected to move from Current to Active LTS, however, with v26.x
+[still unreleased](https://github.com/nodejs/node/pull/62526), this left no Current release left, causing the website to not properly
+render components relying on the Current release of Node.js.
+
+## Fix
+
+[nodejs/nodejs.org#8786](https://github.com/nodejs/nodejs.org/issues/8787) resolved the issue by changing the detection of a release's `status`
+to require `.lts.isLts` to be `true` before allowing a release to be marked as `Active LTS` or `Maintenance LTS`.
+
+## Follow-up Work
+
+* When possible, avoid relying on [the expected schedule](https://raw.githubusercontent.com/nodejs/Release/main/schedule.json), as various
+  delays and circumstances cause this to be inaccurate to actual release dates.