What is the ZANOG cache project?

TL;DR – Content caches and services hosted within the ZANOG ASN for the good of the internet.

Longer version – Traditionally, Johannesburg is the entry point for most CDN’s wanting to deploy infrastructure in South Africa. Network operators that are not based primarily in JHB, are therefore forced to build infrastructure to JHB to connect to CDN’s here. This is often costly, and creates centralised distribution points which may be overwhelmed. In an effort to bring content closer to the end users, minimise long-distance transport costs for regionalised operators, and democratise the spread of content delivery, a few of the ZANOG voluneers started contacting CDN operators to persuade them to deploy regionalised caches. The initial deployment started in Durban when a few CDN’s agreed to provided hardware if the ZANOG team could take care of the rest. The ZANOG volunteers sourced sponsored cabinet space, bandwidth to fill the respective CDN caches, and a high-speed means to distribute this in each region. Having this content connected via a local IXP, helps to deal with peak traffic so that lower bandwidth links don’t get congested at peak times. Localising content means that users realise an enhanced end-user experience, with fewer risks to disruption to service, re-routing options, if a problem *does* exist but more importantly, it created an awareness of the need for a more vibrant regional interconnection ecosystem.

Where are the caches?

The first cache was spun up and started serving content in Durban, in November 2018. By popular demand, in late 2020, the a cache cluster in Cape Town was spun up, with an additional set of caches made available in February 2026.

How can I get access to the content?

The cache clusters are connected to the DINX, CINX, and NAPAFRICA Cape Town Internet exchange points respectively. To request peering with ZANOG, simply connect to the Connect to the IXP and send a bilateral peering request to ZANOG. The ZANOG team maintain an active and accurate PeeringDB record, and we encourage peers to do the same.

Why can I not connect to this over .. XYZ?

As a non-profit, volunteer association, ZANOG has minimal resources. We are open to working with any IX and/or Data Centre operator that is willing to working with us, for mutualistic benefit.

Do I have to pay to peer with ZANOG?

ZANOG does not charge to access content within the cache project. see “How can I get access to the content?” Thanks to sponsors for rack space, power, equipment and cachefill bandwidth (to name a few things), access remains free.

Who covers ZANOG’s costs?

Initially, some ISP’s came together and offered various parts of the cache-fill. Later, ZANOG received a grant from ISOC that helped with equipment purchase and some cache-fill bandwidth. In 2020, in preparation for expansion to CPT, ZANOG received funding from operators to obtain its own Internet number resources. Today, ZANOG succeeds because the community invests in it. The largest ongoing cost is funded by sponsors and donors, and the cache project could not survive without them. We have continued support from INX-ZA (DINX, CINX and JINX) and ADC (hosting at ADC CT1), and most recently Teraco (hosting at Teraco CT2).

Is this a long-term project?

The CDN project has already created immense value for regional operators, and has even had some CDNs comment that they have seen more usage in a specific geography than they expected. Ultimately, the ideal situation is for the CDNs in question to build up enough of a foothold for their product and services in each region, and then deploy, manage and run their own infrastructure in-region. This has already happened with some CDNs, and we are hopeful that this experience will spread.

A note on other CDNs – Cloudflare has a full deployment in Durban and Cape Town (in addition well to JNB). Facebook and Akamai have caching nodes in Durban for static content.