shipfeedAI news, curated daily

02:41:33 CET
21 MAY02:41:33shipfeed
pull to refreshlast sync
Just in — 30 new
§ feed · storyline

CDN origin timeout increased to two minutes

Vercel increases its CDN origin timeout from 30 to 120 seconds across all plans at no extra cost, reducing 504 errors for long-running workloads such as LLM generation.

May 8 · · primary fetch1 sourceupdated May 8 ·

Vercel’s CDN will now wait up to 120 seconds for your backend to start sending data, up from 30 seconds. This extended proxied request timeout is now available on all plans at no additional cost. The defines how long our CDN allows your to respond before canceling the request. After the initial byte is received, your backend can take longer than two minutes to complete the request, as long as it continues sending data at least once every 120 seconds.proxied request timeoutexternal backend This update improves reliability for workloads with long processing times, such as LLM generation or complex data queries, and reduces the chance of 504 gateway timeouts.

This change is effective immediately, with no action or configuration required. Read more

read full article on vercel.com
§ sources1 publication · timeline below
  1. vercel.comCDN origin timeout increased to two minutesprimary