diff --git a/apps/site/pages/en/about/eol.mdx b/apps/site/pages/en/about/eol.mdx
index e2d2cea883c5c..7860f6ecd360c 100644
--- a/apps/site/pages/en/about/eol.mdx
+++ b/apps/site/pages/en/about/eol.mdx
@@ -41,6 +41,4 @@ Despite the obvious downsides of using EOL releases, in practice, organizations
 
 HeroDevs provides [Never-Ending Support (NES)](https://nodejs.org/esp/herodevs) for Node.js versions past their official maintenance phase. This includes security patches, compliance assistance, and technical support to help bridge the gap while you plan your upgrade strategy.
 
-NodeSource provides [security support](https://nodesource.com/services/support) for running older, unsupported versions of Node.js, giving teams more time and flexibility to transition to newer releases while maintaining a secure posture.
-
 Using EOL releases through commercial support should be viewed as a temporary solution—the goal should always be to upgrade to actively supported versions.