V0 Triggered Unexpected Auto-ReDeploys and Maxed Out My Deploy Limit

v0
1

Summary of the Issue

At some point overnight or early today, my V0 projects began to perform automatic re-deploys of old versions without any action from me. This caused:

  1. My production deployment to suddenly revert to a very old version.

  2. Dozens of unexpected deployment and re-deployment attempts, many of them failed, some successful.

  3. These automatic redeploys consumed my entire deploy/build quota.

  4. I am now blocked from deploying new versions or even deploying a fork with recent changes.

What Happened in Detail

1. Production reverted on its own

When I opened my application this morning, I noticed the production version was a very old one—but I definitely did not issue any redeploy or revert.
All my recent chats and data were still there, but the deployed code was outdated.

2. Many deployments appeared that I did not trigger

When I checked the deployments list in my Vercel dashboard:

  • I found many deployments in the last several hours that I did not start.

  • They were all rebuilding old versions of the project.

  • Some deployments failed, others succeeded.

  • None of them correspond to any activity I performed.

3. Deploy limit was consumed automatically

Because of this unexpected deployment storm:

  • I now get the message:
    “Deploy limit exceeded. Please try again later.”

  • I cannot deploy anything new right now—not even a fork with recent updates.

What I already checked

  • I did not run vercel deploy or any CLI command.

  • I did not click “Redeploy” on old deployments.

  • I did not switch versions manually inside V0.

  • I have no GitHub Actions or CI flows active.

  • I did not push changes to old commits.

  • I don’t have any webhook or integration configured that should be triggering rebuilds.

Still, the activity logs show many deployment attempts I never initiated.

Why I believe this is a bug or unexpected platform behavior

  • The redeploys targeted old versions, not the latest one.

  • They occurred during a timeframe where I had zero interaction with the project.

  • There were enough deployments to drain my entire deploy limit.

  • Production was replaced with an outdated build without my intervention.

This suggests that something in V0, or in the deployment system, triggered builds unintentionally.

What I’m asking for

  1. Investigation into the source of these automatic redeploys.
    Specifically, why Vercel triggered builds of older versions without user action.

  2. Reset or restore my deploy limit,
    since it was consumed by events that I did not trigger.

  3. Confirmation whether this is a known issue or bug related to:

    • V0 deployment history,

    • Deployment retries,

    • Deploy Hooks,

    • Or any internal automated processes.

  4. Guidance on how to prevent this from happening again.

I can provide additional information

I’m able to share:

  • Deployment IDs involved,

  • Timestamps of the unexpected redeploys,

  • Activity Log screenshots,

  • My V0 project version settings,

  • Any additional details needed for investigation.

4

Hi, thanks for reporting. If you could please share any deployment IDs we will take a look. This was likely caused by a bug in our CVE mitigation logic. You can read more about the CVE here: Security Advisory: CVE-2025-66478 | Next.js

Apologies for any confusion or disruption. We will investigate.

5

Hello Max, thanks for letting me know, here are some of my recent unexpected auto-redeploys have ocurred in all my projects, not just in one

image
image1920×1080 213 KB

6

Hi, sorry about this! The v0 update script had some issues and redeployed more than expected

In the future we’ll omit these runs from the daily deployment limit so users with many v0 projects don’t get their quotas eaten

7

@sergionvi, I wanted to check in on your issue with the unexpected auto-redeploys. Have you been able to find a solution, or do you still need assistance? Let me know if that helps!