GitHub: Partial System Outage

The worst part of SaaS is that what seems to happen with these incidents is:

* denial * acknowledgement of a limited scope * promises of transparency and openness * "we're working on it as hard as possible" * "all clear" announcement * carefully worded historical summary downplaying the event as much as possible

I am not saying that GitHub will do that but that is the common approach and it's very frustrating and does a huge disservice to all of us.

As an engineering team, you get held to the standards of whatever SaaS the executives you're talking to happen to know about or lightly use, and their perception is that those services NEVER go down or have issues. The poor and curated historical records don't help you make the case or describe what real SaaS uptime looks like.

Amazon is especially guilty of this. They only really admit issues when they've had a full-on, undeniable outage, and even then they curate the summary and impact very carefully.

Normally the operational status is automatically updated on outages. The past incidents part is managed manually.

There is nothing mentioned in their Twitter Status page too [0]

[0] https://twitter.com/githubstatus

Oddly when I first loaded the page I got the same thing, but refreshing turned it green/Operational. Nothing in the "Past Incidents" either way.