Is netlify.com slow?

One Netlify surface: the www.netlify.com marketing homepage, about 410 KB of HTML that Netlify serves from its own CDN cache. Netlify hosts it on the same delivery network it sells, so the page shows how that network answers a cold request from each of our cities. It does not stand for a site you deploy there: your build output, redirects, functions and cache headers set your own numbers. We cannot see Netlify's cache from outside, so a slow request could be a cache miss or the path from our worker to the edge; the timing alone does not say which.

Between 27 September and 10 October 2026 five cities had a typical time of 23 to 38 ms and Amsterdam 73 ms. Amsterdam's daily median stayed between 68 and 87 ms on 12 of the 13 runs and reached 141 ms on 3 October, so this is a steady difference rather than a few slow days. Montreal moved during the window: 22 to 23 ms on three runs and 35 to 45 ms on the other ten, which the pooled typical of 38 ms sits between and the history chart shows. Mumbai, Tokyo and Singapore were the quickest at 23 to 26 ms. Fastly, measured the same way, is faster still in five cities and slower in San Francisco; Vercel is slower in every city, by the smallest margin in Amsterdam (87 ms against 73 ms).