Reported News
Vercel Tracing is generally available with longer retention and Next.js 16.5 auto-trace
Vercel announced on November 6, 2026 that "Vercel Tracing is now generally available on all plans." Retention is "Hobby now keeps traces for 3 days," "Pro for 14 days," and "Enterprise for 14 days"; new Next.js 16.5 projects get tracing after the first successful build, with dashboard and vercel traces CLI KQL search.
- Changes reported
- 5
- listed below, each from a source we read
- We tested
- Not tested yet
- reported from sources; we did not run it ourselves
- Gaps we flag
- 3
- things we could not verify
- Sources
- 1
- 1 primary, linked below
What changed
| # | What the source says | Status |
|---|---|---|
| 01 | GA: Vercel Tracing is generally available on all plans; pricing is unchanged from the beta per the changelog. | Reported |
| 02 | Retention: Hobby keeps traces for 3 days (was 1 hour), Pro for 14 days (was 1 day), and Enterprise for 14 days (was 3 days). | Reported |
| 03 | Dashboard: a Traces page lists spans and traces with Kibana Query Language (KQL) search and Live mode, beyond the beta's per-request Logs entry point. | Reported |
| 04 | CLI: vercel traces search --query, vercel traces inspect and vercel traces config share the same KQL as the dashboard. | Reported |
| 05 | Next.js 16.5: new projects on Vercel with at least one Node.js function get tracing turned on after the first successful build (100% sampling rule, build-time instrumentation); remove sampling rules to opt out. | Reported |
reported by the sourcemeasured or run by usnot verified
Primary source: Vercel Changelog: Vercel Tracing is now generally available. We are the fast, independent index; the vendor’s own page is the source of record for this release.
In the source’s words
“Vercel Tracing is now generally available on all plans.”
“Hobby now keeps traces for 3 days instead of 1 hour, Pro for 14 days instead of 1 day, and Enterprise for 14 days instead of 3 days.”
“Starting with Next.js 16.5, new projects created on Vercel that include at least one Node.js function get tracing turned on after their first successful build.”
What we have not verified
- We did not enable Tracing on a Vercel project or run vercel traces CLI queries ourselves.
- Pricing line items beyond "unchanged from the beta" were not re-checked on the pricing page.
- Auto-instrumentation behaviour on an existing Next.js 16.5 app was not tested.
This brief is Reported: written from the sources below, not from running the release ourselves.
Sources
- Vercel Changelog: Vercel Tracing is now generally availableprimary source · fetched 2026-11-07
Related
Spotted an error? See our corrections policy or email the address on the contact page. Markdown version for agents: /news/vercel-tracing-ga.md
Want these briefs in your Google Top Stories? Add Agentic Weekly as a preferred source on Google.
Newsletter
The Weekly Verdict. Free, every Monday.
A free email every Monday: the week's few big AI releases, then 5 short use cases for the new models, each with a prompt you can paste.
Free. Double opt-in. One click to unsubscribe.