Blitzz Help Center

Network Requirements and Recommendations - Firewall Configuration

Firewall Configuration

This article is intended for network administrators, particularly firewalls and web security administrators. It will help you configure and test your network to support Blitzz.

Some firewalls will not permit applications such as Blitzz (or any applications you have not specifically allowed) to access the internet and it is necessary to open ports for Blitzz servers in the corporate firewall/proxy. It's necessary that the customer's on-premise infrastructure allows the Transmission Control Protocol (TCP) to flow for incoming and outgoing network traffic for Blitzz.

Required IP Addresses/ports to whitelist

Domains / IP AddressProtocolPurpose
1* (recommended)(HTTPS/443)Recommended to recognize any subdomains of If you have trouble whitelisting the wild card domain, please use rows 2, 3, 4, 5, 6 below.
2{company-subdomain} {company-subdomain} with your subdomain. Eg. to connect to backend services and Push notifications for uploading media analytics and storing media

(HTTPS/443)Accessing and storing media

Used for Preview of new features and access to premium features.

(HTTPS/443)Localization Strings to support region-specific languages API for Creating rooms API for video-related features Communication SDK for Android, iOS, and JavaScript
1454.70.204.128/27(HTTPS/443)Access to Reports and Dashboards

For Call Recordings

Following ports are required for audio, data, and video exchange during your Video Calls and for Call Recording features if enabled. By default, Blitzz will pick the closest server to the first participant in the video call. If you prefer your traffic to route through any specific regions only, please contact our support team and we can disable all other regions for your account. This may impact the Quality of your video calls if you intend to have participants globally. Learn more about media regions here.

Server IP Address RangePortsRegion
1 - - -

10,000 - 60,000 UDP/SRTP/SRTCP and TLS/443 or UDP/3478US West Coast (Oregon)
2 - - - -

10,000 - 60,000 UDP/SRTP/SRTCP and TLS/443 or UDP/3478US East Coast (Virginia)
3 - - -

10,000 - 60,000 UDP/SRTP/SRTCP and TLS/443 or UDP/3478Australia
4 - - -

10,000 - 60,000 UDP/SRTP/SRTCP and TLS/443 or UDP/3478Brazil
5 - - -

10,000 - 60,000 UDP/SRTP/SRTCP and TLS/443 or UDP/3478Germany
6 - - - -

10,000 - 60,000 UDP/SRTP/SRTCP and TLS/443 or UDP/3478Ireland
7 - - -

10,000 - 60,000 UDP/SRTP/SRTCP and TLS/443 or UDP/3478India
8 - - -

10,000 - 60,000 UDP/SRTP/SRTCP and TLS/443 or UDP/3478Japan
9 - - -

10,000 - 60,000 UDP/SRTP/SRTCP and TLS/443 or UDP/3478Singapore
Ports used: 10,000 - 60,000 UDP/SRTP/SRTCP and TLS/443 or UDP/3478. We highly recommend you enable UDP Protocol for all incoming connections for the listed IP ranges above to the used ports(10000-60000, 3478). Learn more why UDP here.

Logs and debugging (Recommended)

We use Google Firebase for capturing logs when you encounter an issue or need help. We recommend enabling these IP addresses as well:

*5228 (TCP)
5229 (TCP)
5230 (TCP)
If your organization has a firewall that restricts the traffic to or from the Internet, you'll need to configure it to allow connectivity with GCM. The ports to open are 5228, 5229, and 5230. GCM typically only uses 5228, but it sometimes uses 5229 and 5230. GCM doesn't provide specific IPs. It changes IPs frequently. 

Test your network

Run these diagnostic tests to ensure your network is configured correctly:

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.