CX Agent Studio offers services using
Google APIs
(ces.googleapis.com) designed for high performance and low latency,
leveraging Google's extensive global network infrastructure,
including its many
Points of Presence (PoPs).
Google advertises the IP addresses for its APIs
and services using
Anycast
from numerous Edge PoP locations worldwide.
With Anycast,
the same IP prefix is announced simultaneously from multiple points
in Google's network.
When a user or application makes a request to a Google API,
the internet's routing fabric directs the traffic
to the topologically nearest Google PoP advertising that IP address.
This "nearest" is in terms of network hops and routing metrics,
which generally correlates with geographical proximity.
This minimizes the distance traffic has to travel over the public internet,
reducing latency by getting the request onto Google's high-performance,
low-congestion global backbone network as quickly as possible.
To optimize your connection to Google services, you can move beyond standard internet routing by using Verified Peering Provider (VPP) or Direct Peering. Both options reduce network hops by connecting your infrastructure more directly to Google's edge.
Direct private connectivity using hybrid networking (including Cloud Interconnect to CX Agent Studio is not supported. To mitigate data exfiltration risks and enhance security, it is recommended to implement VPC Service Controls (VPC-SC).
All CX Agent Studio deployment options are supported with inbound access.
Connectivity options
To further optimize performance beyond standard internet routing, you can use peering options to connect infrastructure directly to Google's edge.
Verified Peering Provider (Recommended)
Verified Peering Provider (VPP) identifies Internet Service Providers (ISPs) that have already established diverse, high-capacity, and redundant links to Google.
- Ease of Use: Your ISP manages the peering complexity, BGP configurations, and maintenance.
- Reliability: Partners are vetted by Google to ensure they meet strict performance and redundancy standards.
Direct peering
This provides a physical, direct interconnection between your on-premises network and Google's edge at a mutual Point of Presence (PoP). This service is not the same as the interconnect offerings to establish connectivity to Google Cloud VPC networks.
- Control: You establish a direct BGP session with Google.
- Infrastructure: Requires your own registered Autonomous System (AS) number and physical presence in a colocation facility where Google peers.
Choosing connectivity option
| Feature | Verified Peering Provider | Direct Peering |
|---|---|---|
| Best For | Simplified, managed high-availability access. | Organizations requiring direct control over BGP. |
| Management | Fully managed by your ISP. | Self-managed by your internal network team. |
| Expertise | Low — no deep networking expertise needed. | High — requires AS number and BGP knowledge. |
| SLA | Vetted for reliability. | No Google-provided SLA. |
In essence:
- Choose Verified Peering Provider if you want a simpler, more managed way to get reliable and high-availability access to all Google services, without needing deep networking expertise.
- Choose Direct Peering if you have the technical capability to manage BGP peering, meet Google's requirements, and want direct control over the interconnection, understanding that it comes without a Google-provided SLA.