Github is using Unicorn as their web server.
If you face the 502 error page (https://github.com/502 with the Unicorn) that
only means that the Unicorn worker your request was send too took too much time to process it, and was killed.
https://github.com/blog/517-unicorn
Nothing crazy.
I don't think they were trying to be funny. I think it's just jargon talk. I work with unicorns all day and this didn't strike me as an attempt at humour, more as a technical description of what is going on.
When storage availability is degraded and I can't even clone my repositories (not using the web interface at all) it is pretty enraging to see the status page and twitter account talking about angry unicorns. I get that ruby devs understand this, but not all of us who use Github know or care about them using Unicorn as their webserver. It seems to us like they are trying to be cute and funny at a poor time.
Heh, you caught me there. I don't actually work on long stretches. I usually check HN, Twitter, reddit after every 15-20 minutes of work. I can't concentrate for longer than that.
Not sure, but I thought when I looked at the charts that the spikes to higher latency and exception rates looked like unicorn horns poking over the horizon.
Doesn't look very MLP-ish in expression. I'd suspect the Invisible Pink Unicorn, except that this one's, well, visible. Perhaps a Robot Unicorn Attack reference?