Unexpected Spike in Next.js Image Cache Reads/Writes

Help
1

Issue:
Image cache reads and writes have unexpectedly spiked from zero to around 4k per day, despite having only ~10 users daily. No recent changes were made to the codebase. The app is built with Next.js.

Request:
Looking for insights into what could cause this sudden increase in image cache activity and how to diagnose or resolve the issue.

Additional Context:

  • Using Next.js with next/image for image optimization.
  • The issue appeared without code changes.
  • Traffic has remained consistent at ~10 users/day.

Any suggestions on what to check or potential causes would be appreciated!

image
image1287×513 23.8 KB

2

Im having the same issue

3

I’m having the same issue for both read and writes as of Feb 18 with no code changes.

Screen Shot 2025-02-28 at 9.20.57 AM
Screen Shot 2025-02-28 at 9.20.57 AM1841×1178 116 KB

I’ve changed my tags from Image to img as a temporary workaround.

1 Like
4

Seeing the same thing with the same Vercel / Next combo and also without any code changes, did anyone find anything out?

6

Hi folks, sorry that this was confusing. We’ve recently started tracking these metrics and that’s why it is 0 before Feb 18.

You can read more about it on the changelog:

We also have this documentation to help you with Managing Usage & Costs for image optimization.

I hope this was helpful.