Robust: GGC provides resilience through multiple levels of redundancy, which are transparent to users. Google ensures that users are always served from the best available data location, even in the event of a temporary outage.
Monitoring GGC Google conducts extensive monitoring of all GGC nodes and the GGC Support Team are automatically notified of any faults materially affecting the performance of a GGC node, or of individual GGC machines. Fault tickets raised by GGC Program Partners or contracted third parties may:
Background Google supports the exchange of BGP community tags with GGC nodes and peering sessions to signal important properties of a prefix for reporting, load-balancing, or policy enforcement. All
Carrier Grade NAT Introduction This document describes how to configure Google Global Cache (GGC) nodes to operate with your Carrier Grade NAT (CGN) systems. Once configured, this allows traffic between the GGC node and private user IPs to bypass the CGN. GGC has no requirement that "private IP space" be in the RFC1918 allocation.
Measured in Gbps, the majority of GGC traffic is cacheable YouTube content. High-volume traffic can be served to users by a local GGC node, or from Google core data locations via peering and transit. For high-volume traffic, our systems map user requests to serving locations based on the IP prefixes we see advertised at GGC and peering.
We make use of either static routes or Router Advertisements to configure the default IPv6 gateway on the GGC machines: If you prefer we use a separate gateway as advertised via Router Advertisements, ensure these are enabled and working properly.
GGC Batch Repairs is a system for ISP Partners to self-manage selected repairs for the GGC nodes they host. The differences between the way GGC repairs have traditionally been managed, and the self-management enabled by GGC Batch Repairs are described below.