Vercel Tracing reaches GA, and retention jumps to 14 days
Request tracing is now generally available on every Vercel plan, with Pro retention up from one day to fourteen and a new searchable Traces page.
Vercel Tracing left beta on 6 November and is now generally available on Hobby, Pro and Enterprise. The headline change is retention: Hobby goes from 1 hour to 3 days, Pro from 1 day to 14 days, and Enterprise from 3 days to 14 days.
The dashboard gets a new Traces page that consolidates spans and traces in one place, searchable with Kibana Query Language, plus a Live mode for streaming requests as they happen. The CLI uses the same query syntax, so vercel traces inspect <request-id> works from a log line without opening the dashboard. Pricing is unchanged from beta: Hobby includes 1 million span units a month before tracing pauses team-wide, Pro and Enterprise pay $0.50 per million.
This sits alongside the existing default: new Next.js 16.5+ projects still get tracing turned on automatically, with @vercel/otel injected for framework spans.
Why it matters: a one-day or one-hour retention window means a trace is often gone by the time someone reports the bug. Fourteen days on Pro is long enough to actually catch an intermittent production issue after the fact, which changes tracing from something you check in the moment to something you can go back and search.