p.s. I just posted a Show HN here https://news.ycombinator.com/item?id=13117856
One suggestion, bubble to the top any services that isn't operational ... that way you can easily see at the top all servics which are down.
remote: Resolving deltas: 100% (6/6), completed with 6 local objects.
remote: Unexpected system error after push was received.
remote: These changes may not be reflected on github.com!
remote: Your unique error code: 13f721d92e29fbb811443a19a44a49e0A quick spot check seems most of those are related to GitHub, however. Often times when AWS or Heroku or similar hosting service posts downtime you can see 30% of the services I monitor go down at all once.
Some feedback:
- Great if there was more granularity for some services. Down/warning for all of AWS is not useful. Better if one could scope to region or even better region + service.
- The distinction between warn/down is not entirely clear. Also, it's not clear if it varies between services.
- Great with Slack integration!
- Instead of only selecting by drop-down or search, it would be great with a wall-like page with name + icon/logo, to make it easier to quickly find the service.
- Good with historic stats, makes it easier to choose between down/warn (to know how 'noisy'i it'll be).
Github is on their own gear on their own netblock, but might be on the same IXP fabric with an Akamai POP.
Red is bad right?
remote: Unexpected system error after push was received. remote: These changes may not be reflected on github.com!
/feed subscribe https://status.github.com/messages.rss
I got a "Major service outage" message about 30 minutes ago.
statuspage.io sites have rss/atom feeds in the 'subscribe' options as well.
RSS seems to live on here
- They have an API you could quickly tap to write your own notifier: https://status.github.com/api
- They have a Twitter account that you could pair with IFTTT to send notifications: https://twitter.com/githubstatus