# CDN origin timeout increased to two minutes

By Steven Van · 2025-05-08

The proxied request timeout rises from 30 to 120 seconds on every plan, cutting 504 errors on slow backends like LLM calls.

Vercel's CDN now waits up to **120 seconds** for a backend to start responding, up from 30 seconds. The longer proxied request timeout applies on all plans at no extra cost and needs no configuration.

The timeout governs how long the CDN allows an external backend to respond before cancelling the request. Once the backend sends its first byte, it can keep going past two minutes as long as it sends data at least once every 120 seconds. [Vercel](<https://creatorstoolbox.com/tools/vercel>) says this improves reliability for workloads with long processing times, such as LLM generation or complex data queries, and cuts down on 504 gateway timeouts. The [change](<https://vercel.com/changelog/cdn-origin-timeout-increased-to-two-minutes>) took effect immediately on 8 May 2025.

![Vercel](<https://www.google.com/s2/favicons?domain=vercel.com&sz=128>)

Vercel

The platform for frontend developers — deploy, preview, and scale web apps and AI agents with zero config.

[View Vercel →](<https://creatorstoolbox.com/tools/vercel>)

[Original source](<https://vercel.com/changelog/cdn-origin-timeout-increased-to-two-minutes>)

[Read CDN origin timeout increased to two minutes on Creators Toolbox](<https://creatorstoolbox.com/blog/vercel-cdn-origin-timeout-increased-to-two-minutes>)

---
Canonical source: https://creatorstoolbox.com/blog/vercel-cdn-origin-timeout-increased-to-two-minutes