10 engineers on Hacker News describe using Fastly first-hand: 6 endorse it, 0 regret it, 0 are mixed.
“Even with a CDN cache (shoutout fastly) our catalog is simply too broad to fully saturate the cache while still allowing pages to be updated in a timely manner.”
endorse · production · cupofjoakim · 2025-10-29 · source ↗ · wrong label?“we push all the requests through fastly, which pushes the logs to s3”
endorse · production · mannyv · 2025-03-15 · source ↗ · wrong label?“I've been playing with it on some of my dev servers and so far it's amazingly stable and configurable.”
endorse · personal · maxk42 · 2019-12-13 · source ↗ · wrong label?“As a user, Fastly is really, really good.”
endorse · production · tylermenezes · 2019-04-19 · source ↗ · wrong label?“we like the reliability story of running all of the heavy lifting through fastly's CDN.”
endorse · production · fizx · 2016-12-21 · source ↗ · wrong label?“We switched from Cloudfront to Fastly and couldn't be happier. These guys are awesome and the product is top notch.”
endorse · production · cmer · 2013-11-06 · source ↗ · wrong label?“We used them until we moved to fastly, which does iplocation stuff as part of their service.”
neutral · production · mannyv · 2025-04-23 · source ↗ · wrong label?“For CDNs we switched from Fastly to Cloudflare because we needed support for SSH (port 22)”
neutral · production · sytse · 2020-10-23 · source ↗ · wrong label?“when our relationship with CloudFlare ended and we moved to Fastly”
neutral · production · thefarseeker · 2017-01-10 · source ↗ · wrong label?“Fastly (with a CloudFront fallback) for the static files we serve our users.”
neutral · production · bosdev · 2015-07-25 · source ↗ · wrong label?