Probably a DDoS from a foreign actor.
GitHub was down
51–60 of 94 posts
Re: GitHub was down
#52Github was good while it lasted. Back to SourceForge.
Then if SF goes down we'll go back to emails & patches. Issues will be tracked with post-its & todo lists and communicated by voice.
Re: GitHub was down
#53Re: GitHub was down
#54 Service is recovering and we are continuing to monitor.
[0] https://status.github.com/messagesRe: GitHub was down
#55Re: GitHub was down
#56Earlier quoted context omitted.
Why would one assume that their self-hosted git will never go down or will be up more than github?
At least when it's self-hosted, it's your responsibility and you can fix it. When you are anything larger than a tiny company, this is much less risky. Remember that 'the cloud' just means 'someone else's computers' so you are subject to their infrastructure management practices and uptime guarantees (or lack thereof).
Re: GitHub was down
#57https://status.github.com/messages/2016-07-21 by the way, why the status from July 15, 2016 to July 21, 2016 is red ?
It looks like they've lost a chunk of data - the last items in my news feed are from the 14th of July.
Re: GitHub was down
#58I've heard some good things about GitLab but seems like the majority of the OSS community is still on GitHub (...for now).
Re: GitHub was down
#59Github was good while it lasted. Back to SourceForge.
Re: GitHub was down
#60Probably a DDoS from a foreign actor.
What are the main motivations for foreign actors to DDoS GitHub?
See http://arstechnica.com/security/2015/04/ddos-attacks-that-cr...