diff --git a/docs/platforms/javascript/common/install/loader.mdx b/docs/platforms/javascript/common/install/loader.mdx
index c309a26b23e13c..2d0d422b14f056 100644
--- a/docs/platforms/javascript/common/install/loader.mdx
+++ b/docs/platforms/javascript/common/install/loader.mdx
@@ -47,7 +47,7 @@ To use the loader, go in the Sentry UI to **Settings > Projects > (select projec
 
 ```html
 <script
-  src="https://js.sentry-cdn.com/___PUBLIC_KEY___.min.js"
+  src="https://js-de.sentry-cdn.com/___PUBLIC_KEY___.min.js"
   crossorigin="anonymous"
 ></script>
 ```
@@ -91,7 +91,7 @@ Alternatively, you can set the loader to request the full SDK earlier: still as
 
 ```html
 <script
-  src="https://js.sentry-cdn.com/___PUBLIC_KEY___.min.js"
+  src="https://js-de.sentry-cdn.com/___PUBLIC_KEY___.min.js"
   crossorigin="anonymous"
   data-lazy="no"
 ></script>
@@ -140,7 +140,7 @@ The loader script always includes a call to `Sentry.init` with a default configu
 </script>
 
 <script
-  src="https://js.sentry-cdn.com/___PUBLIC_KEY___.min.js"
+  src="https://js-de.sentry-cdn.com/___PUBLIC_KEY___.min.js"
   crossorigin="anonymous"
 ></script>
 ```
@@ -183,7 +183,7 @@ If you want to call any other method when using the Loader, you have to guard it
   };
 </script>
 
-<script src="https://js.sentry-cdn.com/___PUBLIC_KEY___.min.js" crossorigin="anonymous"></script>
+<script src="https://js-de.sentry-cdn.com/___PUBLIC_KEY___.min.js" crossorigin="anonymous"></script>
 
 <script>
   // Guard against window.Sentry not being available, e.g. due to Ad-blockers
@@ -220,7 +220,7 @@ If this is a critical issue for you, you have two options to ensure that all you
     };
   </script>
 
-  <script src="https://js.sentry-cdn.com/___PUBLIC_KEY___.min.js" crossorigin="anonymous"></script>
+  <script src="https://js-de.sentry-cdn.com/___PUBLIC_KEY___.min.js" crossorigin="anonymous"></script>
 
   <script>
     Sentry.onLoad(function () {
@@ -449,5 +449,5 @@ Without doing this you will find that it's possible for errors to occur before S
 
 If you have a Content Security Policy (CSP) set up on your site, you will need to add the `script-src` of wherever you're loading the SDK from, and the origin of your DSN. For example:
 
-- `script-src: https://browser.sentry-cdn.com https://js.sentry-cdn.com`
+- `script-src: https://browser.sentry-cdn.com https://js-de.sentry-cdn.com`
 - `connect-src: *.sentry.io`