Understand US Ring Fencing in Umbrella Secure Web Gateway

Available Languages

Download Options

  • PDF     (3.3 KB)
    View with Adobe Reader on a variety of devices
  • ePub     (80.5 KB)
    View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
  • Mobi (Kindle)     (65.2 KB)
    View on Kindle device or Kindle app on multiple devices
Updated:October 21, 2025
Document ID:225247

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

    Introduction

    This document describes how Cisco Umbrella Secure Web Gateway provides US Ring Fencing.

    US Ring Fencing in SWG

    US Ring Fencing in Umbrella’s Secure Web Gateway (SWG) ensures that traffic for US customers stays within the US. This functionality minimizes the possibility of US traffic crossing the Canadian border based on geographic location.

    Umbrella's Canadian DCs are configured to do a Geo-IP check when a customer looks up the proxy address: swg-url-proxy-https.sigproxy.qq.opendns.com. If the customer IP is detected to be located in the U.S., the traffic can be redirected to a US data center.

    US Ring Fencing currently only applies to Umbrella's Canadian data centers. This means, based on availability, if US customer traffic hits Vancouver, the traffic can be redirected to LAX, DFW, or PAO in order of availability. If US customer traffic hits Toronto, the traffic can be redirected to CHI, NYC, or MIA in order of availability.

    Revision History

    Revision Publish Date Comments
    1.0
    22-Oct-2025
    Initial Release
    TAC Authored

    Contributed by Cisco Engineers

    Was this Document Helpful?

    FeedbackFeedback

    Contact Cisco

    This Document Applies to These Products