News for hackers. Stuff that matters.
Re:GitHub down 2016.10.34 6:06 GMT by 0xmohit on Tuesday October 04, 2016 @02:15AM (#12633608)

  We are currently experiencing major service outages.
https://twitter.com/githubstatus/status/783187145414541312
Re:GitHub down 2016.10.34 6:06 GMT by 0xmohit on Tuesday October 04, 2016 @02:29AM (#12633674)

  Everything operating normally.
https://twitter.com/githubstatus/status/783191801352126465

It might be interested to see the post-mortem (if there is one).

Re:GitHub down 2016.10.34 6:06 GMT by TheDong on Tuesday October 04, 2016 @02:12AM (#12633603)
I flagged this because I don't think that this is actually interesting, will drive discussion, or in general meets the site's guidelines.

I furthermore don't think upvotes/downvotes playout well with this sort of content. It's obviously low-to-zero-value, but it attracts "hey, me too" type upvotes of people saying they observed this super obvious and dumb thing too. I think that factor ends up with a very low-quality post in general.

People who are interested in github will find out by using github and seeing a very clearly identifying unicorn with complete message and status page.

This provides no value or discussion. The likely post-mortem will be interesting, but until then, nothing to see here.

Re:GitHub down 2016.10.34 6:06 GMT by gauravagarwalr on Tuesday October 04, 2016 @02:46AM (#12633717)
Interestingly, only the site was down, most probably just unicorn. No new workers were created, or the existing workers were busy. I was still able to do a git clone using the [email protected]:TEAM/REPO.git format.
Re:GitHub down 2016.10.34 6:06 GMT by stockkid on Tuesday October 04, 2016 @02:22AM (#12633629)
I actually agree with you. Don't understand why you are being downvoted.
Re:GitHub down 2016.10.34 6:06 GMT by muhic on Tuesday October 04, 2016 @02:26AM (#12633663)
> I don't think that this is actually interesting, will drive discussion, or in general meets the site's guidelines.

I disagree with this. The guidelines refer to Anything that good hackers would find interesting and I certainly think a major outage at the heart of open source software is interesting in that it drives discussion around similar experiences, implications, pre-emptive action and mitigation.

Re:GitHub down 2016.10.34 6:06 GMT by TheDong on Tuesday October 04, 2016 @02:27AM (#12633668)
The post-mortem is interesting and drives discussion. This is logically and historically true.

If you look at the other comments here, and in past threads like it, it's obvious that these threads do not.

Re:GitHub down 2016.10.34 6:06 GMT by detaro on Tuesday October 04, 2016 @02:30AM (#12633676)
A single service has been down for less than 30 minutes...

If it were the first time, or anything special about the outage, maybe. Not much new to be said now.

Re:GitHub down 2016.10.34 6:06 GMT by noajshu on Tuesday October 04, 2016 @02:18AM (#12633618)
I noticed that for 1-3 minutes after the outage began (I was between pageloads and noticed the outage immediately) the 503 page did not load after waiting >30s. Afterwards the 503 page loads in < 1s. I wonder what failover configuration Github uses, such that this delay would occur.
Re:GitHub down 2016.10.34 6:06 GMT by misterbowfinger on Tuesday October 04, 2016 @02:22AM (#12633632)
It's probably just the CDN caching the 503 page.
Re:GitHub down 2016.10.34 6:06 GMT by noajshu on Tuesday October 04, 2016 @02:26AM (#12633666)
Do you mean that the CDN takes a few minutes to "kick in" and start serving that page?
Re:GitHub down 2016.10.34 6:06 GMT by joobus on Tuesday October 04, 2016 @02:14AM (#12633607)
Re:GitHub down 2016.10.34 6:06 GMT by nikolay on Tuesday October 04, 2016 @02:21AM (#12633626)
The title has the wrong date.
Re:GitHub down 2016.10.34 6:06 GMT by bhaak on Tuesday October 04, 2016 @02:50AM (#12633730)
And the wrong format. ISO 8601 rules.

Or at least write out the month. That makes it unambiguous regardless of what weird date ordering is used.

Re:GitHub down 2016.10.34 6:06 GMT by foobarbecue on Tuesday October 04, 2016 @02:21AM (#12633625)
34?
Re:GitHub down 2016.10.34 6:06 GMT by nikolay on Tuesday October 04, 2016 @02:24AM (#12633648)
He possibly meant "04".
Re:GitHub down 2016.10.34 6:06 GMT by noajshu on Tuesday October 04, 2016 @02:28AM (#12633671)
I can no longer edit the title -- is this because the post is flagged?
Re:GitHub down 2016.10.34 6:06 GMT by nodesocket on Tuesday October 04, 2016 @02:18AM (#12633617)
git push seems to be working still.
Re:GitHub down 2016.10.34 6:06 GMT by jlukic on Tuesday October 04, 2016 @02:07AM (#12633586)
Good thing we like to deploy at 2AM.. oh wait..
Re:GitHub down 2016.10.34 6:06 GMT by jwandborg on Tuesday October 04, 2016 @02:10AM (#12633595)
You may not realize that Central Europe is already awake and working.
Re:GitHub down 2016.10.34 6:06 GMT by wluu on Tuesday October 04, 2016 @02:13AM (#12633604)
And let's not forget the rest of the Asia-Pacific region where we've been awake and working for the past 8+ hours :)
Re:GitHub down 2016.10.34 6:06 GMT by jwandborg on Tuesday October 04, 2016 @02:44AM (#12633711)
And Christmas Islands/Kirimati (UTC+14[0]) has been awake for the past 12 hours.

[0]: https://en.wikipedia.org/wiki/UTC%2B14:00