Is fastly.com slow?

One Fastly surface: the www.fastly.com marketing homepage, about 665 KB of HTML served through Fastly's own cache. Fastly puts its own site on the CDN it sells, so the page shows how a cold request to that CDN is answered from each of our cities. It does not stand for your Fastly service: your origin, VCL, cache rules and shielding decide what your visitors see. From outside we cannot tell a cache miss from a longer path to the edge, and we do not know which point of presence answered beyond the address it used.

Between 27 September and 10 October 2026 Amsterdam, Montreal, Singapore, Tokyo and Mumbai all had a typical time of 12 to 15 ms, and San Francisco 72 ms. San Francisco's daily median was 55 to 81 ms on 11 of the 13 runs and 575 ms on 29 September and 314 ms on 2 October, never close to the rest: whatever edge our San Francisco worker reaches, it is not as close as the other cities' edges are to them. The other five cities' daily medians never left 10 to 22 ms. Their slower times split: 20 ms in Amsterdam and 33 ms in Singapore, but 612 ms in Tokyo, 703 ms in Montreal and 1,365 ms in Mumbai, from a handful of slow requests that never moved a daily median. The six different addresses across our cities in the controlled run fit an edge network. Netlify shows the same shape with Amsterdam as the outlier; Vercel is slower in five of the six cities, San Francisco being the exception.