<img height="1" width="1" style="display:none" src="https://www.facebook.com/tr?id=1705902170274878&amp;ev=PageView&amp;noscript=1">
Skip to content
Talk to Us
  • There are no suggestions because the search field is empty.

Zoom Connectivity Overview

IZO™+ Multi Cloud Connect delivers private connectivity to Zoom over Tata Communications’ MPLS backbone, as an alternative to reaching Zoom across the public internet. Because the internet is a best-effort medium, an enterprise has no control over how its Zoom media traffic is transported; this service keeps that traffic on a private, SLA-backed network end to end, giving more predictable performance for real-time voice and video. 

Zoom connectivity is delivered as a managed Layer-3 hub-and-spoke service: Zoom is the hub, your sites are spokes on the Tata Communications MPLS backbone. Unlike the hyperscaler services, you do not create a gateway or run BGP to Zoom – Tata Communications peers with Zoom on your behalf, and your sites receive Zoom’s public routes inside a dedicated VPN. Resiliency is region-based, and Zoom mandates a dual virtual circuit per customer. 

MCC Visual Chapter 8.CDEF By Cloud GCP OCI IBM Zoom-8.F.1-1 Zoom architecture hero.drawio

Why private connectivity to Zoom

Delivering Zoom over the Tata Communications MPLS backbone rather than the internet provides:

  • Committed latency and quality of service within the Tata Communications network.

  • Routing predictability – traffic does not traverse multiple internet backbones, and routing does not change dynamically.

  • Traffic that stays within a private MPLS network end to end, secured using MPLS VPN technologies.

  • Guaranteed availability, and a network that is not exposed to internet DDoS, privacy, and compliance concerns in the same way as best-effort access.

How it works at a glance

  1. Tata Communications establishes peering (NNI) with the Zoom cloud platform in the regions Zoom supports and receives Zoom’s public prefixes.

  2. Your sites are connected into a dedicated Zoom VPN on the Tata Communications MPLS backbone as spokes.

  3. Your sites receive Zoom’s public routes and reach Zoom over the private path - a single public non-routable (PNR) address per customer is advertised toward Zoom.

  4. Resiliency comes from dual peering within a Zoom region, with failover selected at your Zoom application level.

          The architecture, addressing and service characteristics are detailed on Zoom Connectivity Architecture.

          What you do on the Zoom side

          This service carries your Zoom traffic privately; it does not change how you administer Zoom. You continue to manage your Zoom account and applications as usual, including choosing your primary and secondary Zoom region/zone at the application level, which is how failover is controlled (see the architecture page).

          Related pages