vercel httpstat

The command works like , but automatically handles deployment protection bypass tokens for you. It provides visualization of HTTP timing statistics, showing how long each phase of an HTTP request takes. When your project has Deployment Protection enabled, this command lets you test protected deployments without manually managing bypass secrets.

The command runs the tool with the same arguments you provide, but adds an header with a valid token. This makes it simple to measure response times, analyze performance bottlenecks, or debug latency issues on protected deployments.

Get timing statistics for your production deployment:

Analyze timing for a POST request with JSON data:

Test timing for a specific deployment by its URL:

Run multiple requests to get average timing statistics:

When you run :

1. The CLI finds your linked project (or you can specify one with )
2. It gets the latest production deployment URL (or uses the deployment you specified)
3. It retrieves or generates a deployment protection bypass token
4. It runs the tool with the bypass token in the header
5. The tool displays a visual breakdown of request timing phases: DNS lookup, TCP connection, TLS handshake, server processing, and content transfer

The command requires to be installed on your system.

These are options that only apply to the command.

The option, shorthand , lets you specify a deployment URL to request instead of using the production deployment.

The option, shorthand , lets you provide your own deployment protection bypass secret instead of automatically generating one. This is useful when you already have a bypass secret configured.

You can also use the environment variable:

The tool displays timing information in a visual format:

• DNS Lookup: Time to resolve the domain name
• TCP Connection: Time to establish a TCP connection
• TLS Handshake: Time to complete the SSL/TLS handshake (for HTTPS)
• Server Processing: Time for the server to generate the response
• Content Transfer: Time to download the response body

Each phase is color-coded and displayed with its duration in milliseconds, helping you identify which part of the request is taking the most time.

Make sure is installed on your system:

Make sure you're in a directory with a linked Vercel project and that the project has at least one deployment:

If automatic token creation fails, you can create a bypass secret manually in the Vercel Dashboard:

1. Go to your project's Settings → Deployment Protection
2. Find "Protection Bypass for Automation"
3. Click "Create" or "Generate" to create a new secret
4. Copy the generated secret
5. Use it with the flag or environment variable

When using , verify that:

• The deployment ID or URL is correct
• The deployment belongs to your linked project
• The deployment hasn't been deleted

The following global options can be passed when using the vercel httpstat command:

For more information on global options and their usage, refer to the options section.

• Deployment Protection
• vercel curl
• vercel deploy
• vercel inspect