Google Meet Troubleshooting Playbook - Network and Hardware Troubleshooting

Baseline

  • Meet clients use two types of network connections to the Meet back-end:
    • Media: RTP/RTCP protocol over UDP (ports: 19302​–19309). If those ports are blocked, Meet will fallback to TCP, which is suboptimal and should be avoided whenever possible.
    • Everything besides media: HTTPS
  • We discourage proxy servers. If proxy servers are absolutely required, make sure the proxy settings 100% meet proxy best practice and Network preparation for Meet
  • When observing suboptimal Meet experience, checking the Internet connection would be a good start point. Ethernet would generally be stabler than WiFi. If using WiFi, make sure the WiFi signal is ideal, and 5GHz is preferred.

Ideal Metrics

Meet will adapt to suboptimal conditions automatically, so users don’t necessarily get issues when they don’t meet the ideal numbers. 

The following metrics can be found in Meet Quality Tool (Help Center)

Metric 

ideal

Packet loss

< 3%

Connection delay

< 120ms

FPS

> 5

Client CPU usage

< 80%

 

Packet Loss
  • Packet loss should be near to 0%. Meet quality would be degrading if packet loss > 3%.
  • A continuous ping from client machine to lens.meet.google.com can be used to verify packet drop
Connection delay(RTT)
  • Users might experience noticeable delay when RTT > 120ms
FPS
  • FPS varies depending on the present mode(entire screen, a window, or a tab), content(video or static content), and screen resolution.
  • Generally speaking, we expect FPS to be at least 5. Depending on the present mode / content /resolution, Meet may require higher FPS and bitrate.
CPU Usage
  • Computer:
    • CPU usage over 60% can introduce video compression and decompression delay, check if the browser is causing high CPU usage.
    • CPU usage over 90% indicates a resource shortage at the system level, check if the hardware is adequate to run Meet, you can find the required specifications here
  • CfM(Chromebox for meetings):
    • A CfM is dedicated to Meet, and there are no other applications running on a CfM, therefore, as long as the CPU usage doesn’t constantly hit 100%, it should be fine.
Contributors
Version history
Last update:
‎08-02-2021 02:27 AM
Updated by: