Forgot your password?
typodupeerror
Bug Cloud Programming

GitHub Back Online After Service Outage 55

Posted by timothy
from the you-were-asleep-face-it dept.
The Next Web reports that GitHub — home to many open source projects — suffered (and quickly recovered from) a service outage this morning, starting around 14:00 UTC. Other than that the problem "appears to have been caused by its database server," the cause isn't clear.
This discussion has been archived. No new comments can be posted.

GitHub Back Online After Service Outage

Comments Filter:
  • by Anonymous Coward on Sunday June 02, 2013 @12:32PM (#43889455)

    GitHub is based in San Francisco. The time given is UTC. 14:00 UTC is 7am in San Francisco. "Morning" is a local time reference.

  • by Anonymous Coward on Sunday June 02, 2013 @12:43PM (#43889525)

    In my opion their system already handles everything quite well. I've noticed few outages (this one I only heard about because I was reading slashdot, it's sunday, I'm not even working on my project right now) and, so far, they all have recovered quickly. Moreover, due to the nature of git, the outages could even be longer and more frequent that it would still not be a big issue. The issue tracking system is a bit more critical, but I hardly think anything of great value will be lost due to the problems I've seen so far. From the perspective of one of their paying users, the only change I'd care about is lower price. The system itself is already available enough that I don't consider that an issue at all.

    The most worrisome thing on github so far was when it got hacked. However, having high availability would not help in this situation. That was a one time thing. That seems to have happened once to every major service out there. If it was a regular thing, then it would be a big issue.

"A mind is a terrible thing to have leaking out your ears." -- The League of Sadistic Telepaths

Working...