This depends on what kind of monitoring you apply to your stream.

Availability: Stream Alerts Content Availability monitoring won’t eat up much of your bandwidth. Our monitoring software simply connects to your server long enough to confirm that the stream is up or down and then it disconnects until it’s time to check again. The connection period is usually only a second or two at the most.

A good way to estimate the amount of bandwidth we’ll use is to multiply your stream bit-rate by 2 and then multiply that result by the number of test intervals you want to measure. For example, if I have a 24Kbps stream monitored once an hour then I would have 24 tests in a day. 24 x 2 x 24 would give me 1,152 Kb or about 1 Megabit of data a day.

Payload: Our Content Payload monitoring service connects to your stream 24 hours a day, 7 days a week and this will consume much more bandwidth than the Availability service alone. Calculate the amount of bandwidth by dividing your stream’s bitrate by 8 to get the kilo-Bytes per second, then multiply that number by 86400 (number of seconds in a day) and then multiply by the actual days in the month you’re concerned with, or use 30 as an average. Thus with a 24Kbps stream, we would consume about 7.5 GBs a month.