If what I've been seeing is true, then this is actually not so helpful.

I still have my older TiVo HD and have confirmed multiple times that it's able to get to the TiVo service when my Premiere is experiencing a C133 and failing to contact the service. I've seen several threads around here suggesting it might be due to using TiVo's wireless N adapter with the latest software. Some have replaced theirs with other brands of Ethernet bridge, or with an actual Ethernet wire, and gotten a resolution. If this is indeed the source of these maddening C133 errors, then knowing that TiVo's service is up does nothing more than increase our anger at TiVo for not (1) acknowledging the problem and (2) getting a solution out ASAP.

I wonder if a simple ping to the IP of the Tivo mothership would work for this. If so it should be possible to take the result from the ping (succeed or fail) and use that data in an if argument. So put together the IP's for the premiere ping those IP's and if they fail print the message to the screen that the Premiere server is down. Unfortunately I do not know how to use the result of a ping in computer programming but perhaps someone could put something together in c++ or possibly Java. Although we would still need to know the IP's perhaps Margaret can help with that.

It's not just "is the server that sends out guide data up?", it's "what does it do when it finds out it's talking to a -insert series and model number here-?", since the answer seems to vary at certain times depending on which series is trying to get serviced.

Not only do I not see the need for a campaign, I don't even see the need for the feature!

Yes, I understand curiosity, but there are many other things I want TiVo to be working on rather than satisfying curiosity, like reducing the dependency for some actions on their servers being up. The practical import for most folks is going to be zero.