Supported Cloud Providers

Coverage matrix 

Tata Communications advertises from ASN 4755 on every cloud; the cloud-side autonomous-system numbers are noted per provider below.

AWS: Direct Connect

AWS is reached through AWS Direct Connect, available as Tata Communications-managed direct interconnects and as interconnection partner-routed Hosted Connections. Standard bandwidth tiers range from 50 Mbps to 500 Mbps; high-capacity tiers cover 1 Gbps to 25 Gbps. The connection is a routed Layer 3 service using a Virtual Interface (Private, Public or Transit), with BGP between your network and AWS. Jumbo MTU (up to 9001 bytes) is supported on interconnection partner-routed connections.

For detailed AWS guidance, see AWS Direct Connect Overview.

Azure: ExpressRoute

The Azure integration supports both Private Peering (for VNet access) and Microsoft Peering (for Microsoft 365, Dynamics and other public Azure services). Bandwidth tiers run from 50 Mbps to 10 Gbps. Azure provisions each circuit with a primary and secondary peering by default, so a resilient pair is built in. The effective WAN-side MTU is 1500 bytes (no jumbo). Microsoft advertises from ASN 12076; ExpressRoute Metro and ExpressRoute Direct are available for higher-resiliency or higher-capacity needs.

For detailed Azure guidance, see Azure ExpressRoute Overview.

Google Cloud: Cloud Interconnect

Google Cloud is reached via Partner Interconnect. Bandwidth runs from 50 Mbps to 50 Gbps per VLAN attachment: standard slabs go up to 10 Gbps, and 20 and 50 Gbps are available only where 100 Gbps ports are present. Google Cloud currently offers Private Peering only, allocates the peering IP addresses, and assigns the VLAN ID for the attachment (you cannot specify it). Connections are delivered as dual interconnects with zone-level redundancy: a Zone 1 pairing key (ending in /1) lands on the primary path and a Zone 2 pairing key (/2) on the secondary, with BGP local preference and AS-PATH prepend making one primary and the other secondary. Bandwidth can be changed in place (hot upgrade and downgrade). Jumbo MTU below 9000 bytes is supported on interconnection partner-routed connections; multicast is not supported. Google advertises from ASN 16550.

For detailed Google Cloud guidance, see Google Cloud Interconnect Overview.

Oracle Cloud Infrastructure: FastConnect

Oracle is reached via FastConnect with Tata Communications as the provider. On the direct path, bandwidth runs from 1 Gbps to 10 Gbps (slabs 1, 2, 3, 4, 5 and 10 Gbps), with 25 Gbps available where the Oracle interconnect is 100 Gbps; a interconnection partner-routed connection additionally offers lower slabs from 10 Mbps upward. Oracle supports both Private and Public peering, chosen by you when you create the circuit (Tata Communications allocates the private-peering IPs; Oracle allocates the public-peering IPs). The supported MTU is 1500 bytes standard and 9000 bytes jumbo. On the direct path you define and change bandwidth in the Oracle console, with upgrades and downgrades applied without Oracle-side downtime; multicast is not supported. Oracle advertises from ASN 31898.

For detailed Oracle Cloud guidance, see Oracle Cloud FastConnect Overview.

IBM Cloud: Direct Link Connect

IBM is reached via Direct Link Connect with Tata Communications as the provider. Bandwidth runs from 50 Mbps to 2 Gbps (slabs 50, 100, 200 and 500 Mbps, 1 and 2 Gbps). IBM uses Private peering, and the WAN-side MTU is 1500 bytes (jumbo is under evaluation). Bandwidth over-provisioning is not supported; Tata Communications can change bandwidth on your behalf on request, and every gateway request must be accepted by you in the IBM Cloud console. IBM advertises from ASN 13884.

Zoom: Cloud Connect for SaaS

Zoom is reached as a public-service (SaaS) destination over the private backbone rather than as an IaaS interconnect. Zoom advertises its public service prefixes to Tata Communications over the interconnect, and your sites reach Zoom on the private path using public (non-routable) addressing, so Zoom traffic stays off the public internet and keeps predictable, SLA-backed performance. Each Zoom region is delivered from two interconnect locations for resiliency: prefixes from both locations are advertised to your CPE, and failover between them is handled at the application level. Zoom traffic is carried in a single class of service, and BFD uses a 1000 ms × 3 timer for Zoom.

Unlike the IaaS clouds, Zoom is not ordered in fixed bandwidth slabs; capacity is governed by the interconnect and the class of service. Zoom is one of many SaaS destinations reachable this way, and the same public-service model applies to the other supported SaaS providers.

Cross-cloud connectivity

IZO™+ Multi Cloud Connect supports private cloud-to-cloud connectivity (for example, AWS to Azure) over the Tata Communications backbone, so cross-cloud traffic does not go over the public internet. Reaching several clouds over one private platform also reduces dependence on any single provider and keeps networking policy and visibility consistent across them.

Related pages

• Bandwidth Tiers and Slabs
• Coverage and Points of Presence
• AWS Direct Connect Overview