What does a good downtime report look like?

[Jon Stevens]

https://github.com/blog/1346-network-problems-last-friday

When a community asks for information about what is going on when downtime occurs (especially with AppEngine), I think that it helps to provide an example of what a good report would look like. After reading this story, I'm really impressed with the level of detail and transparency that GitHub is sharing. In no way did they expose any top secret information, but they certainly made me feel like they've gone above and beyond what they needed to and that is really appreciated.

I think that over the last year or two, the AppEngine staff has really improved their transparency and reporting of issues. Thank you, it hasn't gone unnoticed! That said, it can always get better, which is why I think sharing this link is important.

best,

jon

[hyperflame]

Another interesting downtime report is the Microsoft Azure downtime
from leap day earlier this year:
http://blogs.msdn.com/b/windowsazure/archive/2012/03/09/summary-of-windows-azure-service-disruption-on-feb-29th-2012.aspx

Just a fascinating read, and shows how just a few problems can spiral
into a disaster,