Has anyone used the Tinify CDN service?

RaptureForums

Active member
Hello,
I stumbled across the Tinify CDN service after checking out the Tinypng.com site.


Has anyone here used this CDN service?

It looks like they use multiple CDNs for their service.

Thank you.
 
Just use Cloudflare like everyone else. :P
I hear you. I use Cloudflare and like the actual service, BUT I hate their customer service which usually involves just them pasting and copying stuff from the docs without taking the time to break things down for some of us that aren't so technically learned. That, in addition, to closing tickets when they haven't answered our questions completely. Finally, it is sometimes a week before they answer back.

I hate paying companies that don't seem to care about their customers. Especially, paying customers. I would expect their replies and lateness on responding to tickets for someone on the FREE account, but not on the PAID account.

I setup a Cloudfront account and it worked pretty good. Better than using Bunny, KeyCDN, etc. that don't have a WAF as part of their CDN. Still got the Chinese bots in on Cloudfront that Cloudflare blocked. But not as many as the others let in. But still way too many. I used Cloudfront's block geographic location and it helped a little, but not much. I need to find out if they have a block by AS Num as that works well with Cloudflare. I'll have to look that up and see if I can find anything on that.

I guess I will just keep paying Cloudflare. :rolleyes:
 
I spoke to a representative at TinyCDN. I asked who the 3 CDN providers where and she said that they currently used Fastly and CloudFront. She said they had Stackpath in their network but they recently stopped their service, so they were down to 2 CDN providers.

She did admit they don't have a bot service like Cloudflare. She did give me this link that was interesting in regards to using multi-CDNs.


Ironically, it mentioned Fastly's service interruption as well as Cloudflare's service interruption.

I think the multi-CDN strategy has merit to it, but my site is not mission critical. But I could see how some sites might benefit from a multi-CDN strategy. 🤔

I will probably stay with Cloudflare, but I thought I'd share for any one else who might be interested. I think their lowest plan is $15 for one CDN and I think Fastly is more than that to start if you go straight through them, so it could be a chance for someone to see how Fastly performs if you have ever wondered. I'm not sure if they give you a chocie if you sign up for the $15 plan. 🤔
 
There's certainly some merit to redundancy, however you are most likely going to have less outage time if you go with a singular provider vs trying to manage failover and redundancy upstream of them. Fastly, Cloudfront and Cloudflare all have plenty of built-in redundancy (Cloudflare for example has POPs in over 320 cities, and some of those cities have multiple even within the same city).

The whole point of those providers running Anycast networks is so that any of their data centers can respond to any request (one city goes down, and users are automatically routed to a different one). No IP address changes needed or anything else that takes time to propagate (the IPs are the same regardless of which data center is serving the request). The chances of every data center going down at the same time is so infinitesimally small that it's not worth trying to mitigate that probability yourself (there's a higher chance that your failover mechanism would be the point of failure for your sites). If a major CDN like Cloudflare or Cloudfront actually went down completely, it's probably a good day to go outside and touch grass because the Internet as a whole more or less would be crippled and let them worry about getting a good chunk of the Internet back online.

Some reading on Anycast here if you want:

 
Back
Top Bottom