On December 4th we will be upgrading the Stream Alerts monitoring system. For a few hours starting about noon EST you will not receive alerts or be able to access the site while we upgrade the database and monitoring servers. These updates include false alert fixes, customized alert formatting and additional stream options. Please contact us for a demo account to check out the great changes!
Unfortunately we had to change the IP Address of the California node last evening. If you are receiving alerts from this node and had access lists opened for the old IP, please login to your account and check update your ACLs to use the new address. Please let us know if you have any questions via the contact form and thank you.
Thanks to Stream UK, we now have two new monitoring nodes in the United Kingdom. They are now available for Availability and Payload streams. As of August 1st 2011, we will be shutting down the existing UK node so please migrate any streams you have on that server to one of the new nodes. This is particularly important for anyone with geo-blocking or filters on the IP of our nodes as we will switch you automatically and you may get false alerts.
Unfortunately, due to a licensing agreement, Stream Alerts is unable to register new customers at this time. We continue to operate independently and support our existing customers and thank them for their continued use of Stream Alerts. If you have any questions, or need to update your account, please contact us here.
On the 28th of January, we’ll be rolling out a huge update to the Stream Alerts monitoring system that completely replaces our back-end monitoring system. With the new setup comes new features such as detailed test reports, the ability to monitor DRM protected streams and (finally) Flash payload monitoring. Contact us for a demo account to check out the great changes! > More
Stream Alerts will be down for brief periods between 9am EST and 3pm EST while we perform upgrades to the monitoring network. If you have any questions, please contact us using the support form. Thanks!
This one has been bugging me for quite a while: I needed to be able to run a live, PUSH encoding session on startup that was required to authenticate to the Windows Media Services server. When you use the WME GUI, clicking the Start Encoding button will pop-up a dialog box where you can enter in your user name and password. However if you save your encoding settings as a .WME file and try to run it using the WM Command Script, it won’t be able to authenticate and your stream will not start broadcasting. It took a lot of trial and error since I couldn’t find any documentation on what elements and attributes the server allows, but I found out how to make it work. > More
As 2009 fades into 2010, we’re working hard to bring a whole new Availability monitoring system to life sometime in January. Great new features include DRM support for tokens, HTTP authentication, playback times, buffering duration, detailed stream/server information and testing logs. A few more bugs and we’ll roll it out soon. So enjoy the holidays and have a safe New Year everyone!
We’ve added another stream monitoring node in Colorado for clients to check their streams from the mid-west. Update your streams today!