Edge requests limit spiked to 400k

I have a single project which is just a simple nextjs application that uses a external Laravel API for its data layer. Now most of the components inside the app are wrapped using a wrapped that has “use client” so basically most of the components are client components. Tanstack query is being used to interact with the backend API and pull data and display it on the components.

Now recently we had ran an ad that brought us 5,700+ visitors that I could confirm using vercel analytics, but for some reason I found out that there had ben more than 400k edge requests made. I checked the observability section where I found that /_next/image was being called 100k times but that is not an issue because 99.7% of them were cached,

but my other 2 routes products/[slug] and categories/[slug] routes were receiving a lot of requests like 23k with 0% caching, now if I have 5,700+ visitors only they will not make 23k edge request on the same route and my client components do not made request to vercel it makes request to the external backend API so I’m confused here on why there is so many edge requests made and how can I fix this issue? this issue caused my accounts free tier 1m edge requests to exceed, so this is kind of urgent for us. Thank you so much!

I believe that the 0% caching on your dynamic routes is the main culprit here - every request is hitting the edge function instead of being served from cache.

I recommend reading the following:

Let us know how you get on!