Running on Fastly?

Fastly VCL failing or purges not clearing? We ship it properly.

Fastly rewards teams that treat the edge as code and punishes the ones that treat it as a dashboard. The usual trouble is a VCL change that compiled last week and will not now, a surrogate key purge that leaves a stale object on a different POP, or a Compute@Edge service that builds locally and refuses to activate. We read the service version diff, the compile output and the real-time log stream until the cause is on screen.

  • Since 2015Fixing technology
  • FreeEstimates
  • US teamReal engineers

fastly-deploy.log

still broken

What it is

Fastly at a glance

Fastly is a content delivery and edge compute network launched in 2011, built on Varnish-derived VCL at the edge rather than the simpler rule-based config of its competitors. It runs an any-cast network of points of presence around the world, with instant surrogate key purging as one of its early differentiators.

On top of the cache sits Compute@Edge, a WebAssembly runtime that lets teams write edge code in Rust, Go, JavaScript and AssemblyScript and deploy it in seconds. The platform is popular with news, commerce and streaming workloads that need both aggressive caching and programmable behaviour, and is often chosen by teams who have outgrown a simpler CDN or Cloudflare's rule model.

Type
Edge CDN with programmable VCL and WebAssembly compute
First released
2011
License
Proprietary SaaS
Maintained by
Fastly, Inc.
Typically used for
High-traffic media, commerce, API acceleration, image optimisation, edge compute

The honest version

Fastly pros and cons

No technology is all upside. This is where Fastly earns its place and where it tends to cause trouble.

Where Fastly is strong

  • VCL gives real control at the edgeYou can rewrite requests, split cache keys, stitch together fragments and run A/B logic without going back to the origin, which is still rare outside Fastly.
  • Instant surrogate key purgeTagged objects can be invalidated across the network in under a second, which means publishing systems can rely on cache invalidation rather than short TTLs.
  • Compute@Edge is genuinely usefulWebAssembly modules deploy in a few seconds and run next to the cache, which lets teams move auth, rewrites and personalisation off the origin without a cold start penalty.
  • Transparent real-time logsLogs can stream to S3, BigQuery, Splunk or any syslog sink within seconds, so there is actual visibility into what the edge is doing in production.
  • Honest status and incident reportingFastly's post-incident writeups are among the better ones in the industry, which matters when the edge is the first thing customers see.
  • Image optimiser is competentOn-the-fly resizing, format conversion and quality settings cover most of what a separate image service would do, without another vendor in the pipeline.

Where Fastly bites

  • VCL has a real learning curveIt is not a simple rules UI; it is a C-like language with a strict subroutine model, and a change compiled against one version of the VCL compiler may not compile against the next.
  • Costs scale with bandwidth and requestsThe pricing model is bandwidth plus requests plus Compute, and it adds up quickly for high-traffic consumer workloads once image and video fetches are counted.
  • Purge-all is rate limitedTeams that reach for purge-all during a release will hit the rate limiter and discover that surrogate keys exist for a reason.
  • TLS and domain changes need patienceCustom certificates, CAA records and HTTP/3 toggles all have real propagation times, and support does not speed them up.
  • Compute@Edge is tied to Fastly's SDKsLock-in is less than a Lambda but more than a plain HTTP worker; moving a module to Cloudflare Workers or Vercel's edge is a rewrite, not a copy.
  • Smaller customers get less white-gloveEnterprise customers get dedicated support and architects; everyone else lives on the dashboard and the status page, which is fine until something subtle breaks.

Sound familiar?

Common Fastly problems we fix

The Fastly problems that bring people to us, and what you have once each one is fixed.

VCL compilation failed: unrecognised statement

A VCL change refuses to activate

A snippet that worked on a previous VCL version, a typo in a subroutine hook, or a conflict between a boilerplate snippet and a custom one that references the same variable.

VCL compiles and activates on first try

purge token lacks purge_select scope

Purge calls return 401 or 403

An API token that was created with narrower scopes than the client assumes, or a token that was rotated and never updated in the CMS or publishing pipeline.

Purge works from the right systems

wasm module exceeds 100MB limit

Compute@Edge build is rejected

A WebAssembly binary that grew past the service limit because of a heavy dependency, a static asset that was bundled by accident, or a release build that was never stripped.

Module under limit, deploys cleanly

surrogate key purge: 503 from 2 POPs

Stale content persists on a few edges

A POP that briefly dropped the purge, or surrogate keys that are different between the publisher and the fetcher, leaving one page refreshed and another unchanged.

Content consistent across every POP

503 backend read error: origin sick

Fastly keeps marking the origin as sick

A healthcheck that is too strict for a slow but working origin, an origin that returns the wrong status on the health URL, or a probe interval set too aggressively.

Healthcheck honest, failover sensible

certificate not deployed: CAA missing

A new domain will not go live

A CAA record missing, DNS not yet delegated, or a certificate that was generated with the wrong SAN set and has to be reissued before activation will succeed.

Domain live on TLS first time

Compute: trap unreachable executed

Compute@Edge service panics in production

A Rust unwrap on an unexpected request, or a Go module hitting a nil pointer under traffic that never appeared in staging.

Panics caught and logged

shielding POP returned MISS

Shielding is not working as expected

A shield POP that was moved, or a cache-vary configuration that splits the key differently from what the origin expects, defeating the shield entirely.

Shield hit rate back where it should be

What we do

Fastly help, from VCL to Compute

Get us on a stuck activation, or hand over the entire edge configuration.

Rescue
Activations blocked, purges flaky, or Compute panicking under live traffic. We unblock the edge first and tidy the config second.
VCL and snippet work
Request and response rewrites, cache splitting, authentication at the edge, and VCL that compiles cleanly on today's version and the next one.
Cache strategy
Surrogate keys mapped to real content objects, TTLs set from real freshness needs, and shielding configured for the backends that matter.
Compute@Edge
Edge functions in Rust, Go and JavaScript for auth, personalisation and API aggregation, with observability so panics do not hide.
TLS, domains and HTTP/3
Certificate provisioning, CAA records, custom TLS, and migrations from a different CDN run without a visible outage to users.
Managed Tech
Config in version control, deploys reviewed before activation, log streams pointed at your observability stack, and a team on call when the edge misbehaves.

How it works

From first message to fixed

  1. Look Free estimate

    Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.

  2. Fix

    We fix the cause, not the symptom. If something is down, getting it back up comes first.

  3. Harden

    Backups, monitoring, updates and access, so the same problem can't quietly come back.

  4. Hand back or stay on

    You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.

Often found together

Running Fastly alongside something else?

We work on the whole stack, so the problem can be wherever it actually is.

Questions

Fastly questions

Something else? Call+1 737 727 7327

Why will my Fastly VCL not compile?

Usually a snippet that references a variable in the wrong subroutine, a boilerplate directive that was removed in a newer Fastly VCL version, or two custom snippets that each try to set the same response header. The error points at the line but not always the cause, and the quickest path is to diff the service against the last version that compiled.

Why do some Fastly POPs still serve stale content after a purge?

Either the purge was accepted on a token that is scoped out of some surrogate keys, two publishers are emitting different surrogate keys for the same object, or a rare POP returned a 503 on the purge and nobody retried. Real-time logs show which POPs confirmed the purge; the fix is usually tightening key emission on the publishing side.

How do we move to Fastly from Cloudflare?

The CDN parts move cleanly if you port rules into VCL rather than translating them one to one. The harder parts are WAF semantics, Workers that must become Compute@Edge functions, and DNS cutover windows. We do these with a parallel setup on a test hostname first, then flip TTLs and DNS on a scheduled window.

When does Compute@Edge beat an origin function?

When the work is small, latency sensitive, and benefits from running next to the cache: auth checks, header rewrites, feature flags, and personalised fragment assembly. Heavy work, database access and anything that needs consistent state is better left at the origin or in a backend service.

How do we keep Fastly costs under control?

Bandwidth is the lever, not requests. Tune image optimiser quality, enable Brotli, set sensible TTLs so repeat views are hits, and think hard before running video through the same account without dedicated pricing. We give a before and after on the invoice as part of the engagement.

How much does Fastly help cost?

A written estimate is free. Share the service, the traffic shape and the issue you are seeing, and a number comes back before any work is booked.

Free estimate

Fastly giving you trouble?

Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.

  • No charge to find out what it will take
  • If it's urgent, say so

Replies come from a person. By sending, you authorize us to email you back. No marketing.