diff --git a/docs/troubleshooting-lambda-tunnel.md b/docs/troubleshooting-lambda-tunnel.md
index 4b7a574db..9bb02c499 100644
--- a/docs/troubleshooting-lambda-tunnel.md
+++ b/docs/troubleshooting-lambda-tunnel.md
@@ -105,14 +105,10 @@ If you are testing a server that requires IP whitelisting, then you just have to
 - 23.82.88.184
 - 23.106.34.219
 - 23.106.54.77
-
-> Below are IPs that will be deprecated soon
->  - 3.214.241.254
->  - 52.36.84.247
->  - 13.126.37.58
->  - 3.66.78.89
-
-However be advised, as we are aggressively adding more and more data centers, these IP would be changed, you can see the updated IP’s on this documentation as well.
+- 3.214.241.254
+- 52.36.84.247
+- 13.126.37.58
+- 3.66.78.89
 
 ## 5. Custom Host Name
 Because of some firewall restrictions, your web application might not be accessible on some other servers even after whitelisting the IP’s and configuring the tunnel, in such case you need to make an entry in the hosts file which is used to map hostnames to IP addresses. With the hosts file, you can change the IP address that you resolve a given domain name. This change only affects your own computer without affecting how the domain is resolved worldwide.