A customer reports that saving a form sometimes takes too long. Before changing code, the team needs to find which part of that request is waiting. A trace breaks the request into recorded steps, called spans.
On September 29, 2026, Vercel announced trace search in its command-line tool. It gives developers another way to find those steps while investigating a production issue.
What the update adds
The new vercel traces search command can filter a project’s spans by environment, service, status, deployment and several request identifiers. Time filters narrow the investigation, and JSON output lets scripts work with the results.
Vercel also documents queries for duration and other span attributes. This is a search capability for trace data; it does not make an application faster by itself.
Sources and release notes: [1]
Start with the affected action
Our suggested approach is to begin with a specific user action and time window. Compare a slow attempt with a successful one. Look for time spent in a database query, an external service or another recorded step before deciding what to change.
An empty search should prompt a check of the selected project, environment and available telemetry. It is not enough evidence to conclude that customers had no problems.
Turn findings into an operational habit
For a business, the useful outcome is a clearer explanation of a failed or delayed action and a focused fix. Keep a short incident record: the affected workflow, evidence, change and the result observed afterward.
We would compare the same workflow before and after a change, including error rates and slower requests. A new debugging tool is valuable when it helps the team close that loop.
Sources and release notes
Original analysis by AtmosGate, based on the sources below. Vendor claims and release status are attributed to their publishers.
- Search trace spans from the Vercel CLI
Vercel · 29 September 2026