OCI FastConnect Redundancy — What You Should Know Before It’s Too Late✅

FastConnect is Oracle Cloud Infrastructure’s dedicated private connectivity option, offering a reliable, high-throughput alternative to internet-based connections. While FastConnect boasts impressive performance and security advantages, there’s a critical element often misunderstood or overlooked by customers — redundancy.

This blog aims to demystify redundancy in FastConnect, guide you on how to identify if your setup is truly redundant, and highlight why redundancy is essential to meet SLA expectations and avoid painful outages.

🔍 Types of FastConnect Connections

OCI provides FastConnect through the following options:

1. Direct Connect FastConnect

• Colocation with Oracle — []
• Using a Third-Party Provider — []

2. Partner-Provided FastConnect — []

In the case of Partner FastConnect, partners often provide L3 connectivity and may provision a single Virtual Circuit (VC) with built-in redundancy. This is typically implemented by using diverse physical paths that terminate on separate Oracle routers — but not all partners implement this by default.

Especially in few markets, some partner base offerings do not include this redundancy.

⚠️ Not All Partner FastConnect Offerings Are Redundant

When a partner enlists as a Layer 3 (L3) service provider, they are typically expected to provision a single Virtual Circuit (VC) with redundant physical links that terminate on different Oracle routers.

However, some partner offerings in regions like India do not include redundancy by default. This means:

• You may only have a single physical link.
• The Oracle end might not terminate the connection across diverse routers.
• Any maintenance activity on the Oracle side or the partner side could lead to a complete outage.

And worst of all — many customers don’t realize this until downtime hits.

🔎 How to Check FastConnect Redundancy in OCI Console

OCI makes it easy to check redundancy status from the Console. Refer to the below screenshot as an example:

Key indicators:

• Redundancy level:

If the redundancy level shows Not Redundant, your FastConnect is NOT redundant, and your connection does not qualify for Oracle’s FastConnect SLA.

What Should You Do?

1. Engage Your FastConnect Partner

• Ask if their offering includes redundant physical paths and diverse terminations at Oracle.

2. Check in Console

• Go to Networking → FastConnect.
• Inspect each Virtual Circuit under your compartment.
• Validate the Redundancy Level.

3. Build Redundancy Yourself (if needed)

If your partner only provides a single circuit:

• Consider provisioning a second redundant FastConnect from a different partner.
• Or, mix a FastConnect + VPN setup for backup.

🛡️ Redundancy Is a Requirement for SLA

Oracle’s FastConnect SLA only applies when you have redundant connections. No redundancy → No SLA.

Don’t rely on assumptions. Validate your setup before downtime impacts your business.

Summary

• Not all FastConnect offerings include redundancy — especially in some regional markets.
• Redundancy must be explicitly verified through the OCI Console and your partner.
• Only redundant setups are SLA-eligible.
• Be proactive. Double-check today to avoid surprises tomorrow.

Learn more about and .

🔗 Suggested references: