Why some images are not showing in different/multiple locations?

Scaleflex (Cloudimage, Filerobot) works with CDN providers that offer CDN services globally. The CDN consists of many servers (Points of Presence—PoPs) located worldwide (e.g., Australia, Japan, Singapore, India, Dubai, Israel, South Africa, USA, France, etc.).
If your images are not loading in some locations but they are loading in another location at the same time, this might be because of the following reasons:

1. Your original image has passed its expiration date and/or is no longer available. It may load successfully in some geographical regions because local CDN PoPs requested the image before its expiration and then cached it. Thus, the image will not load in locations where it was never accessed before it expired and/or was unavailable.   

On October 3rd, a user in Mumbai requests an image. The request is sent to the Mumbai-based CDN PoP server. It sends the request to Cloudimage, Cloudimage fetches the image from the origin server, then processes and optimizes it and returns it to Mumbai's PoP. The image is cached on the Mumbai CDN server.

Ten days later, another user in Sydney, Australia, requested the same image. The request is forwarded to a CDN server in Sydney. The image is not in the cache of the Sydney PoP
; thus, it is requested from Cloudimage. Cloudimage tries to get it from the origin server, but the original image contains an expired URL signature, and Cloudimage can't download the asset. So, it returns the default placeholder and the status 404—File Not Found

Note: Cloudimage is an image optimisation/delivery service and not a storage service; if you need a Storage solution, we recommend Filerobot DAM that integrates all Cloudimage features + Storage for Digital Media Assets

2. Check to see if your firewall is turned on.
If yes, then the solution could be to use whitelisting by headers (to whitelisted/accept requests from user agents containing "cloudimg" or "cloudimage").


If you have any questions or issues, please feel free to contact our Software Engineer and mention the following details:

  • Token
  • Short description of the issue (including URLs, screenshot, short video if available)
  • Steps to reproduce the issue.



Was this article helpful?
0 out of 0 found this helpful



Please sign in to leave a comment.