Troubleshooting delivery from a specific CDN provider

pludlow

Cloudinary uses a multi-CDN solution incorporating Akamai, Cloudflare, and Fastly to ensure a highly available and performant media delivery platform. This approach enables efficient distribution of media assets across the web, reducing latency and improving overall performance.

Typically, it is best to let Cloudinary automatically determine the most efficient and performant CDN provider. However, there may be times when troubleshooting issues or testing delivery between providers is necessary. To do this, change the default subdomain of res.cloudinary.com  in a URL to instead use a subdomain specific to a particular CDN provider.

The following subdomains are used for each provider:

CDN Provider	Subdomain	Example
Auto (default)	res.cloudinary.com	https://res.cloudinary.com/demo/image/upload/beach_huts.jpg
Akamai	resa.cloudinary.com	https://resa.cloudinary.com/demo/image/upload/beach_huts.jpg
Cloudflare	resc.cloudinary.com	https://resc.cloudinary.com/demo/image/upload/beach_huts.jpg
Fastly	resf.cloudinary.com	https://resf.cloudinary.com/demo/image/upload/beach_huts.jpg

DannyFromCloudinary

Hey @pludlow - this is a great post! Thanks for the share :)

For anybody reading this, it is stated above, but just to reiterate, using a delivery domain other than res.cloudinary.com should only be used for debugging purposes. For instance, if your site's users are complaining that images aren't appearing correctly, and you can't reproduce the behaviour, testing our CDN partners one-by-one could be a good way of identifying an issue.

Using resa., resc. or resf. in production is not recommended

pludlow

Thanks for the emphasis @DannyFromCloudinary. I've updated the title to make it more clear that this is a troubleshooting method, and that it shouldn't be a common practice.