Bramble Network Requirements
Bramble data and webRTC traffic operates over standard ports via TCP and UDP using HTTPS, WebSocket Secure (WSS) & TURN so Bramble works across most firewalls. Under strict whitelist only firewalls the below ports must be accessible for the listed protocols. You can use the buttons at the bottom of this page to test UDP connectivity (for live voice) and WSS connectivity before completing the Are You Ready test to check connection speeds and audio setup.
Recommended Approach
- Whitelist by URL, if possible. This is the most robust solution and ensures connectivity remains current.
- If IPs must be specified, but multiple ranges are allowed then please consult AWS published IP ranges to allow for the specified AWS region. This will ensure connectivity remains current.
- If individual IPs must be specified, then the current IPs are listed. However, these are subject to change so we would recommend checking regularly and always as a first step in the event of any connectivity issues arising.
- Ensure WSS & TURN protocols are allowed on the ports you've just opened.
Special Guidance for Smoothwall Firewalls
If you are using a Smoothwall firewall then you will need to add the below IP addresses to the destination exceptions list. Adding them to the HTTPS exceptions and Smoothwall whitelist is not sufficient.
| URL | Protocol | Ports | AWS Region | Current IP* |
|---|---|---|---|---|
| session_server_1.bramble.io | TCP | 443 | eu-west-1 | 52.208.61.41 |
| session_server_2.bramble.io | TCP | 443 | eu-west-1 | 54.170.176.124 |
| session_server_3.bramble.io | TCP | 443 | eu-west-1 | 34.252.122.144 |
| session_server_4.bramble.io | TCP | 443 | eu-west-1 | 46.51.154.222 |
| session_server_5.bramble.io | TCP | 443 | eu-west-1 | 54.228.175.100 |
| session_server_6.bramble.io | TCP | 443 | eu-west-1 | 18.201.7.36 |
| session_server_7.bramble.io | TCP | 443 | eu-west-1 | 46.137.129.40 |
| session_server_8.bramble.io | TCP | 443 | eu-west-1 | 52.215.45.191 |
| session_server_9.bramble.io | TCP | 443 | eu-west-1 | 54.73.246.179 |
| session_server_10.bramble.io | TCP | 443 | eu-west-1 | 52.19.131.29 |
| session_server_cfsr.bramble.io | TCP | 443 | eu-west-1 | 34.248.111.251 |
| api.bramble.io | TCP | 443 | eu-west-1 | 34.252.125.74 |
| test.bramble.io | TCP | 443 | eu-west-1 | 3.249.37.110 |
| coturn_london2.bramble.io | TCP & UDP | 443, 3478, 5349, 49152-65535 | eu-west-2 | 18.130.37.168 |
| coturn_dublin2.bramble.io | TCP & UDP | 443, 3478, 5349, 49152-65535 | eu-west-1 | 54.78.241.20 |
| coturn_frankfurt2.bramble.io | TCP & UDP | 443, 3478, 5349, 49152-65535 | eu-central-1 | 35.157.109.45 |
| coturn_hal1.bramble.io | TCP & UDP | 443, 3478, 5349, 49152-65535 | N/A | 89.38.121.11 |
| datacentre0.bramble.io | TCP | 443 | N/A | 89.38.121.10 |
| datacentre1.bramble.io | TCP & UDP | 443, 3478, 5349, 49152-65535 | N/A | 89.38.121.11 |
| datacentre2.bramble.io | TCP | 443 | N/A | 89.38.121.12 |
*Current IP addresses are subject to change. See recommended approach for more details.