GitHub: We're sorry (again) about (another) outage

GitHub has issued a mea culpa for the latest outage that left users unable to access the code-sharing site.

The company said that a power outage was to blame for Thursday's downtime. The issue did not go unnoticed.

Yikes. GitHub is down. Since my boss doesn't understand git, this is a clear opportunity to play Xbox. I mean, "my code is compiling."

— Scott Hanselman (@shanselman) January 28, 2016

GitHub is down, showing us how programmers designed a single point of failure into their workflows. Well done, everybody.

— Stilgherrian (@stilgherrian) January 28, 2016

"I couldn't do my assignment because GitHub is down" will be the next "my dog ate my homework".

— Jimmy Lin (@lintool) January 28, 2016

On Friday, the text repository issued an explanation for the downtime.

"A brief power disruption at our primary data center caused a cascading failure that impacted several services critical to GitHub.com's operation," wrote systems director Sam Lambert.

"While we worked to recover service, GitHub.com was unavailable for two hours and six minutes. Service was fully restored at 02:29am UTC."

This wouldn't be the first time GitHub has gone down to the dismay of developers. The site has been a favorite target for DDoS attacks and staff wer recently criticized by users for being slow to fix its own code. ®