Hi @sludging, I understand that the usage seems to have gone up after the update.

I'm not sure going output: export will reduce the usage because all requests are Edge Requests (not dynamic).

Let me take this up with our team but it might take some time. So, in the meantime I can suggest three things:

• Disable link prefetching as much as you can (do this immediately)
• Upgrade to the latest Next.js version and see if the usage changes
• Downgrade to the version where usage was within limits

I can't preemptively stop automatic pausing of your project, but in case you get paused, I will be able to assist you.

Update: After reading more about this issue, I realize it's expected behavior of the new Next.js in favor of improved performance and user experience. You can read more about it here: https://nextjs.org/blog/next-16#core-features--architecture

The Next.js team is aware of this feedback.

Hey @anshumanb ,

Thank you for the response and looking into the matter.

While I undertand you say it’s expected behavior, but is it something I can turn off? I don’t think it’s reasonable to put me in a position where I basically have to pay for my site to not be disabled due to a feature change I can’t control.

Or are you saying that doing this will revert me to previous behavior?

Disable link prefetching as much as you can (do this immediately)

I’ve rolled out a new version of my site with prefetch disabled on all of my links and it does seem to immediately make a difference.

I still think the Next.js team should heavily consider not making opt-out behavior that has such implications since it doesn’t seem like a sensible default to me.

Regardless, I suppose my issue is solved now.

I agree that the performance and UX improvements might not make sense for all of the projects. I'll forward this feedback to our Next.js team.

I'm glad you were able to find an interim solution here.

Hi @sludging,

I wanted to follow up regarding the edge request usage issue after your upgrade to Next.js 16. Have you found a permanent solution, or do you still require assistance? If you have additional details or questions, please share them so I can assist you effectively.

Hello,

The only solution I have at the moment is disabling prefetch, which I didn’t need to do in Next.js 15.

While that does solve my problem it means my website has worse UX when compared to earlier, is that the only resolution or is there an alternative? I’d love to not degrade my performance when bumping framework versions as a mitigation for a cost spike that I have no control over.

Would appreciate your thoughts on the matter.