Production alias returns 404 NOT_FOUND

Hi Freemck, That Output view is a useful clue. If the deployment output only contains the default SVG assets, then Vercel likely did not deploy the actual Next.js app routes for...

Recurring 494 REQUEST_HEADER_TOO_LARGE across all routes, including clean browser profiles

Hi Volcanoindustry, The new alias test is a useful clue: a different hostname would not receive the same browser cookies as `volcano-manager.vercel.app`, so I’d still treat this as...

Latency of AI Gateway in AISDK

Hi Flo, I’d avoid treating 300–700ms as expected Gateway overhead until you confirm the Gateway request is hitting the same upstream path as your direct Vertex request. For a...

Intermittent TLS / Edge Routing Failure on Wildcard Subdomains (*.daneh.co)

Hi Hooman, Your `curl --resolve` test is the strongest signal here. Since `curl --resolve` still sends SNI for the hostname, a consistent TLS hang on only some resolved IPs is much...

Push_merge operations to "main" no longer trigger automatic deployment (Production or Preview).

Hi Tilanddi, Thanks for checking all of that. Just to clarify, I’m not Vercel staff, so I can’t inspect internal GitHub App delivery logs or deployment queue logs for the project...

AI Gateway: silently disabling OpenAI BYOK

Hi Rafael, Your 64/65 character boundary test is a really useful signal. I’d treat this as two separate issues: 1. the upstream OpenAI request rejects an oversized safety/user...

Reg: Next.js Version 15 - LTS

Hi Sundaramishacbe, For a multi-year freeze, I would not plan around a Next.js 17 release date unless the Next.js team publishes one. The public support policy currently lists 16.x...

Root domain gets ERR_SSL_PROTOCOL_ERROR on Vercel, but www works

Hi Sergio, The key clue is that `sergiomjsp.com` and `www.sergiomjsp.com` are resolving to different places. A redirect from the root domain to `www` only helps after the browser...

Domain claim fails with "TXT record not found" even though TXT is publicly resolvable

Hi Marlik, I’d verify this against the authoritative nameservers directly, not only Google Public DNS. Public resolvers can show a cached/partial view, while the claim check may...

Next.js 16.3 + Bun runtime (1.3.12) build failure on Vercel, while Bun 1.3.14 works locally

Hi CoffeePuma55644, Since you reproduced it with a fresh Next.js 16.3 app, I’d treat this as a compatibility issue between Next.js 16.3 and the Bun runtime path, not just your...