vercel alerts

The vercel alerts command lists recent alerts for the linked project, a specific project, or an entire team. The inspect subcommand shows details for a single alert group, and the rules subcommand tree manages monitors from the terminal.

By default, vercel alerts reads alerts for the linked project from the last 24 hours. You can change the scope with --project or --all, filter by alert type, change the time range, and switch between table, AI investigation, or JSON output.

Use this command when you want to inspect alert activity from the terminal without opening the dashboard.

# List alerts for the linked project from the last 24 hours
vercel alerts
 
# List team-wide alerts
vercel alerts --all
 
# Filter by alert type and time range
vercel alerts --type usage_anomaly --since 2026-03-01T00:00:00.000Z

These options only apply to the vercel alerts command.

The --project option, shorthand -p, lists alerts for a specific project and overrides the linked project. Pass the project name (the name shown in the dashboard and vercel project ls) or its ID, for example my-app or prj_abc123.

vercel alerts --project my-app

You can't combine --project with --all.

The --all option, shorthand -a, lists team-wide alerts instead of using the linked project.

vercel alerts --all

You must be in team scope to use --all.

The --type option filters by alert type. You can repeat the flag or pass comma-separated values.

vercel alerts --type usage_anomaly
vercel alerts --type usage_anomaly,error_anomaly
vercel alerts --type usage_anomaly --type error_anomaly

Filter by custom alert type:

vercel alerts --type custom_alert

The --ai option prints AI investigation sections instead of the default table output.

This view includes the alert title, resolved time, summary, and key findings when that data is available.

vercel alerts --ai

The --since option, shorthand -s, sets the start of the time range. Use an ISO 8601 timestamp.

If you don't pass --since or --until, the command defaults to the last 24 hours.

vercel alerts --since 2026-03-01T00:00:00.000Z

The --until option, shorthand -u, sets the end of the time range. Use an ISO 8601 timestamp.

vercel alerts --since 2026-03-01T00:00:00.000Z --until 2026-03-02T00:00:00.000Z

--since must be earlier than --until.

The --limit option sets the maximum number of alert groups to return.

The supported range is 1 through 100.

vercel alerts --limit 25

The --format option supports json output for scripting and automation.

vercel alerts --format json

When you use --format json, the command returns a groups array with the alert group payload from the API.

List alerts for the linked project:

vercel alerts

List team-wide alerts:

vercel alerts --all

Filter by usage and error anomalies:

vercel alerts --type usage_anomaly --type error_anomaly

Print AI investigation summaries for a custom time range:

vercel alerts --ai --since 2026-03-01T00:00:00.000Z --until 2026-03-02T00:00:00.000Z

Export alerts as JSON:

vercel alerts --format json

Show details for a single alert group.

vercel alerts inspect <groupId>

Inspect a group in the linked project:

vercel alerts inspect grp_abc123

Inspect as JSON:

vercel alerts inspect grp_abc123 --format json

The rules subcommands keep working and map 1:1 to vercel monitors. They accept the same options and request bodies, but JSON output keys differ; see Migrate from vercel alerts rules:

See vercel monitors for the full subcommand reference.

• To learn how to configure and receive alerts, see Alerts.
• If you want to automatically investigate alerts with AI, see Agent Investigation.

To create and manage monitors from the terminal, see vercel monitors.

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

• --cwd
• --debug
• --global-config
• --help
• --local-config
• --no-color
• --non-interactive
• --scope
• --team
• --token
• --version

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