From d53082fd15989bd950b81ed87030d88c0f701fa4 Mon Sep 17 00:00:00 2001
From: Protogen187 <162638343+Protogen187@users.noreply.github.com>
Date: Mon, 27 Jan 2025 20:03:41 +0100
Subject: [PATCH] Update How-to-check-for-CGNAT.md

---
 docs/en/FAQ/How-to-check-for-CGNAT.md | 2 --
 1 file changed, 2 deletions(-)

diff --git a/docs/en/FAQ/How-to-check-for-CGNAT.md b/docs/en/FAQ/How-to-check-for-CGNAT.md
index 13da8192..237d94d9 100644
--- a/docs/en/FAQ/How-to-check-for-CGNAT.md
+++ b/docs/en/FAQ/How-to-check-for-CGNAT.md
@@ -10,8 +10,6 @@ If you have connection problems and you are using a Hosting-Service, contact the
 
 ## Method 1:
 Open a command prompt, run ``tracert -4 beammp.com``. This will output a series of network hops. Wait for the operation to finish (may take up to 30 hops). Check the first few IP addresses after the IP of your Router/Modem/Gateway.
-If multiple IP addresses within the range of 100.64.x.x-100.127.x.x appear after the Gateway/Modem/Router IP (top IP), you are most likely behind a CGNAT.
-
 If multiple IP addresses within the range of ``100.64.x.x``-``100.127.x.x`` or ``10.xx.xx.xx`` appear after the first hop, you are most likely behind a CGNAT.
 The first hop is your Router/Modem/Gateway and differs between Devices.