Millions of 404 Edge Requests to _ssgManifest, _buildManifest

[abedshamia (Abedalrahman Shamia)]

Sudden Massive Spike in Edge Requests (404 errors)

• Normal daily edge requests: ~2M/day
• After recent deploy: Sudden spike to ~30-40M/day
• Deployment: Using Next.js 12.3.4

The problem is that I’m Getting constant 404 errors (multiple times per millisecond) for these paths:

• /_next/static/{buildId}/_ssgManifest.js
• /_next/static/{buildId}/_buildManifest.js
• /_next/static/chunks/webpack-{hash}.js

Impact

• Massive increase in costs as these 404s count as edge requests

What I’ve Tried

1. Redeploying the same deployment
2. Deploying with new commits
3. Purging the Cache Data

None of these solutions resolved the issue. The high volume of 404 errors with those paths persists.

Additional Context

• This started after a simple deployment last week
• Cannot consistently reproduce the issue
• Logs show these requests happening every millisecond in production

Questions

1. Has anyone encountered similar spikes in edge requests?
2. Any suggestions for debugging these constant 404 errors?
3. Are there known issues with Next.js 12.3.4 that could cause this?

• This started after a simple deployment last week but I doubt that this is the reason.
• Logs show these requests happening every millisecond in production

Any help or guidance would be greatly appreciated. This is significantly impacting our costs.

[system]

There’s another community post with 404 debugging tips that might be helpful. Please give these solutions a try and let us know how it goes.

Debugging 404 Errors

Sometimes things don’t go as expected when deploying a website. If you see a 404 on your site, that means the page or resource couldn’t be found. There are many possible causes, and the absence of something can be tricky debug if you don’t know where to look. Here are some things you can do to find the cause and fix it. Debugging Tips Check the error code If you see a mostly white screen with 404: NOT_FOUND along with a Code and and ID then you can click the blue info box below the error deta…

A human should be around soon to offer more advice. But you can also get helpful information quickly by asking v0.

[anshumanb (Anshuman Bhardwaj)]

Hi @abedshamia, welcome to the Vercel Community!

I’m sorry that you’re facing such issue. Could you share the following information:

• Your next.config.js/ts file contents
• What was the change after which you noticed these spikes?
• Can you try reverting the deployments to an older version where traffic was normal to see that fixes it?