[sitepodmatt]

Imgix is okay, support is terrible, and status page can stay green for 15minute when they are down (eg recent fastly issue). We stuck with them when image processing was slow due to capacity which the CEO eventually publically apologised for, but in new projects we will probably avoid them.

[_Codemonkeyism]

With support I've meant the answers I got from technical support and the timing with issues.

Yes the 15min made me angry too, as I needed to read about the Fastly fail on HN instead of the Imgix status page.

What would you use in your next project?

[sitepodmatt]

We used imgix on last project as a last line of defense against unoptimized images due to the timing constraints of the project. However on greenfield, we would build the image optimization into the build process (could be as simple as few imagemagick commands), and the save pipeline for CMS'ish part (content blocks, adding products etc..) and then just use a dumb CDN.

Imgix really annoyed me as they didnt bother replying about the status page fiasco, this is after we gave them a free-pass with their capacity planning which made us look like idiots recommending them (i.e images loading super slow). Not again, bad ethics.

[_Codemonkeyism]

Ah been there with the imagemagick in several companies, would never go that way again.

[corobo]

Wait people get annoyed at 15 minutes now? I honestly read your comment as if it was 15 hours at first and agreed but come on, 15 minutes is nothing unless you're paying for a five nines SLA.