Live data from Hacker News

GitHub was down

status.github.com

31–40 of 129 posts

Re: GitHub was down

#31
post #23
post #11

Looks like they need some high level analysis on why these outages happen so often. At this point it feels like it’s no longer a series of accidents and that they should improve something.

after this downtime today. We're finally start discussing (again) to use our own Gitlab.

I just setup auto deployment of my Android app to the app store view gitlab-ci, very cool. At this point im not sure if I should spend the time to replicate this in github actions on the copy of the repo.

Re: GitHub was down

#32
post #13

14 Days ago, they went down [0]. And today it's happening again. Twice in less than a month. Another reminder to self host via solutions like GitLab or Gitea. [1] [0] https://news.ycombinator.com/item?id=23675864 [1] https://news.ycombinator.com/item?id=23676072

Could you provide details on how you plan to be more reliable with a self-hosted solution? what kind of archtecture would you use? how many people will be involved in maintaining?

Re: GitHub was down

#33
post #13

14 Days ago, they went down [0]. And today it's happening again. Twice in less than a month. Another reminder to self host via solutions like GitLab or Gitea. [1] [0] https://news.ycombinator.com/item?id=23675864 [1] https://news.ycombinator.com/item?id=23676072

I would choose self-hosting for small to medium size teams any day. I can't fathom why people choose not to self-host at this scale. Your data. Your control. Your network. Your infrastructure. Your responsibility. Are people becoming more afraid of responsibility these days?

Re: GitHub was down

#34
Is there historical data of Github Uptime/Downtime? CSV format or other?

I'd love to do some analysis on how things were pre, vs post the acquisition (and trends in availability)

Re: GitHub was down

#35
post #19
post #8

Earlier quoted context omitted.

But, UI of Gitlab is very bloated. I feel that UI of Github is less bloater than Gitlab. Gitea is OK,but there is no one big instance(yes,I know about codeberg) . Sourcehut is made by one-man in his one-man shop,and it lacks many features that one needs.Also,it is Alpha software.

> But, UI of Gitlab is very bloated. I feel that UI of Github is less bloater than Gitlab. Bloated how? There is a lot of functionality in gitlab, and maybe there is a fair argument that the product itself is bloated, but the UI seems pretty appropriate for the functionality. Maybe I'm just used to it though.

Probably both. I remember the very first versions of Gitlab when it was just announced on habr.com, and it used to be a minimalistic (more in terms of UI) version of Github. As the functionality grew, things got a bit out of control.

Currently UI looks more like it's been designed by people who write code rather than those who have spent considerable time thinking through user interactions and designing based on that. So it's not bloated in terms of the code and libraries, but rather all of the functionality is just thrown to the user as is without much thought.

Re: GitHub was down

#36
post #33
post #13

14 Days ago, they went down [0]. And today it's happening again. Twice in less than a month. Another reminder to self host via solutions like GitLab or Gitea. [1] [0] https://news.ycombinator.com/item?id=23675864 [1] https://news.ycombinator.com/item?id=23676072

I would choose self-hosting for small to medium size teams any day. I can't fathom why people choose not to self-host at this scale. Your data. Your control. Your network. Your infrastructure. Your responsibility. Are people becoming more afraid of responsibility these days?

money.

Re: GitHub was down

#37
post #23
post #11

Looks like they need some high level analysis on why these outages happen so often. At this point it feels like it’s no longer a series of accidents and that they should improve something.

after this downtime today. We're finally start discussing (again) to use our own Gitlab.

At work, we have an employer-provided (some groups also have their own server/setup) GitLab instance. I work on there much more than on GitHub, and am really liking it. Everything seems neatly integrated, especially the CI/CD is nice.

For all I care, GitLab can remain as it is right now. My primary fear is for it to become too bloated, trying to be all things to all people (project management, CI/CD pipeline, bugtracker, Wiki, Git repository, ...).

I would be happy to find out about people's experiences rolling their own GitLab, like what pitfalls to look out for. We are on GitLab CE 13.1.3. The biggest bug plaguing us has been CI/CD failures [0] for no apparent reason; but this is solved by a

    retry:
        max: 1
        when: runner_system_failure
block in the CI YAML, and seems to have been fixed for new releases.

[0]: https://gitlab.com/gitlab-org/gitlab-runner/-/issues/4450

Re: GitHub was down

#38
post #33
post #13

14 Days ago, they went down [0]. And today it's happening again. Twice in less than a month. Another reminder to self host via solutions like GitLab or Gitea. [1] [0] https://news.ycombinator.com/item?id=23675864 [1] https://news.ycombinator.com/item?id=23676072

I would choose self-hosting for small to medium size teams any day. I can't fathom why people choose not to self-host at this scale. Your data. Your control. Your network. Your infrastructure. Your responsibility. Are people becoming more afraid of responsibility these days?

It won't help bring in revenue. Pointless to worry about that at the start

Re: GitHub was down

#40
post #20
post #13

14 Days ago, they went down [0]. And today it's happening again. Twice in less than a month. Another reminder to self host via solutions like GitLab or Gitea. [1] [0] https://news.ycombinator.com/item?id=23675864 [1] https://news.ycombinator.com/item?id=23676072

self-hosting requires quite a bit of scale to be more reliable, otherwise you'll most likely still have possibly longer outages, just at different times.

Very often that's ok if you can choose when the outages occur. With most you can because outages tend to be for regular maintenance and upgrades far more often than hardware failures. A small geographically concentrated company only needs 9 fives.

Even for bigger companies that need more uptime they can at least give a shout out to everyone that it will be unavailable from X to Y, it doesn't just go down randomly with no notice whenever github decides to push a release.

Post reply on HN