You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: incidents/2026-04-01.md
+7-5Lines changed: 7 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,11 +3,11 @@
3
3
- Incident Commander: @MattIPv4
4
4
- Severity Level: P2
5
5
6
-
For a brief period of time, the downloads page was blank due to a false assumption on there always being a Current version of Node.
6
+
For a brief period of time, the `/downloads/current` page was blank due to a logic bug in determining the Current version of Node.js. The main `/downloads` page was unaffected and could be accessed throughout.
7
7
8
8
## Timeline
9
9
10
-
-**2025-04-01 12:00 AM UTC**: Start of impact. Node.js v25.x expected to move from Current to Active LTS.
10
+
-**2025-04-01 12:00 AM UTC**: Start of impact. Release schedule indicates that Node.js 25.x has moved from Current to Active LTS.
11
11
12
12
-**2025-04-01 00:14 AM UTC**: Impact identified by [@MattIPv4's monitoring action](https://github.com/MattIPv4/monitors/actions/runs/23825485542).
13
13
@@ -23,13 +23,15 @@ For a brief period of time, the downloads page was blank due to a false assumpti
23
23
24
24
Users navigating to `https://nodejs.org/en/download/current` would see a blank page instead of the proper download instructions.
25
25
26
+
Users accessing any page on the website would see only the 24.x LTS release in the footer, no Current release.
27
+
26
28
`https://nodejs.org/en/download` was unaffected by this issue.
27
29
28
30
## Root Cause
29
31
30
-
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
31
-
[still unreleased](https://github.com/nodejs/node/pull/62526), this left no Current release left, causing the website to not properly
32
-
render components relying on the Current release of Node.js.
32
+
According to the static release schedule, on April 1st, 2026, Node.js 25.x was expected to move from Current to Active LTS. Due to this, the website logic automatically started treating 25.x as an Active LTS major.
33
+
34
+
However, no new release of 25.x has yet been made to be marked as LTS, nor has the first release of 26.x been made to become the new Current major. This left the website with no Current release per its logic.
0 commit comments