Google Global Cache (GGC) allows ISPs to serve certain Google content from within their own networks. This eases congestion within your network, and reduces the amount on traffic on your peering and transit links. If you do not currently host a GGC node, but would like to enquire about availability, please use this web form. GGC features

The GGC application is designed with redundancy at many levels, including serving locations, servers, network and physical storage. GGC deployments are sized according to current and projected user demand. Over-provisioning is not a supported redundancy strategy. Cache-fill in a multi-node deployment

2013年10月10日 · The GGC server on 208.117.227.31 sees the user's source IP NAT'ed as 208.117.8.0/24. It can to send traffic back to192.168.1.2 through the CGN servers ( the green path ). Traffic from the user 192.168.1.2 is directed towards sites on …

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. The GGC Batch Repairs system is in a restricted Beta testing phase.

GGC nodes that are behind Google routers have additional subnet requirements because of interconnects needed to connect them to the ISP network. Up to 4 interconnects per Google router are supported. Each interconnect may be configured with either IPv4, IPv6, or …

GGC egress-ingress ratio Egress-to-ingress ratio measures the ratio between the asset egress and the cache fill for a single GGC serving point. A simple interpretation of this value is that the node is serving X many times the amount it is downloading at this point in time" where X is the value observed on the graph.

All communities supported by GGC/Google peerings are in the "15169:" space, to avoid conflict with any communities already in use on your network. The same community tags can be used with GGC nodes as well as direct interconnections to AS15169. Supported Communities Communities for Indicating Access Technology

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.

All GGC machines receive regular automated software maintenance, which may result in the machine being restarted. If disk checks are also required, it may be more than an hour before the machine is back online.

GGC servers cache content dynamically, according to local user demand and the storage capacity available. We don't pre-fill the caches in any way. Cache-Fill traffic sources. GGC is a hierarchical CDN. For each GGC node, the source for cache-fill data requests is dynamically selected from one or more of: GGC nodes in your network