diff --git a/docs/platforms/javascript/common/install/esm.mdx b/docs/platforms/javascript/common/install/esm.mdx
index d222a843810b8..665fdc8ccbdb4 100644
--- a/docs/platforms/javascript/common/install/esm.mdx
+++ b/docs/platforms/javascript/common/install/esm.mdx
@@ -37,7 +37,7 @@ Sentry.init({
 Adjust the Node.js call for your application to use the [--import](https://nodejs.org/api/cli.html#--importmodule) parameter and point it at `instrument.js`, which contains your `Sentry.init()` code:
 
 ```bash
-# Note: This is only available for Node v18.19.0 onwards.
+# Note: This is only available for Node v20.19.0 onwards.
 node --import ./instrument.mjs app.mjs
 ```
 
@@ -51,7 +51,7 @@ If you're building a Node.js Single Executable Application (SEA) and can't rely
 on `--import` or `NODE_OPTIONS`, use the <PlatformLink to="/install/esm-without-import/#nodejs-single-executable-applications">SEA
 bootstrap setup</PlatformLink> instead.
 
-We do not support ESM in Node versions before 18.19.0.
+We do not support ESM in Node versions before 20.19.0.
 
 ## Troubleshooting instrumentation
 
diff --git a/docs/platforms/javascript/guides/nestjs/install/esm.mdx b/docs/platforms/javascript/guides/nestjs/install/esm.mdx
index 9ba9ba454e9a0..19e2bd7b12d52 100644
--- a/docs/platforms/javascript/guides/nestjs/install/esm.mdx
+++ b/docs/platforms/javascript/guides/nestjs/install/esm.mdx
@@ -31,7 +31,7 @@ Sentry.init({
 **Step 2:** Adjust your application's start command to use the [--import](https://nodejs.org/api/cli.html#--importmodule) parameter:
 
 ```bash
-# Note: This is only available for Node v18.19.0 onwards.
+# Note: This is only available for Node v20.19.0 onwards.
 "start": "--import ./instrument.mjs nest start"
 ```
 
@@ -41,7 +41,7 @@ If you can't pass the `--import` flag to the Node.js binary, you can alternative
 NODE_OPTIONS="--import ./instrument.mjs" npm run start
 ```
 
-<Alert>We do not support ESM in Node versions before 18.19.0.</Alert>
+<Alert>We do not support ESM in Node versions before 20.19.0.</Alert>
 
 ## Troubleshooting ESM Instrumentation
 
diff --git a/platform-includes/getting-started-prerequisites/javascript.node.mdx b/platform-includes/getting-started-prerequisites/javascript.node.mdx
index 76c8644590648..3aa2b9985a1a2 100644
--- a/platform-includes/getting-started-prerequisites/javascript.node.mdx
+++ b/platform-includes/getting-started-prerequisites/javascript.node.mdx
@@ -4,13 +4,4 @@ You need:
 
 - A Sentry [account](https://sentry.io/signup/) and [project](/product/projects/)
 - Your application up and running
-- Node version `18.0.0` or above (>= `19.9.0` or `18.19.0`  recommended)
-
-<Expandable title="Are you using Node version < 18.19.0 or < 19.9.0?">
-  The required Node version will increase in the next major release of the SDK (v11) to support features that rely on [`TracingChannel`](https://nodejs.org/api/diagnostics_channel.html#class-tracingchannel).
-
-  - We strongly recommend upgrading to at least Node `18.19.0` or `19.9.0` to get the best support.
-  - While we may add features relying on `TracingChannel` in v10.x releases, they will have backwards compatibility for older Node versions.
-
-  See the following [issue on GitHub](https://github.com/getsentry/sentry-javascript/issues/17585) for more details.
-</Expandable>
+- Node version `20.19.0` or above. The full supported range is `>=20.19.0 <22.0.0 || >=22.12.0 <23.0.0 || >=23.2.0` (Node 22 requires `22.12.0`+, Node 23 requires `23.2.0`+).