Skip to content

⌘K

Welcome to the new Vercel Community beta

Report feedback

Community

Community
Announcements
Knowledge Base
Showcase
Events
Live Sessions
Hackathons
Discussions
Help
Feedback
Open Source
v0

Code of Conduct About Privacy Notice Feedback

Vercel Community is built using Discourse.org, an open source discussion platform. For more information on privacy practices, visit discourse.org/privacy.

Community
Announcements
Knowledge Base
Showcase
Events
Live Sessions
Hackathons
Discussions
Help
Feedback
Open Source
v0

Next.js service worker triggers a lot of requests - Help - Vercel Community

Community
Help

Next.js service worker triggers a lot of requests

Nov 26, 10:36 AMClosed#nextjs

Hello,

Billing for our Next.js project has increased a lot over the last month (x5) due to some misconfiguration. As we're trying to understand the causes for this usage (which is still not clear) we have been digging into Vercel Monitoring. It looks like our service worker (which we have not configured in any special way) is triggering a lot of requests and data transfer.

This doesn't look normal to me. How can we mitigate this ? sw-requests sw-data-transfer

Vercel Alum

Hi, ! Welcome to the Vercel Community

Thanks for your patience with this! Some ideas on troubleshooting:

Check your service worker's cache configuration:

Verify the cache duration and invalidation strategy
Ensure proper cache headers are set
Consider implementing cache versioning

Review your service worker registration:

Make sure it's not repeatedly registering/unregistering
Check the update frequency settings
Consider limiting the scope if possible

Monitor your service worker's network requests:

Use Chrome DevTools to inspect the service worker
Look for any infinite loops or excessive fetching
Check for unnecessary asset prefetching

If you could try these suggestions out, and get back to us with updates - that'd be super helpful!

This topic is closed. It no longer accepts new replies.