Netlify Performance: Benchmarks, Latency & Limits 2026
Netlify is fastest on its CDN, near 170ms TTFB, while cold functions run to ~900ms. Functions auto-scale on Lambda; Edge Functions enforce a 50ms CPU budget.
Netlify Performance verdict
Netlify is fastest where it serves static assets.
Independent Bejamas and Checkly monitoring put its CDN near 170ms TTFB from US East, while cold serverless functions ran to 877ms and edge functions to 1,559ms in the same worst-case run. Functions auto-scale on AWS Lambda with no published concurrency cap.
Route everything you can through the CDN, because that is the fast path. Reserve serverless functions for genuinely dynamic work, keep them warm to dodge the ~900ms cold start, and pin each one to the region nearest its database. Use Edge Functions for light personalization within the 50ms CPU budget, not heavy compute. The 99.99% SLA is Enterprise-only, so lower tiers run without a contractual guarantee.
- Bejamas runs checks hourly, so the serverless and edge numbers are cold-start-dominated worst cases. Production traffic that keeps functions warm is markedly faster.
- Netlify publishes no serverless concurrency cap, since functions auto-scale on AWS Lambda, so plan for invocation-based billing rather than a fixed ceiling. Monthly invocation limits are plan-specific, visible only in the billing dashboard.
- Edge Functions have a 50ms CPU budget per request that excludes I/O wait, which rules out CPU-heavy work at the edge.
- CDN TTFB (independent)
- 170 ms
- Serverless cold TTFB
- 877 ms
- Edge CPU budget
- 50 ms
- Max function memory
- 4 GB
- Enterprise SLA
- 99.99%
This page covers how fast Netlify runs and how it scales. Region coverage and pricing live on their own pages.
Plan Netlify delivery latency by region
- In US East (N. Virginia), Static (CDN) is the fastest measured path at 170 ms.
- Static assets are served from the nearest PoP, so route as much as possible through the CDN and reserve functions for genuinely dynamic work.
Measured independently by Bejamas via Checkly (15 AWS probe locations, hourly, cold-start dominated). Verify against your own workload.
Measured latency by delivery mode
| Delivery mode | Probe region | TTFB | Sample |
|---|---|---|---|
| Static (CDN) | us-east-1 | 170 ms | Checkly, hourly |
| Static (CDN) | eu-central-1 | 303 ms | Checkly, hourly |
| Serverless function | us-east-1 | 877 ms | cold-start dominated |
| Serverless function | eu-west-2 | 1,019 ms | cold-start dominated |
| Edge function | us-east-1 | 1,559 ms | cold-start dominated |
| Edge function | ap-southeast-1 | 1,394 ms | cold-start dominated |
Throughput, scaling and rate limits
| Limit | Value | Notes |
|---|---|---|
| Auto-scaling | 500,000+ visitors | Handles 500,000+ visitors as efficiently as 50 with no manual scaling (Enterprise High-Performance Edge) |
| Edge Function CPU time | 50 ms / request | Tracks script run time only; excludes time waiting on external resources |
| Edge Function header timeout | 40 s | Response headers must begin within this window |
| Function invocations / month | Plan-specific | Varies by team plan; check the usage and billing dashboard |
| Cached edge responses | Not counted | Cached edge-function responses do not count toward invocation limits |
| Concurrent builds | 1 (Free) / 12 (Enterprise) | Run multiple builds simultaneously on Enterprise |
Function scale ceilings
| Limit | Default / Free | Pro / Enterprise |
|---|---|---|
| Function memory | 1,024 MB (1 GB) | up to 4,096 MB (4 GB) |
| vCPU allocation | 0.5 vCPU (1,024 MB) | up to 2.0 vCPU (4,096 MB) |
| Synchronous execution | 60 s (fixed) | 60 s (fixed) |
| Background execution | 15 minutes | 15 minutes |
| Buffered payload | 6 MB (binary ~4.5 MB) | 6 MB (binary ~4.5 MB) |
| Edge Function bundle / memory | 20 MB compressed / 512 MB | 20 MB compressed / 512 MB |
Netlify reliability and architecture
- The Enterprise High-Performance Edge tier carries a 99.99% uptime SLA
- Netlify Functions run on AWS Lambda, and the platform is multi-cloud across Google Cloud, AWS and Deno for Edge Functions
- Netlify's documented Recovery Time Objective is 4 hours
- Netlify is audited against SOC 2 (Type 2), ISO/IEC 27001, ISO/IEC 27018:2019, PCI DSS v4.0.0, HIPAA, GDPR and CCPA
- High-Performance Edge ships proactive DDoS protection and 24x7x365 incident-response on-call rotations
- High-Performance Edge delivers 30 to 50% faster response times than standard plans
Netlify latency benchmarks, independently measured
- Bejamas independently monitored Netlify with Checkly from 15 global AWS probe locations, running each check every 60 minutes so the measurements predominantly capture worst-case cold-start performance
- From us-east-1, Netlify's static CDN answered at 170ms TTFB versus 877ms for a cold serverless function, roughly a 5x gap
- Edge Functions measured slower than serverless on TTFB in this run, 1,559ms from us-east-1, because the checks captured cold starts rather than warm edge execution
- Latency degrades with distance from a probe: af-south-1 saw 1,008ms CDN, 1,388ms serverless and 1,610ms edge TTFB
- Netlify's High-Performance Edge serves static content from 70+ global Points of Presence, the layer responsible for the fast CDN numbers
- Edge Functions run in a Deno-based runtime from the network edge location closest to each user, with optional response caching
Netlify Performance FAQ
How fast is Netlify, and what do independent benchmarks show?
Bejamas independently monitored Netlify with Checkly from 15 AWS probe locations every 60 minutes. Static CDN content answered near 170ms TTFB from us-east-1 and 303ms from Frankfurt. Cold serverless functions ran 877ms from us-east-1 up to 1,388ms from Cape Town, and edge functions measured 1,394 to 1,610ms. Because the checks are hourly, these are worst-case cold-start numbers, and warm functions are much faster.
What is Netlify's concurrency or throughput limit?
Netlify does not publish a serverless concurrency cap. Functions run on AWS Lambda and auto-scale, and Netlify markets handling 500,000+ visitors as easily as 50. Edge Functions enforce a hard 50ms CPU budget per request and a 40s response-header timeout. Monthly invocation ceilings vary by plan and appear in the billing dashboard.
What are Netlify's function memory and timeout limits?
Functions default to 1,024 MB, or 1 GB, and scale to 4,096 MB, or 4 GB, on credit-based Pro and Enterprise plans, with vCPU scaling linearly from 0.5 to 2.0. The synchronous execution limit is a fixed 60 seconds. Background functions run up to 15 minutes, and scheduled functions up to 30 seconds. Buffered payloads cap at 6 MB, about 4.5 MB for Base64 binary.
Why are Netlify Edge Functions slower than serverless in the benchmark?
In the Bejamas run, edge functions showed higher TTFB, 1,559ms from us-east-1, than serverless, because the hourly checks caught cold starts rather than warm edge execution. Edge Functions run in a Deno runtime at the location closest to the user and are built for light, low-latency personalization within a 50ms CPU budget. Caching edge responses keeps real-world TTFB low.
What reliability guarantees does Netlify offer?
The Enterprise High-Performance Edge tier carries a 99.99% uptime SLA on a 70+ PoP network, with proactive DDoS protection and 24x7x365 on-call. The documented Recovery Time Objective is 4 hours. Netlify is audited against SOC 2 Type 2, ISO 27001, ISO 27018, PCI DSS v4, HIPAA, and the infrastructure is multi-cloud across AWS, Google Cloud and Deno.
Sources & verification
| Source | What was checked | Last checked |
|---|---|---|
| Netlify Official | Official product page | July 10, 2026 |
| Bejamas Compare Netlify Vs Vercel | Independent reference | July 10, 2026 |
| Netlify Core Edge | Edge network | July 10, 2026 |
| Netlify Core High Performance Edge | Core High Performance Edge | July 10, 2026 |
| Netlify Developer docs | Limits and quotas | July 10, 2026 |
| Netlify Developer docs | Functions Usage And Billing | July 10, 2026 |
| Netlify Developer docs | Functions Configuration | July 10, 2026 |
Every fact on this Netlify page is tied to a named source and a verification date. Freshness-sensitive figures trace to the sources above; verify against the vendor before relying on them.
Explore Netlify
Every page on Netlify in one place, you are on performance.