My team would also benefit from this. Though we would prefer to lean toward the Google Apps status page:
https://www.google.com/appsstatus#hl=en&v=status
And maybe have what Scott suggested follow that for a recent history of incidents/problems and any related KB/FAQ articles.
Exactly was I was looking for this morning.
We've used Staytus and Cachet in the past
however surely we should be able to have these as an integrated part of the solution. then we can publish status to end user portal
Scott Willett
My inspiration for this: https://its.uq.edu.au/serviceview
Want to be able to communicate outages, degraded services, known issues. A status page like above is a possible way to achieve this, along with email / other mass text communication methods.
I see some potential for FreshService to do some great things with this which I think should be considered:
11 people like this idea