SteamCache Program

Valve operates a SteamCache program, where ISPs or IXPs can host one or more SteamCaches.

SteamCaches are servers which cache Steam content traffic and are deployed within a host network. SteamCaches can reduce traffic between an ISP and Valve by up to 90%, and can increase download performance for Steam users.

SteamCache server details/requirements:

• 1RU server
• 2 x 100G connectivity for in-band networking
• 1 x 1G RJ45 connectivity for out-of-band (OOB) management
• Public IPv4 and IPv6 addresses for in-band networking and OOB management
• 350W of available power, with redundancy
• BGP sessions (IPv4 and IPv6) to the SteamCache for advertising client prefixes
  • You must have a public ASN and an up-to-date PeeringDB entry

The host ISP or IXP provides power and connectivity, including public IP addresses and transit service. SteamCaches fill on demand, typically at a rate of 5-10% of their downstream traffic, and so they require connectivity back to Valve either via transit or a peering connection.

Local Steam users’ requests are directed to SteamCaches based on which prefixes are advertised to the SteamCache over the BGP peering session. Steam users with source IP addresses within those prefixes will prefer the local SteamCaches as their first option, with automatic fallback to other locations when the SteamCache is unavailable.

A typical SteamCache can deliver up to 100Gb/s of cached content. Larger networks can host multiple SteamCaches if required.

The minimum traffic level to justify a SteamCache is 20Gb/s.

If you meet these requirements (or with a little flexibility), and wish to request a SteamCache, email us at peering@valvesoftware.com.

Note: we are not able to support caches in all countries.