GitHub incident 2022-03-23 • Hacker News Board

Re: GitHub incident 2022-03-23

#31

Post by julianlam » Wed, Mar 23, 2022, 3:27 PM UTC

Jiejeing wrote: post #25

nimbius wrote: post #16

https://www.githubstatus.com/history 21 incident outages in just 3 months. At this rate the benefits of running your own gitea or gitlab are starting to become competitive.

If you are a closed org, that is. Running your own gitea or gitlab with registration enabled and having to deal with spam is a real hurdle.

Is it not possible to restrict access to the git server from a VPN server only?

Just off the top of my head, that's one thing you can do.

Re: GitHub incident 2022-03-23

#32

Post by gjulianm » Wed, Mar 23, 2022, 3:27 PM UTC

edgyquant wrote: post #22

nimbius wrote: post #16

https://www.githubstatus.com/history 21 incident outages in just 3 months. At this rate the benefits of running your own gitea or gitlab are starting to become competitive.

I’m not sure at what organization that is true. My company lives out of GitHub and Jira and I’ve hardly noticed the three month surge. GitHub would have to do a lot worse to get many companies to want to host their own services. This is the argument people have said about the cloud from day one. People want to know it isn’t their problem, that makes cloud computing (and things like GitHub) worth their weight in gold.…

At my organization it's always been true. Setting up GitLab is fairly easy, in my company we do it and it's cheap (on-prem hosting is basically zero, and we had the IPs/domains already) and it hasn't given us too many headaches. I think last time I had to do something was maybe a few months ago when I restarted it so that it picked up the updated SSL certificate.

Re: GitHub incident 2022-03-23

#33

Post by chockchocschoir » Wed, Mar 23, 2022, 3:27 PM UTC

nimbius wrote: post #16

https://www.githubstatus.com/history 21 incident outages in just 3 months. At this rate the benefits of running your own gitea or gitlab are starting to become competitive.

> At this rate the benefits of running your own gitea or gitlab are starting to become competitive

No need, just use Codeberg.org instead. They run Gitea and is a free collaboration platform (+ git hosting) for free projects. FOSS/OSS should really consider alternatives to GitHub and GitLab, especially when there are much more FOSS/OSS friendly platforms around.

Re: GitHub incident 2022-03-23

#34

Post by okareaman » Wed, Mar 23, 2022, 3:28 PM UTC

What's the difference between GitHub and GrubHub?

GrubHub delivers

Re: GitHub incident 2022-03-23

#35

Post by Chris2048 » Wed, Mar 23, 2022, 3:28 PM UTC

nimbius wrote: post #16

https://www.githubstatus.com/history 21 incident outages in just 3 months. At this rate the benefits of running your own gitea or gitlab are starting to become competitive.

> running your own

assuming that would be flawless, which it wouldn't

Re: GitHub incident 2022-03-23

#36

Post by Kostic » Wed, Mar 23, 2022, 3:29 PM UTC

cube00 wrote: post #30

blueplanet200 wrote: post #20

I hope they figure out what’s going on every morning. Heard from inside they don’t know why the db dies everyday but restarting it fixes it.

Break out the early morning restart cron job.

Early morning in which timezone?

Re: GitHub incident 2022-03-23

#37

Post by intunderflow » Wed, Mar 23, 2022, 3:32 PM UTC

With how often these happen we might as well sticky this thread for the next one

Re: GitHub incident 2022-03-23

#38

Post by afterburner » Wed, Mar 23, 2022, 3:33 PM UTC

Kostic wrote: post #36

cube00 wrote: post #30

Earlier quoted context omitted.

Break out the early morning restart cron job.

Early morning in which timezone?

GaryOldman.gif

Re: GitHub incident 2022-03-23

#39

Post by belter » Wed, Mar 23, 2022, 3:33 PM UTC

nimbius wrote: post #16

https://www.githubstatus.com/history 21 incident outages in just 3 months. At this rate the benefits of running your own gitea or gitlab are starting to become competitive.

Excluding ones reported as [Errors], [Scheduled] or [Notifications]

2019 -> 39 Incidents

2020 -> 67 Incidents

2021 -> 86 Incidents

2022 -> 20 Incidents so far

Edit: Using Linear Regression...Prediction for total end 2022: 111 Incidents.

Re: GitHub incident 2022-03-23

#40

Post by rglullis » Wed, Mar 23, 2022, 3:34 PM UTC

rvz wrote: post #24

nimbius wrote: post #16

https://www.githubstatus.com/history 21 incident outages in just 3 months. At this rate the benefits of running your own gitea or gitlab are starting to become competitive.

Well, I think I have said that since 2020 [0] and it is self-evident that you are better off self-hosting your own Git repo. If you can host a website you can do it. If GNOME, ReactOS, Wireguard, Linux Kernel Project, Mozilla, etc can do it, so can you. Or even use it as a backup / failsafe just in case. But going 'all in' on GitHub just doesn't make any sense anymore. [0] https://hn.algolia.com/?dateRange=all&page=1…

It's almost like people forget that git is a Distributed Version Control System, after all...