Skip to main content
  • 20 Product updates

What’s New: FiberMap
What’s New: Netskope Private Access on Network Edge
What’s New: EMS Expansion to Melbourne and Sydney
Fabric Geo Zones: When to Use it and What to Expect

Fabric Geo Zones: When to Use it and What to Expect

The Challenge:Organizations in government, finance, healthcare, and other regulated industries must ensure sensitive traffic remains within specific jurisdictions and complies with applicable regulations. This challenge extends beyond where data is stored to how network traffic moves between locations, clouds, and applications.Today, customers often rely on public internet routes or cloud service provider backbones that do not provide deterministic routing evidence or granular control over where traffic traverses. This can create trade-offs between compliance requirements and operational flexibility.A Better Approach:Fabric Geo Zones provides a single, end-to-end capability that enables customers to enforce geographic routing boundaries for network traffic. Customers apply policy-based routing controls, such as keeping traffic within a specific country or region, helping support sovereignty and compliance requirements.Fabric Geo Zones is delivered through new Fabric virtual connections that include sovereign routing controls, providing a straightforward way to implement geographic routing boundaries without requiring a bespoke networking approach.When to Use This:When sensitive workloads require traffic to remain within a specific country or region, such as enforcing EU-only or in-country routing policies When organizations need additional assurance that network traffic will stay within defined geographic boundaries across cloud and interconnection environmentsLearn More:Documentation - Fabric Geo Zones Fabric Geo Zones Demo Fabric Geo Zones Press Release

Related products:FabricFeature Enhancement
What’s New: Fabric Marketplace Provider Dashboard
Google Verified Peering Partner: When to Use it and What to Expect

Google Verified Peering Partner: When to Use it and What to Expect

The Challenge:Organizations increasingly rely on cloud services and hybrid multicloud architectures, but achieving reliable, high-performance connectivity to cloud providers can be complex. Establishing direct peering relationships often requires specialized networking expertise and ongoing operational management.Many organizations need a simpler way to access Google services with enterprise-grade performance and reliability, without managing peering relationships themselves.A Better Approach:Equinix Internet Access (EIA) is now a Google Gold Verified Peering Provider, enabling customers to access Google connectivity through an approved provider rather than managing a direct peering relationship themselves.This approach gives customers a private, off-internet peering path from EIA to Google’s public services – provisioned and operated by EIA, so customers don’t have to qualify for or manage Direct Peering themselves.When to Use This:When connecting to Google services and seeking a simpler alternative to establishing and managing a direct peering relationship When requiring enterprise-grade connectivity to Google with verified performance, resiliency, and operational support When supporting SASE, SD-WAN, or branch-office traffic patterns that need predictable, low-latency paths to Google across many sites, rather than one high-throughput dedicated pipeWhen Not to Use This:When you require a private, dedicated connection to Google Cloud with reserved bandwidth and greater control over routing. In these scenarios, Equinix Fabric with Google Cloud Interconnect may be a better fitLearn More:Blog: Your Connectivity is Now Your Cloud Equinix Documentation

Related products:Equinix Internet Access (EIA)Partner Integration
What’s New: Online IP Block Management for EIA
What’s New: Palo Alto Networks Prisma AIRS on Network Edge
What’s New: IBX Openings in Madrid & Silicon Valley
What’s New: Network Edge Expansion to Kamloops
What’s New: Fabric 100G Virtual Connection Expansion to Los Angeles
What’s New: Fabric Geo Zones – EU Zone Expansion
What’s New: Fabric 100G Virtual Connections in Miami
Fabric Geo Zones – Network Edge: When to Use it and What to Expect
Welcome to Product Release Notes
What’s New: Fabric Insights Hub
What’s New: EMS Managed Private Storage Block/File
What’s New: Network Edge Expansion to Johannesburg
Fabric Geo Zones (Preview): When to Use it And What to Expect

Fabric Geo Zones (Preview): When to Use it And What to Expect

The Challenge: As organizations scale across regions and clouds, ensuring that sensitive data stays within specific geographic or jurisdictional boundaries becomes increasingly complex. Today, teams often struggle to:Prove that data-in-motion stays within required jurisdictions (not just where it’s stored)   Enforce deterministic routing paths across multicloud and partner ecosystems  Meet regulatory requirements like GDPR, DORA, or healthcare and government policies  Existing approaches often rely on public internet routing, cloud provider backbones, or custom-built architecture that could lack control, forcing tradeoffs between performance, compliance, and operational complexity.  A Better Approach: Fabric Geo Zones (Preview) introduces a new way to define and validate geographic traffic boundaries directly within Equinix Fabric.  Enables policy-based, jurisdiction-constrained routing (e.g., USA-only, EU-only)  Introduces Network Zones to control how and where traffic flows  Provides foundational observability to validate whether traffic aligns with defined policies  Customers define routing boundaries through Network Zones; Fabric applies those constraints during path selection Additional enforcement and IAM controls are planed ahead of general availability – this preview is designed to help teams validate workflows and provide input before GAWhen to Use This: When validating data sovereignty or compliance requirements (e.g., GDPR-aligned routing)   When designing architectures that require traffic to stay within defined geographic boundaries   When testing early implementations of policy-based routing across Fabric and multicloud environments  When Not to Use This: When full production enforcement or complete feature maturity is required   When advanced observability or independent verification of routing guarantees is needed How it Works: Fabric Geo Zones introduces policy-driven controls within the Fabric layer to define where traffic is allowed to flow. At a high level:  Customers define geographic or jurisdictional boundaries through Network Zones   Fabric applies policy-based routing constraints aligned to those boundaries   Observability capabilities provide insight into traffic behavior relative to defined policies   IAM updates support controlled access to policy configuration and management  Expected Outcomes: Performance: Predictable traffic behavior aligned to defined routing policies   Cost: Reduced need for bespoke network engineering to meet sovereignty requirements  Risk: Improved ability to align with regulatory and compliance mandates for data-in-motion What This Means For You: For teams operating in regulated industries, Fabric Geo Zones removes the need to build custom network architecture to meet data sovereignty requirements. You can now define jurisdiction-constrained routing directly within Equinix Fabric, validate it early, and feed back into the GA roadmap.Additional ResourcesPress Release Blog: Data Sovereignty vs. Global AI Scale: The Networking Challenge Facing Every Digital Business Blog: Connectivity Without Compromise: How Organizations Can Ensure Digital Sovereignty 

Related products:FabricNew Product IntroductionGeo Expansion