Investigating high bandwidth usage in a Sanity project

Hi Sanity Help,
I noticed spikes in bandwidth usage which do not not entirely correspond with other usage metrics (see attached).

This is a tiny project with virtually no users so the high bandwidth usage is odd. I would like to identify the cause of the high bandwidth usage before adding new users.

Could you please provide logs or other data that could help me identify the cause of the high bandwidth consumption? I am interested in 24th September in particular.

Many thanks,

User

Hey, . Although I'm not part of the Sanity team, there are some quick solutions you can employ here.First, it is common for projects to fetch data all the time from Sanity. If your website is targeted by a bot or even a malicious user, this can cause spikes in data usage.
The most common solution to problems of that nature is adding a caching mechanism which will stop data from being fetched on repeat.

Hi , thank you for your response. Hopefully the Sanity team will be able to retrieve data about the requests which are causing these spikes.

Can you share your project ID?

Hi , certainly. I have DM-ed (not sure public they are)

They’re not considered secret but that’s ok!

OK, it looks like the main consumers are mp3 files. This one in particular is the largest:

Thanks User. OK that makes sense but I am surprised by the amount consumed, especially on 24th September. Is there there additional metadata, e.g. User Agent?

The project is on the free tier and we’ll naturally upgrade but I just want to ensure I’m not doing anything wrong.

In depth reporting like that is only available on Enterprise plans, unfortunately. What stack are you using for your frontend?

Ok we’re not quite there yet!
There are two frontends:

• iOS app (Sanity content exposed via NodeJS-based API)
• web (NextJS hosted in Vercel) but it doesn’t play audio so won’t consume MP3s

Can I assume that the majority of the bandwidth consumed is due to the audio files?

Did you happen to be doing a lot of development on the24th?

Quite possibly. Will take a look

OK actually I was debugging some playback issues in the app. 3GB is pretty hefty but perhaps the app doesn’t do proper client-side caching of the audio

That sounds like the likely cause!

Ok thanks for your help User.

Much appreciated!

Happy to help!