diff --git a/data-governance/no-code-access.mdx b/data-governance/no-code-access.mdx
index 085f47cb..8ef8ad72 100644
--- a/data-governance/no-code-access.mdx
+++ b/data-governance/no-code-access.mdx
@@ -40,7 +40,8 @@ which includes `octomind`.
 
 ## Two IP addresses
 
-If you need to set your firewall to allow our agent to access your web app, please allow our IP addresses: `35.192.162.70` and `34.159.153.198` (europe proxy).
+If you need to set your firewall to allow our agent to access your web app, please allow our IP addresses: `35.192.162.70`,
+`34.159.153.198` (europe proxy) or `34.129.193.156` (australia proxy).
 
 ## NDA option
 
diff --git a/octomind-bot.mdx b/octomind-bot.mdx
index 6935a714..571f0da1 100644
--- a/octomind-bot.mdx
+++ b/octomind-bot.mdx
@@ -50,7 +50,8 @@ Key functionalities include:
 3. **IP Address Management:**
 
    - The bot uses a proxy for all web requests, ensuring that the IP address is consistent across all interactions. It does not use IP rotation.
-   - The proxy server is configured by the octomind platform and currently uses two IP addresses `35.192.162.70` and `34.159.153.198`.
+   - The proxy server is configured by the octomind platform and currently uses 3 IP addresses `35.192.162.70`, `34.159.153.198`
+     and `34.129.193.156`.
 
 4. **Page Loading and AI Analysis:**
 
diff --git a/private-location.mdx b/private-location.mdx
index 7f19ab69..1566e304 100644
--- a/private-location.mdx
+++ b/private-location.mdx
@@ -19,7 +19,7 @@ The worker acts as a combination of a proxy and tunneling mechanism, connecting
 ### Tunneling with FRP
 
 The tunneling is managed using [FRP](https://github.com/fatedier/frp), connecting the worker’s frp-client to Octomind’s proxy servers (EU or US).
-It requires access permission to specific public IPs: `35.192.162.70` or `34.159.153.198`.
+It requires access permission to specific public IPs: `35.192.162.70`, `34.159.153.198` or `34.129.193.156`.
 
 ### Access to private web applications
 
diff --git a/proxy/private-location.mdx b/proxy/private-location.mdx
index 169e369f..941cbbb8 100644
--- a/proxy/private-location.mdx
+++ b/proxy/private-location.mdx
@@ -19,7 +19,7 @@ The worker acts as a combination of a proxy and tunneling mechanism, connecting
 ### Tunneling with FRP
 
 The tunneling is managed using [FRP](https://github.com/fatedier/frp), connecting the worker’s frp-client to Octomind’s proxy servers (EU or US).
-It requires access permission to specific public IPs: `35.192.162.70` or `34.159.153.198`.
+It requires access permission to specific public IPs: `35.192.162.70`, `34.159.153.198` or `34.129.193.156`.
 
 ### Access to private web applications
 
diff --git a/rate-limiting.mdx b/rate-limiting.mdx
index 2d27466c..e8a42a6c 100644
--- a/rate-limiting.mdx
+++ b/rate-limiting.mdx
@@ -6,7 +6,8 @@ icon: "gauge-max"
 
 Whenever the AI agent generates tests for user flows on your page, or when the test runner executes the tests - we are sending requests to your application.
 
-To ensure a well defined behavior all requests are sent through **two fixed IP addresses** - `35.192.162.70` and `34.159.153.198` (europe proxy).
+To ensure a well defined behavior all requests are sent through **3 fixed IP addresses** - `35.192.162.70`, `34.159.153.198` (europe proxy) 
+and `34.129.193.156` (australia proxy).
 
 ## AI generation
 
@@ -30,4 +31,5 @@ While Octomind supports a login with a **one time password (OTP)**, it might run
 ## Rate limiter
 
 If your application is protected against [DoS Attacks](https://en.wikipedia.org/wiki/Denial-of-service_attack) with a [rate limiter](https://en.wikipedia.org/wiki/Rate_limiting) it is very likely that Octomind test runs and/or AI generation will fail.
-The easiest solutions is to configure and exception for our IP address: `35.192.162.70` and `34.159.153.198` (europe proxy) for white listing.
+The easiest solutions is to configure and exception for our IP address: `35.192.162.70`, `34.159.153.198` (europe proxy) 
+ or `34.129.193.156` (australia proxy) for white listing.