CODEWITHSUNDEEP
cloudinary
Paul
Paul

Reputation: 3

Why is Cloudinary serving images from California to UK location?

I'm having a weird problem with Cloudinary. We moved over last week and found that our image load times were now significantly worse than serving the images from our AWS server. Looking into it, it appears that the images are being served from the ip address 151.101.17.137, which is in San Francisco. I'm finding that similar sized images are taking 3 times as long to load when compared with images being served from the AWS server.

So why does the CDN appear not to be working?

We've already implemented PRECONNECT as advised by Cloudinary.

Using Chrome Devtools and webpagetest.org I can see each of the Cloudinary image responses with a long ttfb and Header Response, Remote Address: 151.101.17.137

Any help or advice would be appreciated.

Upvotes: 0

Views: 81

Answers (1)

Igy
Igy

Reputation: 43816

Adding to James' comment above, that IP is Fastly's but the location the traffic is served from may differ based on where you're accessing it from.

Likely, the IP is part of an Anycast network and served from multiple locations

Upvotes: 1

Related Questions