Google Peering is the option in the Secure Connect family with the most client ownership attached to it. It offers real benefits — direct interface with the Google network, low cost, high bandwidth, but Pega does not support the connection itself, and Google does not offer an SLA. Set expectations accordingly.
What it means
Pega Cloud Secure Connect enables the use of Google Peering to establish a public peering connection with the Google network. Access points are listed in the Google Peering Database.
Availability: Google Peering is only available via Secure Connect in GCP deployment regions for Pega Cloud. Clients on AWS deployment regions use one of the other Secure Connect options.
The distinguishing characteristic is directness — you interface with Google and remove intermediate networks from the traffic path.
What it does
-
Improved reachability, reliability, and resilience, drawing on Google’s existing peering agreements with ISPs.
-
Low up-front and ongoing maintenance cost.
-
High bandwidth support.
-
Choice of model: Google Direct Peering or Google Carrier Peering.
-
Intermediate networks removed from the traffic path.
How it works
- Pega’s role is narrow. Pega enables Google Peering in GCP deployment regions, and triages Pega Cloud networking issues to help you determine whether a problem relates to your peering connection. That is the extent of it — Pegasystems does not provide direct support for establishing or maintaining Google Peering connections.
- Your role is everything else. Set up and maintain the peering connection with Google. Work with Google directly to resolve peering issues. Set up controls for the public peering connection. Understand the performance impact, and assess the cost implications.
- Setting it up: follow Google’s prerequisites for a peering connection, submit a Peering Request in the Google ISP Portal, then submit a Google ISP Portal Access Request. Note the ordering — the public peering connection must be established before you submit the access request. All of this is transacted directly with Google.
What to remember
-
No SLA from Google for Google Peering. For a client whose requirement is a contractual availability commitment, this option does not meet it.
-
BGP prefix filtering is not supported in Google Peering. If route control is central to your design, this is a material constraint and points toward a different option.
-
Pega will not troubleshoot the peering connection for you — only triage far enough to identify where the problem sits. Make sure the client’s network team understands they own this.
-
GCP deployment regions only.
-
Sequence matters in setup: peering connection first, ISP Portal access request second.
Technical documentation: Google Peering