This article is intended for network administrators responsible for firewall and web security configuration. It will help you configure your network to support Blitzz video calls and services.
Some firewalls block applications like Blitzz from accessing the internet unless explicitly allowed. You will need to whitelist the domains, IP addresses, and ports listed below to ensure Blitzz functions correctly on your network. Both incoming and outgoing TCP traffic must be permitted.
Required Domains & IP Addresses
We recommend whitelisting *.blitzz.co to cover all subdomains. If your firewall does not support wildcard domains, whitelist each entry individually using the table below.
| # | Domain / IP Address | Protocol | Purpose |
|---|---|---|---|
| 1 | *.blitzz.co (recommended) | HTTPS/443 | Covers all Blitzz subdomains. Use rows 2–10 if wildcard is not supported. |
| 2 | {company-subdomain}.blitzz.co | HTTPS/443 | Replace {company-subdomain} with your assigned subdomain (e.g. acme.blitzz.co) |
| 3 | services.blitzz.co | HTTPS/443 | Backend services and push notifications |
| 4 | media.blitzz.co | HTTPS/443 | Media uploads |
| 5 | analyticapi.blitzz.co | HTTPS/443 | Data analytics |
| 6 | api-ga.blitzz.co | HTTPS/443 | Backend services and push notifications for new portals |
| 7 | socket-ga.blitzz.co | WSS/443 | CoBrowse product |
| 8 | storageapi.blitzz.co | HTTPS/443 | Accessing and storing media |
| 9 | blitzzmedia.blob.core.windows.net | HTTPS/443 | Accessing and storing media |
| 10 | *.launchdarkly.com | HTTPS/443 | Feature previews and premium feature access |
| 11 | 159.69.72.82 138.201.23.91 94.130.129.237 | HTTPS/443 | Localization strings for region-specific language support |
| 12 | api.twilio.com | HTTPS/443 | REST API for creating rooms |
| 13 | video.twilio.com | HTTPS/443 | REST API for video features |
| 14 | global.vss.twilio.com | WSS/443 | Signaling communication |
| 15 | sdkgw.us1.twilio.com | WSS/443 | Video SDK for Android, iOS, and JavaScript |
| 16 | 54.70.204.128/27 us-west-2.quicksight.aws.amazon.com | HTTPS/443 | Reports and dashboards |
Media Server IP Ranges (Video Calls & Call Recordings)
The following IP ranges and ports are required for audio, video, and data exchange during calls, and for the Call Recording feature if enabled.
By default, Blitzz routes traffic through the server closest to the first participant. If you need to restrict traffic to specific regions only, please contact our support team — note that this may affect call quality for participants in other regions.
Ports required: 10,000–60,000 UDP/SRTP/SRTCP and TLS/443 or UDP/3478
We strongly recommend enabling UDP for all incoming connections on these IP ranges across ports 10,000–60,000 and 3478.
| # | IP Address Range | Ports | Region |
|---|---|---|---|
| 1 | 34.216.110.128 - 34.216.110.159 54.244.51.0 - 54.244.51.255 44.234.69.0 - 44.234.69.127 | 10,000–60,000 UDP & TLS/443 or UDP/3478 | US West Coast (Oregon) |
| 2 | 34.203.254.0 - 34.203.254.255 54.172.60.0 - 54.172.61.255 34.203.250.0 - 34.203.251.255 3.235.111.128 - 3.235.111.255 | 10,000–60,000 UDP & TLS/443 or UDP/3478 | US East Coast (Virginia) |
| 3 | 13.210.2.128 - 13.210.2.159 54.252.254.64 - 54.252.254.127 3.25.42.128 - 3.25.42.255 | 10,000–60,000 UDP & TLS/443 or UDP/3478 | Australia |
| 4 | 18.231.105.32 - 18.231.105.63 177.71.206.192 - 177.71.206.255 18.230.125.0 - 18.230.125.127 | 10,000–60,000 UDP & TLS/443 or UDP/3478 | Brazil |
| 5 | 52.59.186.0 - 52.59.186.31 18.195.48.224 - 18.195.48.255 18.156.18.128 - 18.156.18.255 | 10,000–60,000 UDP & TLS/443 or UDP/3478 | Germany |
| 6 | 52.215.253.0 - 52.215.253.63 54.171.127.192 - 54.171.127.255 52.215.127.0 - 52.215.127.255 3.249.63.128 - 3.249.63.255 | 10,000–60,000 UDP & TLS/443 or UDP/3478 | Ireland |
| 7 | 52.66.193.96 - 52.66.193.127 52.66.194.0 - 52.66.194.63 3.7.35.128 - 3.7.35.255 | 10,000–60,000 UDP & TLS/443 or UDP/3478 | India |
| 8 | 13.115.244.0 - 13.115.244.31 54.65.63.192 - 54.65.63.255 18.180.220.128 - 18.180.220.255 | 10,000–60,000 UDP & TLS/443 or UDP/3478 | Japan |
| 9 | 13.229.255.0 - 13.229.255.31 54.169.127.128 - 54.169.127.191 18.141.157.128 - 18.141.157.255 | 10,000–60,000 UDP & TLS/443 or UDP/3478 | Singapore |
Logs & Debugging (Recommended)
Blitzz uses Google Firebase for log capture to help diagnose issues. We recommend allowing outbound connections on the following ports for all IPs (*):
- TCP 5228 — Primary port used by Firebase Cloud Messaging (GCM)
- TCP 5229 — Used occasionally
- TCP 5230 — Used occasionally
Note: GCM does not use fixed IP addresses and changes IPs frequently. Configure rules by port only for this service. See Firebase documentation for more details.
VPN Considerations
If users on your network connect via VPN, video call traffic may be affected by the additional latency and bandwidth overhead a VPN introduces. To ensure the best call quality, we recommend configuring split tunneling so that Blitzz traffic bypasses the VPN tunnel. Use the domain and IP whitelist above to configure your split tunnel rules.
Test Your Network
Once configured, run our diagnostic tests to verify your network is set up correctly: