Network Preparation for Meet Video Calls Network Preparation for Meet Video Calls
  1. Home
  2. Troubleshooting
  3. Recommended Guides

Network Preparation for Meet Video Calls

Workspace Support Workspace Support
Support_Portal_Image@2x.png

Introduction

This article details how to prepare your network for Meet video calls.

Process

To provide high-quality video meetings with Google Meet, you need to set up your network so that Meet can efficiently communicate with the Google infrastructure. 

You should:

  • Make sure Meet traffic has a short path to the internet. 
  • Avoid proxies, packet inspection, protocol analyzers, and quality of service (QoS)
  • Measure and optimize latency, bandwidth, and your Wi-Fi network.

 

Step 1: Set up outbound ports for media traffic

Update your firewalls to allow media traffic to flow to and from your organization:
  • For media (audio and video), set up outbound UDP ports 19302​–19309. If you want to limit  the number of Chrome WebRTC ports being used, see Chrome WebRTC UDP Ports setting. Alternatively you can limit those ports via your firewall.
  • For web traffic and user authentication, use outbound UDP and TCP port 443.

Notes:

  • TCP will be used if these UDP ports are blocked.
  • Sustained use of TCP or SSLTCP by any participant can degrade overall call quality.

 

Step 2: Allow access to uniform resource identifiers (URIs)

The core Google services need full network access. If there are restrictions or filtering policies for users on your network, give network access to the following URI patterns using port 443.

 

Note: If you're using Google Meet hardware, please also review the networking requirements for ChromeOS.

For web traffic, APIs, feedback reports, logs upload, and connectivity setup patterns:

  • https://*.google.com/*
  • https://*.googleapis.com/*
  • https://*.gstatic.com/* 
  • https://*.googleusercontent.com/*

For live streaming patterns:

 

Step 3: Allow access to Google IP address ranges

Allow access to the following IP address ranges to enable audio and video media traffic. 

 

Note: These IP addresses are different from the URIs specified in Step 2.

Google Workspace IP address ranges

These IP ranges are used exclusively for Meet to identify video meeting traffic used with your organization’s Google Workspace accounts and to deprioritize Meet traffic from consumer accounts.

Allow access to Meet's media servers using the following set of IP ranges:  

  • IPv4: 74.125.250.0/24
  • IPv6: 2001:4860:4864:5::0/64

Consumer IP address ranges

The following IP ranges are used exclusively for media traffic coming from participants who are signed in to a personal Google Account or not signed in to any account.

Allow access to Meet's media servers using the following set of IP ranges:  

  • IPv4: 142.250.82.0/24
  • IPv6: 2001:4860:4864:6::/64

 

Step 4: Review bandwidth requirements

Your network should have enough bandwidth for concurrent HD video meetings, plus additional bandwidth for other needs, such as live streaming. If there’s not enough bandwidth, Meet lowers the video definition to fit the network constraints. If the bandwidth is insufficient to transfer video, an audio-only mode is used.

Calculate minimum Meet bandwidth requirements

To calculate minimum bandwidth for participants and live streaming, multiply the average bandwidth per participant by the peak number of concurrent participants. 

Bandwidth requirements per participant

The bandwidth used by Meet varies to provide the best experience on participants’ networks.

 

Average bandwidth per participant    
Meeting type Outbound Inbound
HD Video 3.2 Mbps 1.8 Mbps
Audio only 12 Kbps 18 Kbps

 

Ideal bandwidth per participant    
Meeting type Outbound Inbound
2-person HD video meetings 3.2 Mbps 2.6 Mbps
Group video meetings 3.2 Mbps 3.2 Mbps

 

Estimate peak number of concurrent participants

Determine the number of concurrent participants based on how important video calling is at each site, as shown in the following table.
 

Importance of video meetings Peak number of concurrent video meetings
High 10–20%
Normal 1–4%
Low 0.01–0.5%

 

For example, if video meetings are of high importance, estimate that 20% of the users at that site will use Meet. If video meetings are of low importance, only 0.5% of people at that site might be in a video meeting at the same time.

Bandwidth requirements per live stream viewer

If your organization live streams video meetings, the ideal bandwidth for each viewing participant is 2.6 Mbps. The default high-quality video setting is 720p and is used if the participant has enough individual bandwidth.
 
If sufficient bandwidth isn't available, viewers can also optionally choose to reduce the Meet video quality.

 

Meet video setting Inbound bandwidth required Notes
720p 2.6 Mbps Default high quality setting results in the best user experience
480p 1.5 Mbps  
360p 1.0 Mbps  
240p 0.5 Mbps Results in a poor viewer experience and is not recommended

 

Articles in this section