Live data from Hacker News

GitHub was having issues

githubstatus.com

11–20 of 96 posts

Re: GitHub was having issues

#11
post #9
post #7

Earlier quoted context omitted.

possibly Azure?

Doesn't look like it, unless the status-page update is also affected :) https://status.azure.com/en-us/status

It seems that status pages never work properly in those kind of situations. The only reliable source of information seems to be twitter and HN

Re: GitHub was having issues

#12
post #5

Here we go again [0] and again [1] and again [2] and again [3]. Time to reset the counter once again. Now everything there is degraded performance. Oh dear. Consider a self-hosted alternative or have one as a backup like I have said before. [0] https://news.ycombinator.com/item?id=27192869 [1] https://news.ycombinator.com/item?id=27172443 [2] https://news.ycombinator.com/item?id=26666843 [3] https://news.ycombinator.…

Cue the age old argument chain about outsourcing responsibility vs having control of downtimes.

I’m tired of them now, anyone using hosted solutions should know this by now and they’ve made that choice.

Personally I believe people underestimate how easy it is to host your own services.

But I’m sick of having the conversation over and over, if people aren’t willing to investigate then, what’s the saying: “you can lead a horse to water but you can’t make them drink”

Re: GitHub was having issues

#13
post #5

Here we go again [0] and again [1] and again [2] and again [3]. Time to reset the counter once again. Now everything there is degraded performance. Oh dear. Consider a self-hosted alternative or have one as a backup like I have said before. [0] https://news.ycombinator.com/item?id=27192869 [1] https://news.ycombinator.com/item?id=27172443 [2] https://news.ycombinator.com/item?id=26666843 [3] https://news.ycombinator.…

self hosted won't insulate you from your VCS instance failing. I used to work at a medium-sized company with Gitlab 8 years ago, it was running into several issues and required frequent maintenance.

Re: GitHub was having issues

#15
post #8

Maybe these are just a bunch of coincidences, but I have a feeling that GitHub is being poorly run recently. Apart from quite frequent uptime issues, it seems that Github Actions is pretty half-baked and they completely botched the migration of Dependabot (for example, take a look at this issue and especially, how it was handled: https://github.com/dependabot/dependabot-core/issues/3253 )

A shame they removed all their uptime graphs on the status page, since it's much harder to get a read on things now.

However, scrolling back through the status page's history for the last year shows that there between 6 and 12 incidents every month, and it often hovers at the high end of that range.

That has to be an utter misery for anyone who's on call.

Re: GitHub was having issues

#16
post #3

OT but why did it capitalize the title like that? I submitted "GitHub is having issues". I don't see that for other submissions (unless people manually edit them afterwards). EDIT: Before the change to "GitHub was having issues" it had converted my original submission from "GitHub is having issues" to "GitHub Is Having Issues".

I first interpreted it as a puny way to advertise some improved github issue tracker

Re: GitHub was having issues

#18
post #11
post #9

Earlier quoted context omitted.

Doesn't look like it, unless the status-page update is also affected :) https://status.azure.com/en-us/status

It seems that status pages never work properly in those kind of situations. The only reliable source of information seems to be twitter and HN

Saying that twitter is the only source of truth for something usually means that this something is utterly broken... :D

Re: GitHub was having issues

#19
post #12
post #5

Here we go again [0] and again [1] and again [2] and again [3]. Time to reset the counter once again. Now everything there is degraded performance. Oh dear. Consider a self-hosted alternative or have one as a backup like I have said before. [0] https://news.ycombinator.com/item?id=27192869 [1] https://news.ycombinator.com/item?id=27172443 [2] https://news.ycombinator.com/item?id=26666843 [3] https://news.ycombinator.…

Cue the age old argument chain about outsourcing responsibility vs having control of downtimes. I’m tired of them now, anyone using hosted solutions should know this by now and they’ve made that choice. Personally I believe people underestimate how easy it is to host your own services. But I’m sick of having the conversation over and over, if people aren’t willing to investigate then, what’s the saying: “you can lead…

But the argument isn't static. GitHub has become much more of a target to large-scale attacks as it's grown in popularity and has become mission critical to so many companies and projects.

Security risk isn't a one-and-done decision. It's a changing landscape and, arguably, there are far too many eggs in the GitHub basket for this not to be something people might want to think twice about now.

Re: GitHub was having issues

#20
post #4

What's the reason these Git services have so many issues all the time?

Aren't these pretty heavy duty and any issue sticks very prominently ?

A ton of companies are using these tools literally 24/7, at most of my jobs Github/Gitlab being down meant most of us would just be spending half of our time faking working (rare are the people who could just do "offline" dev for half a day without any external input/output)

Slack could be down it had less impact overall.

Post reply on HN