Skip to content


Subversion checkout URL

You can clone with
Download ZIP
Browse files

Merge pull request #228 from travis-ci/mm-status-page-post

Blog post on our new status page
  • Loading branch information...
commit a5e722cb4a127321e377e1cb5fe7ab510ec09c3a 2 parents 3363fa1 + 7e232f6
@roidrage roidrage authored
Showing with 37 additions and 0 deletions.
  1. +37 −0 blog/_posts/
37 blog/_posts/
@@ -0,0 +1,37 @@
+title: Introducing Our Status Page
+author: Mathias Meyer
+twitter: roidrage
+created_at: Thu Mar 7 2013 18:00:00 CET
+permalink: blog/2013-03-07-introducing-our-status-page
+layout: post
+"All Systems Operational!" is the kind of thing everyone loves to see and hear.
+Unfortunately failure is always lurking around the corner. During our outages in
+the past, we lacked a public facing way to inform our users and customers about
+potential issues on the platform, both for open source and private projects.
+In short, we lacked a status page. We're sorry for holding off on shipping one
+for so long, but the good news is, we finally have one in place.
+If you hop over to <> you'll be greeted by our
+friendly mascot and the current state of all relevant parts of Travis CI,
+together with the latest incidents and their resolutions.
+The status updates are also connected to our Twitter account, so any incidents
+will be posted there as well. We'll publish notifications for both platforms
+there to avoid the confusion of having two status pages for each separately.
+The status page also supports updates notifications via email, so you can sign
+up to be notified via email when an issue comes up. Note that you'll get
+notifications for both platforms, which may or may not be relevant to you
+depending on which ones you're using.
+We're using a hosted service for this service, courtesy of the fine folks at
+<>. They just yesterday shipped an initial version of their
+API, so we already started implementing support for hubot so we can update the
+site's status from the comfort of our Campfire room.
Please sign in to comment.
Something went wrong with that request. Please try again.