Vercels CDN Gets a New Dashboard Live Traffic Map, Cache Control & Routing – No Redeploy Needed

What’s New in Vercel’s CDN Dashboard?

If you’ve ever wished for a single pane of glass to monitor your Vercel-powered app’s global traffic, manage cache, and tweak routing rules without triggering a full redeploy, your wish just came true. Vercel’s CDN dashboard has been completely rebuilt with three major sections: Overview, Caches, and Project-level Routing.

Let’s break down each one and see how they can streamline your workflow.

1. Overview: Live Global Traffic Map

The new Overview tab replaces the old static metrics page. You now get a live map showing exactly where your traffic is coming from across Vercel’s regions. Alongside the map, you’ll see top-level request volume and cache performance metrics (hit rate, origin latency, etc.).

Why it matters:

• Instantly spot regional bottlenecks or unexpected traffic spikes.
• Quickly verify if your cache strategy is working as expected.
• No more digging through separate analytics tools for basic CDN health.

2. Caches: Redesigned Purge Interface

Purging content from Vercel’s CDN used to be buried under project settings. Now it has its own dedicated Caches tab. You can purge by URL, by tag, or by entire cache layer. The interface is cleaner and faster.

Example use case:

# Before: had to navigate to Settings > Caching > Purge
# After: one click from the CDN dashboard
# You can also use the Vercel CLI:
vercel purge --tag my-release-v2

3. Project-level Routing: No Redeploy Required

This is the biggest quality-of-life improvement. You can now update routing rules (e.g., set response headers, rewrite to an external API) directly from the dashboard UI without triggering a new deployment. Previously, any routing change required a git push and a fresh build. Now it’s instantaneous.

Example:

{
  "headers": [
    {
      "source": "/api/(.*)",
      "headers": [
        {
          "key": "X-Custom-Header",
          "value": "my-value"
        }
      ]
    }
  ],
  "rewrites": [
    {
      "source": "/legacy/(.*)",
      "destination": "https://external-api.com/$1"
    }
  ]
}

You can now apply these rules directly from the dashboard. No code change, no CI/CD pipeline delay.

Limitations & Caveats

• Not a full replacement for Infrastructure-as-Code: For teams that rely on vercel.json for all configuration, the dashboard UI should be used with caution. If you make changes both in code and in the dashboard, conflicts can arise. Vercel recommends treating the dashboard as a convenience layer, not the source of truth.
• Cache purge granularity: While tag-based purging is powerful, you still cannot purge by regex pattern. For complex cache invalidation scenarios, you may need to fall back to the API.
• Routing rules scope: Project-level routing is limited to per-project settings. If you manage multiple projects, you’ll need to configure each one separately.

Next Steps & Learning Path

• Try it now: Go to the CDN tab in your Vercel project dashboard and explore the new Overview map.
• Deepen your understanding: Check out our guide on building fine-grained API authorization with Amazon Verified Permissions to see how routing rules can be paired with auth logic.
• Advanced context engineering: For teams building background coding agents, see our deep dive on context engineering from Spotify’s trenches – it’s a great complement to understanding how CDN-level routing can be used in complex agent workflows.

Conclusion

Vercel’s new CDN dashboard is a welcome upgrade for any developer who wants more visibility and control over their edge infrastructure. The live traffic map, streamlined cache purging, and no-redeploy routing rules reduce friction and speed up iteration. While it’s not a full replacement for code-defined configurations, it’s a powerful tool for day-to-day operations.

Try it today by visiting your project’s CDN tab. For more context on how routing and caching fit into larger architectural patterns, refer to the source announcement.